Problem

When using an asynchronous solution (using JMS), messages are sent to the RCB/IB without waiting for a response. The front-office post a request message on a request queue. The response of the Risk Control Builder (RCB)/Interaction Builder (IB) is posted on a response queue, and the front-office checks on this queue whether an answer is available to the request made earlier. When used in call center/web environment, multiple requests are sent at the same time (dependent on the number of call center seats or web site visitors). This causes multiple requests to be put on the request queue of the RCB/IB. Because RCB/IB is a J2EE application, multiple threads are started to be able to process requests in parallel fashion. In some implementations the LOG database is used to store the results of the scoring process. This database can be used in the analytical environment to improve the current models. Problem: If the RCB/IB is faced with a load of messages (20-30 requests) at the same time and production logging is enabled, the RCB/IB cause the LOG database to hang. The only solution is to restart the database server containing the LOG database. The SPSS and Websphere log files gives the following exceptions: 2008-11-07 12:42:47,375 ERROR [Default : 27] - Failed to obtain JDBC connection from the application server pool com.ibm.websphere.ce.cm.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 180000 at com.ibm.ws.rsadapter.AdapterUtil.toSQLException(AdapterUtil.java:1233) at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:444) The SystemOut.log files contains the following error information: [11/7/08 12:42:47:734 GMT] 000002a5 FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/CIMDB. [11/7/08 12:42:47:656 GMT] 0000030b ExceptionUtil E CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "findByPrimaryKey". Exception data: com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction rolled back; nested exception is: javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout The SQL Server database is hanging and needs to be restarted to correct the situation. The PES server requires a restart as well.