Your assurance is good enough for me. I'll check the WL mailing lists, with which I'm intimately aware for the very reasons you just described.
Cheers, Dave -----Original Message----- From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 7:37 PM To: Turbine Torque Users List Subject: Re: Not releasing connections? on 4/24/02 6:44 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > That's encouraging! :) So, *could* there by an issue w/ Torque not > releasing connections? I see in my BaseXXXPeer classes calls to > Torque.releaseConnection, and I also see this in the db methods in BasePeer. > This method delegates to the releaseConnection method on ConnectionPool, > which callse close() on the connection if it's still valid. All of this > looks fine, though I guess I have to trust that releaseConnection is being > called in all the places it should be. I have a 99.99999% confidence that it is releasing all connections. That code has been pretty well pounded over years. > In point of fact, I'm not quick to point fingers at Torque, and actually > suspect that it's running fine, but that I've got some configuration issue > with WL. Still, it seems likely enough that another Torque maven would've > seen this with Weblogic, so I thought I'd give it a shot in this mailing > list. I gave up using WL years ago because I found so many bugs (including security related bugs) in it that I couldn't rely on it any longer. I spent more time figuring out workarounds than moving forward with development. Eventually, I switched to working on Jserv and haven't gone back to weblogic. One could say that WL was the very reason why I gave up on commercial closed source software. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
