HTTP Status 500 - An exception occurred processing JSP page /modules/clientHomeCn/aberdeenCentre.jsp at line 17


type Exception report

message An exception occurred processing JSP page /modules/clientHomeCn/aberdeenCentre.jsp at line 17

description The server encountered an internal error that prevented it from fulfilling this request.

exception

org.apache.jasper.JasperException: An exception occurred processing JSP page /modules/clientHomeCn/aberdeenCentre.jsp at line 17

14:     session.setAttribute("lanUrl","aberdeenCentre.jsp?centerId="+centerId);   
15: }
16: 
17: Center center=cd.getCenterById(Integer.parseInt(centerId));
18: List<Staff> staffList=sd.getWebStaffByCenterId(centerId); 
19: if(staffList==null){
20:   staffList=new ArrayList<Staff>();


Stacktrace:
	org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:521)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:430)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
	com.embraiz.filter.RoleFilter.doFilter(RoleFilter.java:90)

root cause

java.lang.NumberFormatException: For input string: "86?lctHref=15"
	java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	java.lang.Integer.parseInt(Integer.java:492)
	java.lang.Integer.parseInt(Integer.java:527)
	org.apache.jsp.modules.clientHomeCn.aberdeenCentre_jsp._jspService(aberdeenCentre_jsp.java:116)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
	com.embraiz.filter.RoleFilter.doFilter(RoleFilter.java:90)

note The full stack trace of the root cause is available in the Apache Tomcat/6.0.44 logs.


Apache Tomcat/6.0.44