Fixes are available
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
During abnormal termination of a WebSphere servant region, a secondary S0C4 ABEND was encountered by the JVM. The servant region was on its way down due to an SEC3 RSNC9C2198F ABEND, which produced an SVCDUMP, and was caused by +BBOO0220E: J2CA0026E: Method addSync caught javax.transaction.SystemException: ATRBEG Failed, RC = 1841 at com.ibm.ws390.tx.NativeGlobalTransactionContext.create( NativeGlobalTransactionContext.java:245) at com.ibm.ws.tx.jta.TransactionImpl.checkIfNativeTransactional( TransactionImpl.java:1722) at com.ibm.ws.tx.jta.TranManagerSet.registerSynchronization( TranManagerSet.java:520) at com.ibm.tx.jta.impl.EmbeddableTranManagerSet. registerSynchronization(EmbeddableTranManagerSet.java:227) at com.ibm.ejs.j2c.RRSGlobalTransactionWrapper.addSync( RRSGlobalTransactionWrapper.java:232) at com.ibm.ejs.j2c.ConnectionManager.initializeForUOW( ConnectionMan ager.java:2004) at com.ibm.ejs.j2c.ConnectionManager.involveMCInTran( ConnectionMana ger.java:1661) at com.ibm.ejs.j2c.ConnectionManager.allocateConnection( ConnectionM anager.java:1036) at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection( WSJdbcD ataSource.java:669) at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection( WSJdbcD ataSource.java:636) at com.acme.setConnection_DS(BaseDAO.java:168) at com.ibm.ws390.orb.CommonBridge.invoke( CommonBridge.java:1884) at com.ibm.ws390.orb.CommonBridge.getAndProcessWork( CommonBridge.ja va:7191) at com.ibm.ws390.orb.CommonBridge.runApplicationThread( CommonBridge .java:608) at com.ibm.ws.util.ThreadPool$ZOSWorker.run( ThreadPool.java:1951) while trying to register the Resource Adapter with the Synchronization Manager for the current transaction, and threw a ResourceException. com.ibm.ejs.j2c.RRSGlobalTransactionWrapper ------------ A second SEC3 RSNc9c20008 ABEND and SVCDUMP was generated, but then the SOC4 abend in the JVM was detected, and produced a third SVCDUMP. IP STATUS from the third SVCDUMP showed: PSW: 07850401 80000000 00000000 792B3138 Instruction length: 06 Interrupt code: 0010 Failing instruction text: 0000A779 0000E360 60000004 Translation exception address: 0000004B5E9FE800 The translation exception address was determined to be pointing into the (now freemained) STACK storage for the TCB which encountered the original error in Method addSync. At the time of the SOC4, this TCB has exitted - and all native storage has been released - but the JVM still thinks it is active.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0, V8.5, and V9.0. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server for * * z/OS' servant region abnormal * * termination encounters a 00C4 abend * * with reason 00000010. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Websphere Application server for z/OS' servant region encounters a secondary 0C4 abend(ABENDS0C4, ABEND0C4, or 00C4) with reason 00000010 during abnormal termination. The dump shows the following information: Program id: 5655I3500 Load module name: CBSERIES Csect name: CBSERIES System abend code: 00C4 Abend reason code: 00000010 Recovery routine csect name: BBORLEXT The 0C4 might happen if a thread attempts to traverse the thread's stack frame that is no longer available. For example, the dump might show the thread experiencing the condition to doing the following: Traceback: DSA Entry 1 walkJNICallInFrame 2 walkStackFrames 3 getStackTraceForThread 4 RUNJAVATHREAD 5 javaProtectedThreadProc ...
Problem conclusion
Code was updated to prevent the 0C4 condition. APAR PI69131 is currently targeted for inclusion in Fix Packs 8.0.0.13, 8.5.5.12, and 9.0.0.3 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI69131
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-13
Closed date
2016-11-04
Last modified date
2016-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
03 May 2022