Clean shutdown? Can sessions survive a jsvc stop/start ?

[August Detlefsen <au...@yahoo.com>]

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: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: Clean shutdown? Can sessions survive a jsvc stop/start ?

[Bill Barker <wb...@wilshire.com>]

"August Detlefsen" <au...@yahoo.com> wrote in message 
news:20050408191321.2506.qmail@web54305.mail.yahoo.com...
> 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: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org