[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: Transaction bridging bug?

And another possible bug is leaking memory bug.... org.jboss.txbridge.TxBridgeManager should contain method similar to this one | public synchronized static void disposeInboundBridge(String externalTxId) { | | log.trace("disposeInboundBridge()"); | | Xid xid = txIdMappings.remove(externalTxId); | if (xid == null) { | log.error("inconsistency: null jta xid"); | return; | } | | InboundBridge inboundBridge = inboundBridgeMappings.remove(xid); | | if (inboundBridge == null) { | log.error("inconsistency: null inbound bridge"); | return; | } | | try { | | inboundBridge.stop(); | } catch (Exception e) { | e.printStackTrace(); | } | } | In my opinion method similar to method above should be called by BridgeParticipantAT when participant commits or rolls back. Somebody must dispose InboundBridge from maps in TxManagerBridge.... Pavel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129593#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...