When running performance testing in the perf environment we saw 18 of these. This is while in the environment the product and/or database is in a VERY bad state performance wise. 2011-08-04 14:07:56,799 WARN [org.jboss.resource.adapter.jdbc.WrappedConnection] Closing a result set you left open! Please close it yourself. java.lang.Throwable: STACKTRACE at org.jboss.resource.adapter.jdbc.WrappedStatement.registerResultSet(WrappedStatement.java:909) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:343) at org.rhq.enterprise.server.measurement.MeasurementScheduleManagerBean.returnSchedulesFor(MeasurementScheduleManagerBean.java:984)
Mike, can you reproduce this?
I previously fixed this. We should do another coverity run monday. But lets close this one out and reopen new bugs after the new coverity runs. commit fece00f1862612104aef1439fb02c4f7a35d797e Author: Robert Buck <rbuck> Date: 2011-09-26 08:54:05 -0400 Oracle em cites lots of open cursor issues; fix open cursor leaks by closing result sets and prepared statements in finally blocks.
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
marking VERIFIED BZs to CLOSED/CURRENTRELEASE