WARN [WrappedConnection] Closing a statement you left open, please do your own housekeeping

[jeff]

I keep getting this warning and it makes me wonder what kind of
thrashing is going on underneath.

This error is thrown to users of jboss 3.2.2 because of their "bug fix"
that introduced the tag eager-release to their descriptive datasource
declarations. I happens when my connection is not closed when I exit
the method that executes the query. But I want to use it for
transactions over multiple tables using
conn.autocommit(false)...con.commit().

I would like to get rid of it. A google shows me that this was default
eager-release=true setting in jboss 3.2.2. Unfortunately I inherited
this project and it is using JNDI, not descriptive (xml) JDBC
datasource. I know that if I had a datasource declared that I could
specify:
<eager-release> false</eager-release>
But this feature is not available via my Connection object.

Does anyone know how I can set eager-release to false using jndi?

Thanks

[pthis...@gmail.com]

Even when using JNDI there still should be a *-ds.xml file in the
deploy directory that registers the resource in the JNDI tree.

As an aside, since you are in a full container why not wrap your save
process with a UserTransaction and clean up the connection after each
query and ensure no connection leaks.