You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Laurent Salinas <La...@rtsnetworks.com> on 2000/02/10 19:32:32 UTC

mod_jserv/5739: JVM never closes down cleanly

>Number:         5739
>Category:       mod_jserv
>Synopsis:       JVM never closes down cleanly
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Feb 10 10:40:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Laurent.Salinas@rtsnetworks.com
>Release:        1.3.11
>Organization:
apache
>Environment:
NT 4.0 SP 4, Apache 1.3.11 with EAPI, mod_jserv 1.1 (all recompiled except NT 8-))
>Description:
Sometimes, it seems that during the shutdown of Apache, the thread in charge 
of watching the JVM hangs. As it can't "read" any event state, the closing down
consists in it (the thread) being killed, and the JVM also, in the wrapper_destroy
function. I've tried to put a log instruction in the wrapper (by waiting
with a time-out and so on...), and it effectively stops tracing as soon
as the shutdown begins.
Sometimes, the thread is well running, but fails in sending the SHUTDOWN
function to the JVM (AJPV12 error). The java side also traces an exception
(Unterminated Stream or something like that).
>How-To-Repeat:
Send me a log of a clean shutdown on NT and I'll begin to think that my 
platform is in fault...
>Fix:
After 3 days spent on the problem, I must admit I'm out of ideas. Maybe a weird
mutual exclusion problem.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]