Fix (APAR): JR25612 Status: Fix Release: 6.0.1.3 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 6484 Date: 2007-01-17 Abstract: JCA binding does not close connection when JCA adapter throws an exception. So the connection leak can cause no available connections and WPS hang. Description/symptom of problem: JR25612 resolves the following problem: ERROR DESCRIPTION: Under certain circumstances, if a failure occurs while an events in progress, it may not be recoverable and the event may not be available in Failed Events Manager. The Process Server will give transaction timeout errors and hang. The module may need to be restarted to continue processing of new requests. LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.1.x users PROBLEM DESCRIPTION: JCA binding does not close connection when JCA adapter throws an exception. So the connection leak can cause no available connections and WPS hang. RECOMMENDATION: None In the JCA adapter component, SCA J2C binding, when the adapter throws an exception the existing connections are not being closed. The reason exception is thrown is since the connections are not closed and the pool size has reached max limit container waits forever to allocate a connection and hence transactions timeout, only when the connections are closed they go back to the pool. So no connections are available in the pool for the container to a given transaction and can cause WPS hang. You may see the following exception: com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException: Connection not available at com.ibm.ejs.j2c.poolmanager.FreePool. createOrWaitForConnection(FreePool.java:1310) at com.ibm.ejs.j2c.poolmanager.PoolManager. reserve(PoolManager.java:2114) ... PROBLEM CONCLUSION: With the fix, connections will be closed by SCA JCA binding when an exception occurs JCA adapter. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system. Also download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server Additional Information: