On 29/04/17 16:23, Naveen Nandyala - Vendor wrote:
> Hi Team,
> 
> We are using Tomcat "7.0.61.0", and running on SUSE Linux Enterprise
> Server 11 (x86_64), Version 11, and PatchLevel 3.  Our tomcat
> instance is going down due to below message,

No it isn't.

Something is shutting down Tomcat.
That in turn causes Tomcat to stop each of the web applications.
One of those web applications has a memory leak and Tomcat is reporting
it. For an explanation of the memory leak, see my presentation from 2010
[1].

Mark


[1] http://tomcat.apache.org/presentations.html



> and its not a normal
> shutdown we are not sure why and who is causing to throw this
> messages and causing tomcat instance go down.  Can anyone provide
> some inputs for cause of this and how can we debug what is causing.
> 
> Below is op from catalina logs.
> 
> 
> Apr 26, 2017 12:38:41 PM org.apache.coyote.AbstractProtocol pause 
> INFO: Pausing ProtocolHandler ["http-nio-61034"] Apr 26, 2017
> 12:38:41 PM org.apache.catalina.core.StandardService stopInternal 
> INFO: Stopping service Catalina Apr 26, 2017 12:38:52 PM
> org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc 
> SEVERE: The web application [/MainframeJobRequest] registered the
> JDBC driver [com.ibm.db2.jcc.DB2Driver] but failed to unregister it
> when the web application was stopped. To prevent a memory leak , the
> JDBC Driver has been forcibly unregistered. Apr 26, 2017 12:38:52 PM
> org.apache.coyote.AbstractProtocol stop INFO: Stopping
> ProtocolHandler ["http-nio-61034"] Apr 26, 2017 12:38:52 PM
> org.apache.coyote.AbstractProtocol destroy
> 
> 
> 
> Warm Regards, Naveen Kumar Reddy N
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to