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 2004/02/22 13:55:48 UTC
DO NOT REPLY [Bug 27141] New: -
spontaneous clean tomcat shutdown
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=27141>.
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=27141
spontaneous clean tomcat shutdown
Summary: spontaneous clean tomcat shutdown
Product: Tomcat 4
Version: 4.1.27
Platform: Other
URL: http://marc.theaimsgroup.com/?l=tomcat-
user&m=102680354726732&w=2
OS/Version: Linux
Status: NEW
Severity: Critical
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: hauser@acm.org
CC: james.canada@cubepoint.com,szegedia@freemail.hu
My tomcat spontaneously shuts down. Sometimes after a week or even a month,
sometimes after a few hours:
<<GlobalResourcesLifecycleListener: Destroying MBeans for Global JNDI Resources
Stopping service myApp-Standalone
FATAL [Thread-1] (myServlet.java:236) - Feb 22, 2004 6:21:11 AM: shutting down ...?
Stopping service myApp-Port8080
HttpConnector[8080] Stopping background thread
EngineConfig: EngineConfig: Processing STOP
HostConfig[www.mydom.com]: HostConfig: Processing STOP
HostConfig[www.mydom.com]: Undeploying deployed web applications
HostConfig[www.mydom.com]: Undeploying web application at context path
StandardHost[www.mydom.com]: Removing web application at context path
StandardContext[]: Stopping
StandardContext[]: Stopping filters
StandardContext[]: Sending application stop events
StandardContext[]: Processing standard container shutdown
ContextConfig[]: ContextConfig: Processing STOP
StandardContext[]: Stopping complete
Stopping service myApp2
FATAL [Thread-1] (myServlet.java:236) - Feb 22, 2004 6:21:11 AM: shutting down
...?>> in non of the logs, I see a reason why.
Sometimes, it happens minutes up to an hour after an out-of-memory event.
Is there any way to find out why a shutdown was initiated?
A long time ago, others appear to have had similar problems with no reported
resolution: Bug 6028 or
http://marc.theaimsgroup.com/?l=tomcat-user&m=102680354726732&w=2, ...
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org