Loading...

XML

Word

Printable

Affects:

Release Notes
Workaround:

Workaround Exists
Workaround Description:

Hide

Use StrictMaxPool instead

Show
Use StrictMaxPool instead
Release Note Text:

Hide
A memory leak was discovered in the InfinitePool's implementation of the ThreadLocalPool which could eventually lead to OutOfMemory exceptions. The InfinitePool maintained a list of active beanContexts but did not override the discard method so a small memory leak occurred every time this method was called. A discard method was implemented, preventing memory leaks occurring.

Show
A memory leak was discovered in the InfinitePool's implementation of the ThreadLocalPool which could eventually lead to OutOfMemory exceptions. The InfinitePool maintained a list of active beanContexts but did not override the discard method so a small memory leak occurred every time this method was called. A discard method was implemented, preventing memory leaks occurring.
Release Note Status:
Documented as Resolved Issue
Docs QE Status:
NEW

Platform JIRA for ~~EJBTHREE-2251~~ - ThreadlocalPool.discard() memory leak when exception thrown from bean method

incorporates

EJBTHREE-2251 ThreadlocalPool.discard() memory leak when exception thrown from bean method

is incorporated by

JBPAPP-7578 Upgrade jboss-ejb3-bom-eap5 to 1.0.4

is related to

AS7-1687 Pooled components do not discard instances on system exception