Description of problem: I am hitting ResourceException: IJ000655 when my JON server runs +- 2 days. After this amount of time, server is unable to log me in through UI and server log is full of messages like: Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/RHQDS at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:390) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464) at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139) ... 86 more Caused by: javax.resource.ResourceException: IJ000655: No managed connections available within configured blocking timeout (300 00 [ms]) When I stopped server, I got a lot of these warnings 22:40:09,241 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject] (MSC service thread 1-1) IJ000615: Destroying active connection in pool: RHQDS (org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@8b3d9a0) so it looks like there is a bug in code that does not close connections properly. Version-Release number of selected component (if applicable): JON 3.2.ER1 How reproducible: so far always Additional info: I am hitting this behavior on both Windows x64 and Linux environments.
I think that this is the same as bug 1009640 which will be fixed in ER2.
Setting target according to comment 2
verified on JON 3.2.0.ER02