The negative active session count is a bug; thanks for pointing it out. See http://jira.jboss.com/jira/browse/JBAS-2897.
anonymous wrote : When we invalidate the session, it makes the session a local session instead of a clustered session. What do you guys think? The logging from your last post shows what happens when a session times out, rather than being invalidated via an explicit call to session.invalidate(). Are you saying you changed the session replication code so it does this now? Or you somehow tweaked your webapp so it does causes an expiration rather than an invalidation (e.g. change the session's maxInactiveInterval to 1 so it will immediately expire)? In any case, what happens after the last log statement is the session is removed from the local cache. However, it still exists in the other cluster node's caches. So, if your user fails over to another node, they will see the old session data. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927979#3927979 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927979 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
