You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/08/06 17:08:27 UTC
DO NOT REPLY [Bug 11502] New: - Tomcat does not terminate all servlets correctly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11502>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11502

Tomcat does not terminate all servlets correctly

           Summary: Tomcat does not terminate all servlets correctly
           Product: Tomcat 4
           Version: 4.1.8
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: Erich.Meier@methodpark.de


The current tomcat version does not stop all my servlets correctly. I use 
struts (the current nightly build) and define four servlets 
named "init", "config", "download" and "pkit". They all start up correctly (my 
application is under the /pkit context):

2002-08-06 16:53:00 StandardWrapper[/pkit:default]: Loading container servlet 
default
2002-08-06 16:53:00 default: init
2002-08-06 16:53:00 init: init
2002-08-06 16:53:01 StandardWrapper[/pkit:invoker]: Loading container servlet 
invoker
2002-08-06 16:53:01 invoker: init
2002-08-06 16:53:01 config: init
2002-08-06 16:53:05 download: init
2002-08-06 16:53:05 jsp: init
2002-08-06 16:53:05 pkit: init

If I stop tomcat, it tries to make the session persistent (and fails because my 
sessions are not yet serializable) and stops the servlets. But it only stops 
three of the servlets. The fourth servlet named "pkit" (the main servlet that 
processes the struts actions) is never stopped and thus, the JVM refuses to 
stop.

Here is the excerpt from the log. Please note that the "pkit" servlet is not 
mentioned there:

2002-08-06 17:01:18 StandardHost[localhost]: Removing web application at context
 path /manager
2002-08-06 17:01:18 StandardHost[localhost]: Removing web application at context
 path /pkit
2002-08-06 17:01:18 StandardContext[/pkit]: Stopping
2002-08-06 17:01:18 StandardContext[/pkit]: Stopping filters
2002-08-06 17:01:18 StandardManager[/pkit] Cannot serialize session attribute us
er for session 78E657ED2623FEEBA49892B47D257BF7
java.io.NotSerializableException: de.methodpark.pkit.storage.User$1
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
        ...
2002-08-06 17:01:18 StandardContext[/pkit]: Processing standard container shutdo
wn
2002-08-06 17:01:18 ContextConfig[/pkit]: ContextConfig: Processing STOP
2002-08-06 17:01:18 download: destroy
2002-08-06 17:01:18 config: destroy
2002-08-06 17:01:18 init: destroy
2002-08-06 17:01:18 StandardContext[/pkit]: Sending application stop events
2002-08-06 17:01:18 StandardContext[/pkit]: Releasing document base pkit
2002-08-06 17:01:18 StandardContext[/pkit]: Stopping complete
2002-08-06 17:01:18 StandardHost[localhost]: Removing web application at context
 path
2002-08-06 17:01:18 StandardHost[localhost]: Removing web application at context
 path /admin

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>