Corrupted HttpSession with clustered JBoss 7.1.1
safetytrick Jun 21, 2012 8:48 PMI'm seeing problems with HttpSession clustering in JBoss 7.1.1, occasionally a user's session will become corrupted and until they clear their JSESSIONID they get a blank result from every page. The stack trace for my issue is very similar to: https://issues.jboss.org/browse/AS7-4932
14:48:23,736 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http-app03-10.41.108.33-8080-14) An exception or error occurred in the container during the request processing: java.lang.NullPointerException
at org.jboss.as.web.session.ClusteredSession.update(ClusteredSession.java:973)
at org.jboss.as.web.session.DistributableSessionManager.loadSession(DistributableSessionManager.java:1392)
at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:686)
at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:85)
at org.apache.catalina.connector.CoyoteAdapter.isSessionIdValid(CoyoteAdapter.java:710)
at org.apache.catalina.connector.CoyoteAdapter.parseSessionCookiesId(CoyoteAdapter.java:683)
at org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:609)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:365)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:897)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:626)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2039)
at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
If I'm understanding correctly the workaround for this issue is to disable passivation. In the JBoss 6 bug the issue is marked not critical because passivation is not the default but in the infinispan cache store config within standalone.xml passivation is the default? Is there a different layer of passivation that can be configured under jboss-web.xml? And if so I can work around this issue by setting <file-store passivation="false" /> ?