Hi, I have thus far built 20+ controls that extend JDBCControl, These JDBCContorls are used by dao objects. These dao objects are in turn custom beehive controls. The problem that I am running into is that the JDBCControls are not being cleaned up until the parent custom control is destroyed. I have gone so far as to null the control instance to force the onRelease() method to be fired.
I need a way to force the connection to be released on demand. One of my more advanced JUnit tests is exhausting the connection pool and is failing. Any help would be greatly appreciated. -- View this message in context: http://www.nabble.com/Releasing-JDBCControl-connections-early-tp18078694p18078694.html Sent from the Beehive - User mailing list archive at Nabble.com.
