The current implementation assumes that the AtomicAction instance is around after
termination for status, identification and in the event of heuristics potentially for
management and recovery information (the log still exists on disk at that point and hence
the AA instance can be used to access it). Changing it so that is no longer the case could
have implications throughout the areas of the code. I'd prefer to see what is keeping
hold of the TransactionImple reference and not releasing that, since it appears that is
the root of the leak (assuming we're understanding the reported problem.)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028070#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...