Details
-
Bug
-
Resolution: Done
-
Minor
-
4.3.0.GA_CP04
-
None
-
Change log triggered by failover of an expired session from ERROR to DEBUG.
-
Not Required
Description
The following message appears in the server.log when trying to load an HttpSession from the distributed store, i.e. failover. The HttpSession is timed out, but it has not been expired at this point. JBoss does interval based HttpSesion timeout check so this overdue is normal.
> ERROR [org.jboss.web.tomcat.service.session.JBossCacheManager] Cannot add session with id=aaaaaaaaaaaaaaaaaaaaaa** because it is invalid
In JBossCacheManager#loadSession(), it calls JBossCacheManager#add() method, and then ClusteredSession#isValid() is called. In isValid() method, it actually checks time out and performs expire() here. This session instance is not used by JBoss Web because isValid() == false, and new session is created and returned to the application.
Nothing wrong, you can ignore this ERROR message and this ERROR message should be lowered to DEBUG.