This content has been marked as final.
Show 5 replies
-
1. Re: JDBCStore and JDBCImple: connection leak?
marklittle Jan 16, 2009 6:40 AM (in response to mauromol)Can you not close them in your JDBCAccess implementation?
-
2. Re: JDBCStore and JDBCImple: connection leak?
mauromol Jan 16, 2009 6:57 AM (in response to mauromol)"mark.little@jboss.com" wrote:
Can you not close them in your JDBCAccess implementation?
This is what I am doing now... However there's no hint in accessor or JDBCAccess documentation that says that the connections used by the Object Store are never closed (except when reconnecting, to get another one). One could also think that putConnection is used by the object store when the connection is no longer used so that it can be closed by the accessor, but:
- the Object Store closes it by itself before calling putConnection
- in any case, putConnection is called only when reconnecting
- so one connection will always be kept and not returned... if JBossTS is shut down, that connection is leaked.
May I open a new JIRA?
Mauro. -
3. Re: JDBCStore and JDBCImple: connection leak?
mauromol Jan 16, 2009 6:59 AM (in response to mauromol)"mark.little@jboss.com" wrote:
Can you not close them in your JDBCAccess implementation?
By the way: what I am doing is to register a "hook" in my webapp shutdown to close all the connection given away by my JDBCAccess implementation on webapp shutdown. So, all connections returned by getConnection() are tracked down by JDBCAccess in order to do such cleanup.
Mauro. -
4. Re: JDBCStore and JDBCImple: connection leak?
marklittle Jan 16, 2009 7:39 AM (in response to mauromol)Sounds reasonable. I've created a feature request issue. Not sure if/when we'll get to this because there may be backward compatibility issues, particularly when running embedded.
-
5. Re: JDBCStore and JDBCImple: connection leak?
mauromol Jan 16, 2009 8:22 AM (in response to mauromol)"mark.little@jboss.com" wrote:
Sounds reasonable. I've created a <a href="https://jira.jboss.org/jira/browse/JBTM-465">feature request</a> issue. Not sure if/when we'll get to this because there may be backward compatibility issues, particularly when running embedded.
Thank you Mark!
Mauro.