By: Thomas Maerz user 16 Aug 2016 at 9:54 a.m. CDT

2 Responses
Thomas Maerz gravatar
If a user leaves a browser session open at the Gluu Login page for a longer than normal time, then tries to use the same form to log in without refreshing the page, they are presented with an Apache Tomcat error page for StreamCorruptedException. This wouldn't be a huge issue aside from maybe handling the error in the form rather than a tomcat error, but what I'm seeing is that once this error occurs, no user can log in from any system and all users get the same error until tomcat restarts. This is the error presented: ``` HTTP Status 500 - invalid stream header: 1FD67C2E type Exception report message invalid stream header: 1FD67C2E description The server encountered an internal error that prevented it from fulfilling this request. exception java.io.StreamCorruptedException: invalid stream header: 1FD67C2E java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) java.io.ObjectInputStream.<init>(ObjectInputStream.java:299) com.sun.faces.renderkit.ApplicationObjectInputStream.<init>(ApplicationObjectInputStream.java:81) com.sun.faces.spi.SerializationProviderFactory$JavaSerializationProvider.createObjectInputStream(SerializationProviderFactory.java:211) com.sun.faces.renderkit.ResponseStateManagerImpl.getTreeStructureToRestore(ResponseStateManagerImpl.java:170) javax.faces.render.ResponseStateManager.getState(ResponseStateManager.java:226) com.sun.faces.application.StateManagerImpl.restoreTree(StateManagerImpl.java:650) com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:131) org.jboss.seam.jsf.SeamStateManager.restoreView(SeamStateManager.java:76) com.sun.faces.application.ViewHandlerImpl.restoreView(ViewHandlerImpl.java:311) org.jboss.seam.jsf.SeamViewHandler.restoreView(SeamViewHandler.java:93) com.sun.facelets.FaceletViewHandler.restoreView(FaceletViewHandler.java:317) com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:175) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:103) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) org.jboss.seam.web.RewriteFilter.process(RewriteFilter.java:98) org.jboss.seam.web.RewriteFilter.doFilter(RewriteFilter.java:57) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) ```

By Aliaksandr Samuseu staff 16 Aug 2016 at 10:19 a.m. CDT

Aliaksandr Samuseu gravatar
Hi, Thomas. I believe some issues with stream headers were fixed in 2.4.4. May be it's an option for you to try to upgrade your instance? Best regards, Alex.

By Michael Schwartz Account Admin 16 Aug 2016 at 12:44 p.m. CDT

Michael Schwartz gravatar
yes, this is probably the case. There was a bug in JSF, and if you're seeing this issue, you should follow export / import process, and move to 2.4.4 ASAP.