4 Replies Latest reply on Jun 18, 2006 8:26 PM by Brian Stansberry

    replication problem with cross-context session updates

    Eric Reed Newbie

      We're using 2 nodes of JBoss 4.0.4.GA with an Apache mod_jk balancer. We've also enabled the ClusteredSingleSignOn Valve to avoid the FORM challenge during fail-over.

      Usage: webapp1 calls another webapp2 via cross-context dispatch during the Request, and webapp2 is making updates to a non-primitive session attribute. However, replication seems to be missing the updates. When node1 dies, the user is properly sent over to node2, but the updates that were made to webapp2's session are missing. (The user never requests webapp2 directly.)

      We've watched the printDetails() on the TomcatClusteringCache MBean, and the session for webapp1 increments its VERSION with each new request, but the session for webapp2 doesn't. Is Tomcat keeping a separate session cache?

      Also, this article http://www.theserverside.com/tt/articles/article.tss?l=ClusteringTomcat makes me wonder if cross-context session updates will replicate at all under JBoss, given the fact that we have no Cluster element in the tomcat.sar's server.xml. Or is that element unnecessary under JBoss?

      any help is greatly appreciated.