Bug 728335

Summary: Failed to close result sets that should have been closed yourself.
Product: [Other] RHQ Project Reporter: Robert Buck <rbuck>
Component: Core ServerAssignee: Robert Buck <rbuck>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.1CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-07 19:29:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robert Buck 2011-08-04 18:20:13 UTC
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)

Comment 1 Charles Crouch 2011-08-11 04:03:37 UTC
Mike, can you reproduce this?

Comment 2 Robert Buck 2011-10-07 15:07:53 UTC
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.

Comment 3 Mike Foley 2012-02-07 19:29:50 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE

Comment 4 Mike Foley 2012-02-07 19:30:24 UTC
marking VERIFIED BZs to CLOSED/CURRENTRELEASE