Description of problem: There is query to determine which schedules do not have baselines. This is executed as a native, SQL query. The method MeasurementBaselineManagerBean.getSchedulesWithoutBaselines() obtains a JDBC connection to execute the query but fails to close it. I saw the following errors in my server.log after it was running for a few days. 12:38:29,277 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject] (EJB default - 1) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:458) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:395) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:782) . . . Caused by: org.postgresql.util.PSQLException: FATAL: connection limit exceeded for non-superusers at org.postgresql.core.v3.ConnectionFactoryImpl.readStartupMessages(ConnectionFactoryImpl.java:572) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:177) at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:64) at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:136) at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:29) at org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:21) at org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:31) at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24) at org.postgresql.Driver.makeConnection(Driver.java:393) at org.postgresql.Driver.connect(Driver.java:267) at java.sql.DriverManager.getConnection(DriverManager.java:620) [rt.jar:1.6.0_24] at java.sql.DriverManager.getConnection(DriverManager.java:200) [rt.jar:1.6.0_24] at org.postgresql.ds.common.BaseDataSource.getConnection(BaseDataSource.java:95) at org.postgresql.xa.jdbc3.AbstractJdbc3XADataSource.getXAConnection(AbstractJdbc3XADataSource.java:54) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:441) ... 284 more Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I committed the fix to master. commit hash: 7776a638
Moving to ON_QA for testing.
Is it possible to make an assumption about the date of the next release, which will come with this bug fix?
@Selim this should be in next release of product and community.
@Simeon: Actually i would like to know the release date of the next release. We wait this fix urgently, becaus our RHQ instance became inaccessible every two days and we have to restart it each time.
Do we have an ETA for RHQ 4.10.0, or would we be able to patch 4.9.0 in order to fix this problem?
Bulk closing of 4.10 issues. If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.