[jbossts-issues] [JBoss JIRA] Updated: (JBTM-327) Memory leak bug in org.jboss.txbridge.TxBridgeManager
[
https://jira.jboss.org/jira/browse/JBTM-327?page=com.atlassian.jira.plugi...
]
Brice Ruth updated JBTM-327:
----------------------------
Attachment: JBTM-327_patch.txt
Per Red Hat Support Case 263468, attaching proposed patch to fix memory leak for
InboundBridge and Xids in TxBridgeManager.
+Needs review to determine if changes to BridgeParticipantAT are calling removeMappings()
at the appropriate time and if this covers all the necessary cleanup cases.
+Recommendation: would it be beneficial to make the entries in the concurrent hashmaps
"weak" references, in case any border condition fails to remove a mapping? Or
would this only work if a WeakHashMap were used (which isn't available in a Concurrent
flavor until possibly Java 7)?
Memory leak bug in org.jboss.txbridge.TxBridgeManager
-----------------------------------------------------
Key: JBTM-327
URL: https://jira.jboss.org/jira/browse/JBTM-327
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: WS-T Implementation
Environment: JBoss-4.2.1.GA, JBossTS-4.2.3.SP7
Reporter: Pavel Kadlec
Fix For: 4.7
Attachments: JBTM-327_patch.txt
There is no way to dispose InboundBridge from memory in class
org.jboss.txbridge.TxBridgeManager. There should be some method that does it. That method
should be called from org.jboss.txbridge.BridgeParticipantAT when commit or rollback is
received.
--
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