[jbossts-issues] [JBoss JIRA] Commented: (JBTM-327) Memory leak bug in org.jboss.txbridge.TxBridgeManager

Tue Feb 10 06:50:45 EST 2009

    [ https://jira.jboss.org/jira/browse/JBTM-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12451950#action_12451950 ] 

Jonathan Halliday commented on JBTM-327:
----------------------------------------

Due to the async messaging and timeouts, it's possible you'll wind up in a situation where an attempt is made to remove an entry that has already been removed. In such case removeMappings() should log.warn or fail silent rather than throwing NullPointerException. In future releases this will also apply to crash recovery situations, in which the mapping won't exist as it's not persisted.

WeakRefs can cause GC issues in high load situations, so in general I prefer to avoid them even in situations where concurrency control is not an issue. Best alternative for the paranoid would be a Timer that looked for mappings that outlived the expected tx timeout by some safety interval. Its also feasible to have the bridge expose a 'purge mappings' method by JMX to allow manual cleanup without a need to restart the server.

> 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, 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