All, we are trying to setup a JBoss 3.2.3 (Tomcat) cluster with Apache and mod_jk.
We discovered that the sticky sessions with mod_jk only work if you give the "jvmRoute" parameter in the tomcat configuration file. If we do not use sticky sessions we receive an error from Tomcat if during form based authentication the form post is routed to another instance then the one redirecting to the authentication form. That is OK and form based authentication works fine with the sticky session. The "jvmRoute" paramter causes the extra dot seperated name at the end of the session id. The problem is that we also want session replication and failover in case one machine is not working. So we also configured the <distributable/> tag in the web.xml deployment descriptor and deployed the "jbossha-httpsession.sar". If we stop the first JBoss, which created the session and which got all the request so far because of the sticky session, mod_jk is performing a fail-over and redirects the request to the second JBoss. But this one is now complaining that it does not know the session which has the extension of the "jvmRoute" paramter of the first JBoss. Is is not possible to use sticky sessions and session replication? If not there seems to be a bug in Tomcat which is complaining that he does not understand the login form post of a client which was initiated on anonther Tomcat. Any comments and information about this is appreciated, --Marcus ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
