Hi, Looks like it is not able to unregistered during closing the DataSource - which causes memory leak, and Tomcat complains about it.
Check in your web application if any jdbc unregister method using, also try to move your jdbc drivers to tomcat common lib directory instead of using in web application. Regards, Siva On Sun, Apr 30, 2017 at 6:47 AM, Naga Ramesh <naga.ram...@manthan.com> wrote: > Naveen, > > Can u provide the setenv changes and total system RAM and free RAM output > for need to investigation > > Regards, > Ramesh > On Apr 29, 2017 8:53 PM, "Naveen Nandyala - Vendor" < > naveen.nandy...@walmart.com> wrote: > > > Hi Team, > > > > We are using Tomcat "126.96.36.199", 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, 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 > > > > > > > -- Regards Siva #068860592040