I have been working with a Tomcat clustering solution that involves sticky
sessions and Clustered Single Sign On.  Everything seems to work, in that
the session information is being replicated as expected, however, the
problem is that when an instance is shutdown (either for failover,
maintenance, whatever) it sends out a SESSION_DESTROYED_EVENT, which
ultimately gets replicated across the cluster and results in the user
needing to re-login.  It appears that the guys and gals over at
jboss.orgcame across this same issue quite some time ago and
implemented a fix in
their JBoss Application Server, but it doesn't appear this fix has been
merged into Tomcat anywhere.  Is there a reason why it was not merged?

The original JBoss JIRA can be found here:
https://jira.jboss.org/jira/browse/JBAS-2429

I am looking for solutions to this problem, so if there is a good reason why
this fix has never made it into the Tomcat source I would like to know so I
can try to find a better solution.  Alternatively, if there is a known way
to deal with this, I would love to hear about it!  Thanks for the help!

Reply via email to