卡特彼勒D5K2履带推土机
卡特彼勒D5K2履带推土机
Type Exception Report
Message An exception occurred processing [resources2020/pro/contrast_brand_prolist.jsp] at line [50]
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
org.apache.jasper.JasperException: An exception occurred processing [resources2020/pro/contrast_brand_prolist.jsp] at line [50] 47: String realPath = Common.getAbsolutePath(request) ; 48: 49: for(Map brand : brandList){ 50: String pronum = CommonString.getFormatPara(brandProMap.get(CommonString.getFormatPara(brand.get("id"))+"_"+catalog)); 51: String brandName = CommonString.getFormatPara(brand.get("name")); 52: String shou = getFirstLetter(brandName); 53: brand.put("pronum", pronum); Stacktrace: org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:610) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:499) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:379) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:327) javax.servlet.http.HttpServlet.service(HttpServlet.java:764) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) com.jerehnet.filter.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:36)
Root Cause
java.lang.NullPointerException org.apache.jsp.resources2020.pro.contrast_005fbrand_005fprolist_jsp._jspService(contrast_005fbrand_005fprolist_jsp.java:235) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:764) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:466) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:379) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:327) javax.servlet.http.HttpServlet.service(HttpServlet.java:764) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) com.jerehnet.filter.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:36)
Note The full stack trace of the root cause is available in the server logs.