Hi,

did anybody got Hibernate working with Websphere 5.1 and an Oracle Database (we testet 8.1.7 and 9.x)? We are having extreme Problems with stress testing on that environment.

Our Websphere uses OracleConnectionPoolDataSource as implementation. It seems that if more connections are requested as are available in the (WAS) connection pool, the WAS freezez. After the configured time limit for connections we get timeouts for every request.



[01.03.05 11:41:06:428 CET] 17a122f FreePool E J2CA0045E: Die Verbindung ist beim Aufruf der Methode queueRequest für Ressource comp/env/jdbc/XyDataSource nicht verfügbar.
[01.03.05 11:41:06:428 CET] 144f3c9 ConnectionMan E J2CA0020E: Der Connection Pool Manager konnte eine verwaltete Verbindung nicht zuordnen: com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 1800225
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1034)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1720)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:677)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:461)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:241)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:214



When all request got that timeout, the system no more hangs, but really only if no more connections are requested.

We implemented our own "Connection Provider". With counters and tracing we figured out that all connections are closed.

Is there any specific to set in web.xml or ibm-xxx.xmi's ?
Or is any another connection pool implementation running fine?

For information. We did that same stress test on a JBoss (but local installation, so it was much slower). But it handled all connections fine. Even if the pool was configured with min 1 max 2, all request from e.g. 80 Users did result successfully.

Thanks and Greetings

Dennis