Bug 1021750

Summary: Redeploying BRMS components causes thread leak
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Toshiya Kobayashi <tkobayas>
Component: BRM (Guvnor), Deployment, jBPM ConsoleAssignee: manstis
Status: NEW --- QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.1   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Toshiya Kobayashi 2013-10-22 01:47:45 UTC 
Description of problem:

When you redeploy BRMS components (jbpm-human-task, business-central, business-central-server, jboss-brms), some threads are not cleaned up and keep live.


Steps to Reproduce:
(This is an example of business-central-server. You may test other components with similar steps)

1. Start brms-standalone
2. Login to http://localhost:8080/business-central/
3. Capture a thread dump
4. Redeploy business-central-server.war (e.g. touch web.xml)
5. Login to http://localhost:8080/business-central/
6. Capture a thread dump
7. Compare 2 thread dumps taken in step 3 and 6

Actual results:

The number of threads increases. (You may ignore http threads)

Expected results:

The number of threads is not increased. (You may ignore http threads)

Additional info:

If you use BRMS components in Tomcat 7.0.42, Tomcat will log more clear messages for this issue so maybe useful to verify.

====
SEVERE: The web application [/business-central-server] appears to have started a thread named [Thread-0 (HornetQ-client-global-scheduled-threads-1981488825)] but has failed to stop it. This is very likely to create a memory leak.
====