Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 961617

Summary:	Tomcat7 - possible memory leak when stopping it
Product:	[JBoss] JBoss Enterprise Web Server 2	Reporter:	Libor Fuka <lfuka>
Component:	tomcat7	Assignee:	David Knox <dknox>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Libor Fuka <lfuka>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.0.1	CC:	jclere, jdoyle, majoshi, mhasko, mhusnain, pslavice, rsvoboda
Target Milestone:	---
Target Release:	2.0.1
Hardware:	i386
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	JBoss Enterprise Web Server's Tomcat 7 did not stop correctly when used with the Windows operating system and instead displayed an error in the <filename>catalina.out</filename> file. This issue is fixed in JBoss Enterprise Web Server 2.0.1. As a result, when Tomcat 7 is used with Windows, it stops as expected and does not display any errors.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-03 12:58:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.