tomcat has stop working unexpectedly.

[glb anil singh]

apache tomcat server has stop services after some times. then i have to start it. my website is deployed on cyberhost.

bellow is logs of the server.


Sep 11, 2012 10:30:43 AM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-4844
Sep 11, 2012 10:30:44 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Destroying JForum...
Sep 11, 2012 10:30:44 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/jforum] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
Sep 11, 2012 10:30:44 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/jforum] appears to have started a thread named [HSQLDB Timer @1567e6c] but has failed to stop it. This is very likely to create a memory leak.
Sep 11, 2012 10:30:44 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/jforum] appears to have started a thread named [File Reaper] but has failed to stop it. This is very likely to create a memory leak.
Sep 11, 2012 10:30:44 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/key] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Sep 11, 2012 10:30:44 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/web] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Sep 11, 2012 10:30:44 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-4844


Is there any permanent solution of this problem?

[Bill Clar]

I had a similar problem when too many database connections ran amok without being properly closed and sent back to the Connection pool. By closing every connection I was able to eliminate Tomcat crashes.

I'm not saying this is the source of your problem as I don't know your application. You may need to look into profiling software to check for memory leaks.

[glb anil singh]

Bill Clar wrote:I had a similar problem when too many database connections ran amok without being properly closed and sent back to the Connection pool. By closing every connection I was able to eliminate Tomcat crashes.

I'm not saying this is the source of your problem as I don't know your application. You may need to look into profiling software to check for memory leaks.

thank you clar for the clue. I am going to check my database connections.