Type Exception Report
Message An exception occurred processing [detail-bando-siab.jsp] at line [173]
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
org.apache.jasper.JasperException: An exception occurred processing [detail-bando-siab.jsp] at line [173] 170: String tipoAvviso = ""; 171: if ("Avviso".equals(tipo)) { 172: entryAvviso = siabScp.getListaAvvisiEntryById(""+id); 173: dettaglioAvviso = siabScp.dettaglioAvviso(VERIFY_SSL, codice, entryAvviso.getCodiceSA(), entryAvviso.getCodiceSistema().toString()); 174: 175: if (dettaglioAvviso != null) { 176: if (dettaglioAvviso.getTipologia() != null) { 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:623) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) it.publisys.filter.XSSFilter.doFilter(XSSFilter.java:25)
Root Cause
java.lang.NullPointerException: Cannot invoke "java.lang.Long.toString()" because the return value of "it.publisys.siabscp.wsConsultBandi.model.ListaAvvisiEntry.getCodiceSistema()" is null org.apache.jsp.detail_002dbando_002dsiab_jsp._jspService(detail_002dbando_002dsiab_jsp.java:983) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:623) 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:623) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) it.publisys.filter.XSSFilter.doFilter(XSSFilter.java:25)
Note The full stack trace of the root cause is available in the server logs.