Re: Clean shutdown? Can sessions survive a jsvc stop/start ?
Where do you get the non-buggy version? The TC 5.5 release notes don't mention anything changing in jsvc since version 5.5.3. Is 5.5.9 now released? Does it include the jsvc fixes? --- Bill Barker [EMAIL PROTECTED] wrote: August Detlefsen [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] In TC 5.5.7, the tomcat start/stop script for Linux/Solaris (/etc/init.d/tomcat) stops tomcat by simply killing the process: stop) # # Stop Tomcat # PID=`cat /var/run/jsvc.pid` kill $PID ;; Do user sessions ever get a chance to be serialized if tomcat is stopped in such a manner? They do if you're not using the broken version of jsvc that ships with Tomcat. The non-buggy jsvc program catches SIGTERM and performs a clean shutdown of Tomcat. I have noticed that users are forced to login again (we determine login status based on an object in a user's session) after tomcat restarts and I need to know if the object is getting serialized at all. Is there a better stop procedure? Nope. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clean shutdown? Can sessions survive a jsvc stop/start ?
One mroe question: If you are using jsvc can you still use the $CATALINA_HOME/bin/[shutdown|startup].sh scripts to do manual tomcat restarts? --- August Detlefsen [EMAIL PROTECTED] wrote: Where do you get the non-buggy version? The TC 5.5 release notes don't mention anything changing in jsvc since version 5.5.3. Is 5.5.9 now released? Does it include the jsvc fixes? --- Bill Barker [EMAIL PROTECTED] wrote: August Detlefsen [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] In TC 5.5.7, the tomcat start/stop script for Linux/Solaris (/etc/init.d/tomcat) stops tomcat by simply killing the process: stop) # # Stop Tomcat # PID=`cat /var/run/jsvc.pid` kill $PID ;; Do user sessions ever get a chance to be serialized if tomcat is stopped in such a manner? They do if you're not using the broken version of jsvc that ships with Tomcat. The non-buggy jsvc program catches SIGTERM and performs a clean shutdown of Tomcat. I have noticed that users are forced to login again (we determine login status based on an object in a user's session) after tomcat restarts and I need to know if the object is getting serialized at all. Is there a better stop procedure? Nope. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Clean shutdown? Can sessions survive a jsvc stop/start ?
In TC 5.5.7, the tomcat start/stop script for Linux/Solaris (/etc/init.d/tomcat) stops tomcat by simply killing the process: stop) # # Stop Tomcat # PID=`cat /var/run/jsvc.pid` kill $PID ;; Do user sessions ever get a chance to be serialized if tomcat is stopped in such a manner? I have noticed that users are forced to login again (we determine login status based on an object in a user's session) after tomcat restarts and I need to know if the object is getting serialized at all. Is there a better stop procedure? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clean shutdown? Can sessions survive a jsvc stop/start ?
August Detlefsen [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] In TC 5.5.7, the tomcat start/stop script for Linux/Solaris (/etc/init.d/tomcat) stops tomcat by simply killing the process: stop) # # Stop Tomcat # PID=`cat /var/run/jsvc.pid` kill $PID ;; Do user sessions ever get a chance to be serialized if tomcat is stopped in such a manner? They do if you're not using the broken version of jsvc that ships with Tomcat. The non-buggy jsvc program catches SIGTERM and performs a clean shutdown of Tomcat. I have noticed that users are forced to login again (we determine login status based on an object in a user's session) after tomcat restarts and I need to know if the object is getting serialized at all. Is there a better stop procedure? Nope. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
