Try killing one of the Tomcat JVM's at the OS level.
-Robert
Richard Mixon (qwest) wrote:
Filip,
Thanks so much for some reason taking the "<Manager " statement completely out of the context worked.
I can now see session replication occurring, which then identified some objects that were not serializable. I have fixed these and can see the session replicating correctly in the log messages.
I quickly realized that I could not just run "catalina stop" as this caused the session to be deleted on both the tomcat instance that was stopping and on the remaining Tomcat instance - hence the reason I was always prompted to re-login in.
So how do I trigger the "maintenance failover"? If I use the Admin console to delete the port 8009 connector (first Tomcat instance), this does not prevent JK from continuing to route traffic to this instance.
I also tried using "ant stop" from the tomcat-deployer, but this results in a "HTTP Status 503 - This application is not currently available" message.
I feel like I'm very close, but not quite there.
Thank you - Richard
Filip Hanik - Dev wrote:
you said you enabled it in your context.xml file, if so remove it
---- <snip> ----- this was getting really long...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
