Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Memory leak error on shutdown with Tomcat

Description

When shutting down a Tomcat server, the following error message will appear in the app server window:

Apr 16, 2013 6:04:29 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc Apr 16, 2013 6:04:29 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-78] but has failed to stop it. This is very likely to create a memory leak. Apr 16, 2013 6:04:29 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-79] but has failed to stop it. This is very likely to create a memory leak. Apr 16, 2013 6:04:29 PM org.apache.coyote.AbstractProtocol stop

  1. Start Liferay with Tomcat

  2. Login as SA

  3. Add a portlet

  4. Shutdown Liferay

Environment

Tomcat 7.0 + MySQL 5. 6.2.x Git ID: 0afe05df98599c0c9094ce8e5eba60d471c44cba. Windows 7.

Attachments

1
  • 16 Apr 2013, 11:09 AM

Activity

Show:

Michael HashimotoApril 22, 2013 at 9:29 AM

Miguel's Email:

Hey guys,

I have been able to reproduce it on my local environment.

Tomcat is complaining about a couple of threads which are not being closed. These threads are not being created by us, but in external libraries (bobo-browse.jar and jython.jar) so we can ignore this messages (I will take a look to newer versions of the libs) since the Java process is being shut down correctly.

Thx!

So for now we will ignore this memory leak. Thanks!

Michael HashimotoApril 19, 2013 at 5:49 PM
Edited

Hi Miguel,

We found some additional steps that will consistently cause this error.

SEVERE: The web application [] appears to have started a thread named [Thread-78] but has failed to stop it. This is very likely to create a memory leak.

Sorry about the confusion. Thanks!

-Michael

Miguel Ángel Pastor OlivarApril 17, 2013 at 2:50 AM

Hey Sharon,

I am not able to reproduce it; everything is working fine for me.

Sometimes you can see an error like this

SEVERE: The web application [] appears to have started a thread named [org.python.google.common.base.internal.Finalizer] but has failed to stop it. This is very likely to create a memory leak

but you can ignore it since it is not Liferay related

Please, reopen the ticket with some more details if you are still able to reproduce it.

Thx!

Won't Fix
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix Priority

5

Bug Type

Regression Bug

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created April 16, 2013 at 11:09 AM
Updated June 25, 2023 at 10:29 PM
Resolved April 22, 2013 at 9:29 AM

Flag notifications