[jboss-jira] [JBoss JIRA] Commented: (JBAS-5941) NullPointerException in ClusteredSession

[Brian Stansberry (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12429121#action_12429121 ] 

Brian Stansberry commented on JBAS-5941:
----------------------------------------

Can you make it 2 minutes and see if the issue goes away? AFAICT, the only way this NPE can occur is if a node where the session isn't active locally expires the session, removing all data for it from JBC, and then another replication message arrives, without the metadata. The metadata is not replicated on every request.  The replication message will restore the JBC node for the session, but it will be partial data, missing the metadata.

The session manager includes logic to defer expiring sessions that aren't active locally to give time for replication messages to arrive, so it's not clear to me why this would fail. But if the problem goes away with a 2 minute expiration time, that will give me a good indication my thinking is on the right track.

Also, how often does the test have sessions configured to fail over?

> NullPointerException in ClusteredSession
> ----------------------------------------
>
>                 Key: JBAS-5941
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5941
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>         Environment: perf01
>            Reporter: Radoslav Husar
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-5.0.0.GA
>
>
> During SOAK (failover, session replication, passivation disabled) testing, after 90 minutes JBoss logs:
> [JBoss] 11:24:29,329 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
> [JBoss] java.lang.NullPointerException
> [JBoss] 	at org.jboss.web.tomcat.service.session.ClusteredSession.update(ClusteredSession.java:1097)
> [JBoss] 	at org.jboss.web.tomcat.service.session.SessionBasedClusteredSession.update(SessionBasedClusteredSession.java:154)
> [JBoss] 	at org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.JBossCacheService.loadSession(JBossCacheService.java:344)
> [JBoss] 	at org.jboss.web.tomcat.service.session.JBossCacheManager.loadSession(JBossCacheManager.java:1432)
> [JBoss] 	at org.jboss.web.tomcat.service.session.JBossCacheManager.findSession(JBossCacheManager.java:491)
> [JBoss] 	at org.apache.catalina.connector.Request.isRequestedSessionIdValid(Request.java:2160)
> [JBoss] 	at org.apache.catalina.connector.CoyoteAdapter.parseSessionCookiesId(CoyoteAdapter.java:626)
> [JBoss] 	at org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:551)
> [JBoss] 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:322)
> [JBoss] 	at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
> [JBoss] 	at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:384)
> [JBoss] 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> [JBoss] 	at java.lang.Thread.run(Thread.java:619)
> Hudson build: http://hudson.qa.jboss.com/hudson/job/as5-soak/44/

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira