Type Exception Report
Message An exception occurred processing JSP page [/jsp/Template4/ProductVarious.jsp] at line [90]
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
org.apache.jasper.JasperException: An exception occurred processing JSP page [/jsp/Template4/ProductVarious.jsp] at line [90] 87: <div id="allcrow"> 88: <div class="wrapper allprods" id="variousproducts"> 89: <%if(myMCateg.getSelectedCategories()!=null && myMCateg.getSelectedCategories().size()>0) { 90: for (int i=0;i<myCateg.getSelectedCategories().size();i++) { 91: WOCateg myCat=(WOCateg)myCateg.getSelectedCategories().elementAt(i); 92: myCat.setTables(mirData); 93: myCat.retrieveCateg(); Stacktrace: org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:617) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:514) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) javax.servlet.http.HttpServlet.service(HttpServlet.java:742) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) com.desys.urlrewrite.UrlRewriter.doFilter(UrlRewriter.java:221) com.desys.urlrewrite.UrlRewriter.doFilter(UrlRewriter.java:208)
Root Cause
java.lang.NullPointerException org.apache.jsp.jsp.Template4.ProductVarious_jsp._jspService(ProductVarious_jsp.java:650) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:742) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:476) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) javax.servlet.http.HttpServlet.service(HttpServlet.java:742) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) com.desys.urlrewrite.UrlRewriter.doFilter(UrlRewriter.java:221) com.desys.urlrewrite.UrlRewriter.doFilter(UrlRewriter.java:208)
Note The full stack trace of the root cause is available in the server logs.