HTTP Status 500 ? Internal Server Error


Type Exception Report

Message Cannot create a session after the response has been committed

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

javax.servlet.ServletException: Cannot create a session after the response has been committed
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:230)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)

Root Cause

java.lang.IllegalStateException: Cannot create a session after the response has been committed
	org.apache.catalina.connector.Request.doGetSession(Request.java:2957)
	org.apache.catalina.connector.Request.getSession(Request.java:2419)
	org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:650)
	org.apache.myfaces.context.servlet.SessionMap.setAttribute(SessionMap.java:56)
	org.apache.myfaces.util.AbstractThreadSafeAttributeMap.put(AbstractThreadSafeAttributeMap.java:109)
	org.apache.myfaces.util.AbstractThreadSafeAttributeMap.put(AbstractThreadSafeAttributeMap.java:38)
	org.apache.myfaces.application.viewstate.ServerSideStateCacheImpl.saveSerializedViewInServletSession(ServerSideStateCacheImpl.java:250)
	org.apache.myfaces.application.viewstate.ServerSideStateCacheImpl.saveSerializedView(ServerSideStateCacheImpl.java:642)
	org.apache.myfaces.renderkit.html.HtmlResponseStateManager.saveState(HtmlResponseStateManager.java:138)
	org.apache.myfaces.application.StateManagerImpl.saveView(StateManagerImpl.java:279)
	org.apache.myfaces.shared.view.JspViewDeclarationLanguageBase.renderView(JspViewDeclarationLanguageBase.java:220)
	org.apache.myfaces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:313)
	org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:116)
	org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:267)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:200)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)

Note The full stack trace of the root cause is available in the server logs.


Apache Tomcat/9.0.85