Greetings all,
first off - all the different hints of how not to leave open connections at webapp shutdown (ie using DBCP in Tomcat and supply JNDI DataSource to OJB, or explicitly calling release methods in OJB at shutdown) are equally good ways of doing.
Danilo Tommasina wrote:
however it could be that the DBCP connection factory implementation in OJB 1.0.1 does not closes the connections when calling the methods above.
I think Martin fixed this in OJB 1.0.2
That's correct. So if you are using DBCP as connection factory in OJB.properties, releaseAllResources will not close the connections in v1.0.1 or earlier.
Finally, for the sake of clarity: using a DBCP Connection pool in Tomcat and supplying a JNDI DataSource to OJB is not affected by this since the Connection management is then entirely left to Tomcat.
Regards, Martin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
