[JBoss-dev] [ jboss-Bugs-614313 ] TxManager memory leak
Bugs item #614313, was opened at 2002-09-25 10:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 Category: JBossTX Group: v3.2 Status: Closed Resolution: None Priority: 6 Submitted By: Michael Bartmann (bartmann) Assigned to: Adrian Brock (ejort) Summary: TxManager memory leak Initial Comment: The TxManager stores all allocated TransactionImpl instances in a private HashMap (globalIdTx). The only package-private method releaseTransactionImp which would clear them from the HashMap does not seam to be called from anywhere. This is a leak which costs us 100MB per day on a medium trafic server. (Each TransactionImpl itself holds an XIdImpl, a Logger, ...) Regards, Michael Bartmann -- Comment By: Adrian Brock (ejort) Date: 2002-11-04 12:44 Message: Logged In: YES user_id=9459 This has now been applied to HEAD -- Comment By: Adrian Brock (ejort) Date: 2002-10-10 10:05 Message: Logged In: YES user_id=9459 This has been fixed in 3.0 but not 3.2 and HEAD -- Comment By: Infogest (infogest) Date: 2002-10-09 17:02 Message: Logged In: YES user_id=167837 Seams to me that's fixed ... I see that in jb 3.0.3 the method is called throug: TxCapsule - commit,releaseInstance - TransactionImpl-setDone - TxManager-releaseTransactionImpl -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 --- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-614313 ] TxManager memory leak
Bugs item #614313, was opened at 2002-09-25 10:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 Category: JBossTX Group: v3.2 Status: Open Resolution: None Priority: 6 Submitted By: Michael Bartmann (bartmann) Assigned to: Adrian Brock (ejort) Summary: TxManager memory leak Initial Comment: The TxManager stores all allocated TransactionImpl instances in a private HashMap (globalIdTx). The only package-private method releaseTransactionImp which would clear them from the HashMap does not seam to be called from anywhere. This is a leak which costs us 100MB per day on a medium trafic server. (Each TransactionImpl itself holds an XIdImpl, a Logger, ...) Regards, Michael Bartmann -- Comment By: Adrian Brock (ejort) Date: 2002-10-10 10:05 Message: Logged In: YES user_id=9459 This has been fixed in 3.0 but not 3.2 and HEAD -- Comment By: Infogest (infogest) Date: 2002-10-09 17:02 Message: Logged In: YES user_id=167837 Seams to me that's fixed ... I see that in jb 3.0.3 the method is called throug: TxCapsule - commit,releaseInstance - TransactionImpl-setDone - TxManager-releaseTransactionImpl -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-614313 ] TxManager memory leak
Bugs item #614313, was opened at 2002-09-25 12:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 Category: JBossTX Group: v3.2 Status: Open Resolution: None Priority: 6 Submitted By: Michael Bartmann (bartmann) Assigned to: Nobody/Anonymous (nobody) Summary: TxManager memory leak Initial Comment: The TxManager stores all allocated TransactionImpl instances in a private HashMap (globalIdTx). The only package-private method releaseTransactionImp which would clear them from the HashMap does not seam to be called from anywhere. This is a leak which costs us 100MB per day on a medium trafic server. (Each TransactionImpl itself holds an XIdImpl, a Logger, ...) Regards, Michael Bartmann -- Comment By: Infogest (infogest) Date: 2002-10-09 19:02 Message: Logged In: YES user_id=167837 Seams to me that's fixed ... I see that in jb 3.0.3 the method is called throug: TxCapsule - commit,releaseInstance - TransactionImpl-setDone - TxManager-releaseTransactionImpl -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-614313 ] TxManager memory leak
Bugs item #614313, was opened at 2002-09-25 12:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 Category: JBossTX Group: v3.2 Status: Open Resolution: None Priority: 6 Submitted By: Michael Bartmann (bartmann) Assigned to: Nobody/Anonymous (nobody) Summary: TxManager memory leak Initial Comment: The TxManager stores all allocated TransactionImpl instances in a private HashMap (globalIdTx). The only package-private method releaseTransactionImp which would clear them from the HashMap does not seam to be called from anywhere. This is a leak which costs us 100MB per day on a medium trafic server. (Each TransactionImpl itself holds an XIdImpl, a Logger, ...) Regards, Michael Bartmann -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-614313 ] TxManager memory leak
Bugs item #614313, was opened at 2002-09-25 12:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 Category: JBossTX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Michael Bartmann (bartmann) Assigned to: Nobody/Anonymous (nobody) Summary: TxManager memory leak Initial Comment: The TxManager stores all allocated TransactionImpl instances in a private HashMap (globalIdTx). The only package-private method releaseTransactionImp which would clear them from the HashMap does not seam to be called from anywhere. This is a leak which costs us 100MB per day on a medium trafic server. (Each TransactionImpl itself holds an XIdImpl, a Logger, ...) Regards, Michael Bartmann -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
