Here is the scenario we have <track-statements>true</track-statements> for our datasource. We also have code that wraps Connections and statements and closes resultsets when you close statements, and the same for statements when you close connections. This is code that has been working for quite some time, under jboss 3.2.3 as well as weblogic 5.1 and 7.0.
Since we upgraded to jboss 3.2.4 we started seeing: 2004.07.13 08:54:08.734 EDT WARN [WrappedConnection] Closing a result set you left open! Please close it yourself. and a corresponding stacktrace. Two things are strange about this: 1. We are closing our resultsets 2. Even if I wasn't, that would be ok, becuase I'm closing my statements. Now if you say something like 'you should close your RestultSet', which I don't disagree with and I am actaully doing, I'm going to have to refer you to the jdbc spec which pretty clearly states that the resources opened by statements will be closed when the statement is closed. If you're now saying that I have to take extra steps, then this seems like you're not conforming to the spec. Regarding the statment caching, I don't think that this applies since I am actually closing my resultsets. In summary, there seems to be a bug that is causing WrappedConnection to think that I have not closed resultsets when I actually have. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841911#3841911 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841911 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
