-
1. Re: Managed Connections not returned into pool
adrian.brock Oct 26, 2003 9:55 AM (in response to tom_doehler)I've fixed the leak, thanks for drawing it to my attention.
You shouldn't be attempting to do more work in a transaction
that is (marked) rollbacked.
This kind of thing typically happens when applications attempt
to do the work of the system.
e.g.
try
{
// Do work
}
catch (EJBException e)
{
// Doing work here is bad
}
Even worse is code I've seen:
try
{
// Do work
}
catch (EJBException e)
{
log.warn("Error", e);
// Don't rethrow and try to continue :-(
}
Regards,
Adrian -
2. Re: Managed Connections not returned into pool
moomin Dec 29, 2003 2:48 AM (in response to tom_doehler)Hi Adrian,
I have read your reply to Tom at 26 Oct 2003 for the Managed Connections not returned into pool problem, I would like to ask you do your fix included in jboss 3.0.8?
Thanks
Moomin
29 Dec 2003 -
3. Re: Managed Connections not returned into pool
adrian.brock Dec 29, 2003 3:58 AM (in response to tom_doehler)No, 3.2.3
Regards,
Adrian -
4. Re: Managed Connections not returned into pool
moomin Dec 29, 2003 8:35 PM (in response to tom_doehler)Dear Adrian,
Thank you for your prompt reply.
As I encounter this problem at my customer production site, we need to perform SIT and UAT for the upgrading the JBoss application from 3.0.X to 3.2.X. Thus, I would like to ask it is possible to put the fix on Jboss 3.0.x.
Regards,
Moomin -
5. Re: Managed Connections not returned into pool
adrian.brock Dec 30, 2003 12:09 PM (in response to tom_doehler)This is the bug fix. The 3.0 implementation is different to the 3.2 implementation.
You will have to apply it to the LocalTxConnectionManager and the XATxConnectionMananger
depending upon which you using.
http://cvs.sourceforge.net/viewcvs.py/jboss/jbosscx/src/main/org/jboss/resource/connectionmanager/TxConnectionManager.java?r1=1.15&r2=1.16
Regards,
Adrian