[
https://jira.jboss.org/jira/browse/JBESB-2523?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-2523.
-------------------------------
Resolution: Done
Pulled across 'special' cleanup in revision 26615.
We should consider reviewing this at some point, given the comment.
Thread related InVM resources created by DefaultInVMReplyToEpr not
being cleaned up on thread cleanup
------------------------------------------------------------------------------------------------------
Key: JBESB-2523
URL:
https://jira.jboss.org/jira/browse/JBESB-2523
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.5
Reporter: Tom Fennelly
Assignee: Kevin Conner
Fix For: 4.4 CP3
The DefaultInVMReplyToEpr class creates an InVMCourier + InVMEpr for handling async
replies on a deliverSync over InVM. It attaches these details to the active thread. The
logic at the time was that they could be reused. The obvious flaw in the logic
(hindsight) is that when the threads are pooled and the pool is persiodically cleaned...
new threads are created... more InVmCouriers are created, resulting in the InVMCourier
list (held by the CourierFactory) growing and growing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira