Bug 1021750 - Redeploying BRMS components causes thread leak
Summary: Redeploying BRMS components causes thread leak
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor), Deployment, jBPM Console
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: manstis
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-22 01:47 UTC by Toshiya Kobayashi
Modified: 2025-02-10 03:28 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:28:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.
====

Comment 4 Red Hat Bugzilla 2025-02-10 03:28:48 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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