Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1035787 - Thread leak in JBossWeb after :reload
Summary: Thread leak in JBossWeb after :reload
Status: CLOSED DUPLICATE of bug 1032552
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: EAP 6.3.0
Assignee: Rémy Maucherat
QA Contact: Radim Hatlapatka
Russell Dickenson
Depends On:
TreeView+ depends on / blocked
Reported: 2013-11-28 13:26 UTC by Ladislav Thon
Modified: 2014-06-29 22:52 UTC (History)
2 users (show)

Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-12-19 09:36:16 UTC
Type: Bug

Attachments (Terms of Use)
reproducer (deleted)
2013-11-28 13:26 UTC, Ladislav Thon
no flags Details
preliminary patch (deleted)
2013-11-28 13:27 UTC, Ladislav Thon
no flags Details | Diff

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1032552 None None None Never

Internal Links: 1032552

Description Ladislav Thon 2013-11-28 13:26:55 UTC
Created attachment 830235 [details]

Description of problem:

JBossWeb threads keep running after :reload, even though the subsystem is stopped successfully.

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

EAP 6.2.0.CR3

How reproducible:


Steps to Reproduce:
1. Start EAP
2. Invoke :reload via the CLI several times
3. Look at the number of running threads named "http-/*" via jstack

I have this automated in the script (see attachment).

Actual results:

The number of threads keeps rising during the test.

Expected results:

The number of threads is still the same during the test.

Additional info:

I looked into the implementation of JBossWeb and I believe I fixed the problem. Attaching a patch for the class -- note that this totally needs review, as I'm not familiar with the codebase. Also note that similar patch might be needed for NioEndpoint and maybe others, not sure.

Comment 1 Ladislav Thon 2013-11-28 13:27:29 UTC
Created attachment 830236 [details]
preliminary patch

Comment 2 Rémy Maucherat 2013-11-29 16:56:47 UTC
Very good catch, it would leak 2 or 3 threads depending on the connector. Obviously it was a bit hard to notice.

I applied something like your patch (for all connectors).

Comment 3 Radim Hatlapatka 2013-12-19 09:36:16 UTC
Closing as duplicate as it is about the same issue as in BZ#1032552

*** This bug has been marked as a duplicate of bug 1032552 ***

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