-
1. Re: jboss 7 connection close does not release statement
jaikiran May 24, 2013 12:03 AM (in response to d3ni5)Please post the relevant code, configurations (like datasource) and the subsequent exception stacktraces that you see.
-
2. Re: jboss 7 connection close does not release statement
jesper.pedersen May 24, 2013 8:38 AM (in response to d3ni5)1 of 1 people found this helpfulBecause you have a leak - use <track-statements>true</track-statements> + make sure that use-ccm="true" + <cached-connection-manager debug="true"/>, and are using WildFly 8/Alpha1
-
3. Re: jboss 7 connection close does not release statement
d3ni5 May 30, 2013 11:55 AM (in response to d3ni5)WildFly8/Alpha is not an option for production - i have a requirement to extend app support to EAP601 so i use following <track-statements>true</track-statements> + make sure that use-ccm="true" + <cached-connection-manager debug="true"/> settings and fixed jdbc resource management.
The one thing i dont understand - statement.close() should close associated resultSet (http://docs.oracle.com/javase/6/docs/api/java/sql/Statement.html#close()) "When a Statement object is closed, its current ResultSet object, if one exists, is also closed."
Why JBoss is still complaining about unclosed resultset in case the statement is closed ?