Bug 961617 - Tomcat7 - possible memory leak when stopping it
Summary: Tomcat7 - possible memory leak when stopping it
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Web Server 2
Classification: JBoss
Component: tomcat7
Version: 2.0.1
Hardware: i386
OS: Windows
low
low
Target Milestone: ---
: 2.0.1
Assignee: David Knox
QA Contact: Libor Fuka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-10 05:42 UTC by Libor Fuka
Modified: 2015-11-02 00:18 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-03 12:58:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Libor Fuka 2013-05-10 05:42:50 UTC
Description of problem:
1. Stopping Tomcat7 on Windows shows SEVERE in catalina.out

May 9, 2013 6:19:43 AM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance.
May 9, 2013 6:19:43 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-apr-8080"]
May 9, 2013 6:19:43 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-apr-8009"]
May 9, 2013 6:19:43 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
May 9, 2013 6:19:44 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/docs] appears to have started a thread named [SeedGenerator Thread] but has failed to stop it. This is very likely to create a memory leak.
May 9, 2013 6:19:44 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/docs] appears to have started a thread named [SeedGenerator Thread] but has failed to stop it. This is very likely to create a memory leak.
May 9, 2013 6:19:44 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-apr-8080"]
May 9, 2013 6:19:44 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["ajp-apr-8009"]
May 9, 2013 6:19:44 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-apr-8080"]
May 9, 2013 6:19:44 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-apr-8009"]

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jean-frederic Clere 2013-05-13 10:01:19 UTC
I can't reproduce that one on the box I have...

Comment 2 Libor Fuka 2013-05-13 12:00:27 UTC
It happens only on MS Windows 2008 32-bit with OracleJDK 1.6, 1.7.
MS Windows 2008 64 bit and MS Windows 2008 R2 64 bit are OK.

Comment 3 Jean-frederic Clere 2013-05-13 12:23:28 UTC
The box I have tried is MS Windows 2008 R2 64 :-( and I used a 32-bit JVM.

Comment 4 Jean-frederic Clere 2013-05-13 15:39:04 UTC
After looking a little.
I think it isn't a Tomcat7 but a problem with the entropy in the box See http://www.docjar.com/html/api/sun/security/provider/SeedGenerator.java.html, the thread hangs because there isn't enough entropy in the box.
Typically a server without mouse and keyboard.
Would it be possible to wait either between the tests or during the test and see if the error just goes away?

Comment 5 Libor Fuka 2013-05-14 06:48:37 UTC
I retest it manually on Windows 2008 32bit machine with JDK 1.7, did repeat-ably startup/shutdown of tomcat7 and problem did not appear in catalina.out.
Its random problem, hard to simulate.

Comment 6 Libor Fuka 2013-05-14 07:33:33 UTC
setting low priority beacuse the bug is hard to simulate

Comment 7 Libor Fuka 2013-05-14 07:42:27 UTC
It should go to known issue in release notes

Comment 8 Mandar Joshi 2013-05-15 09:29:42 UTC
Added DocText.

@David, can you please review the Doc Text content?

Comment 9 Jean-frederic Clere 2013-05-31 06:30:49 UTC
The DocText looks ok.

Comment 10 Libor Fuka 2013-06-07 07:03:28 UTC
This problem disappeared from Tomcat7 catalina.out log on MS Windows after upgrading to 7.0.40.
Tomcat6 catalina.out log on MS Windows is also without this problem.

You can remove this bug from known issues in release notes 2.0.1

Comment 11 Misha H. Ali 2013-06-07 07:16:40 UTC
Assuming lfuka means to remove it from release notes altogether. Removed flag.

Comment 12 Jean-frederic Clere 2013-06-07 09:53:40 UTC
Well it is a fixed bug instead a known one :D

Comment 13 Libor Fuka 2013-06-07 10:03:02 UTC
Thank you Jean-Frederic
Misha please move this to bug fix section

Comment 14 Michal Haško 2013-06-12 12:49:29 UTC
Based on comment #10.


Note You need to log in before you can comment on or make changes to this bug.