Hi,
I'm sending JMS message from
Tomcat to weblogic JMS server. Its wroking well. But when I try to shut down the Tocat server, the log shows the following message,
INFO: Stopping service Catalina
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/MyApp] registered the JBDC driver [oracle.jdbc.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the
JDBC Driver has been forcibly unregistered.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a
thread named [Status] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [weblogic.timers.TimerThread] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [weblogic.transaction.TxTimer: '1'] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [ExecuteThread: '0' for queue: 'default'] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [ExecuteThread: '1' for queue: 'default'] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [ExecuteThread: '2' for queue: 'default'] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [ExecuteThread: '3' for queue: 'default'] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [ExecuteThread: '4' for queue: 'default'] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/MyApp] appears to have started a thread named [ExecuteThread: '0' for queue: 'JmsAsyncQueue'] but has failed to stop it. This is very likely to create a memory leak.
Jan 19, 2011 1:32:15 PM org.apache.coyote.http11.Http11AprProtocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Jan 19, 2011 1:32:15 PM org.apache.coyote.ajp.AjpAprProtocol destroy
INFO: Stopping Coyote AJP/1.3 on ajp-8009
Basically my applcation is sending JMS message to
EJB messageDriven Bean deployed under weblogic. Currently I dont see any problem with my tomcat server. I'm worried abt the issue will create any problem in future. Any information will be helpful.
Thanks.