Fixes are available
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
WebSphere for z/OS hit an abend S0C4-0004 after a Java dump during the server startup. . Segmentation error: Unhandled exception Type=Segmentation error vmState=0x00000000 J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000035 Handler1=00000048176392A0 Handler2=000000480B13B630 ... JVMDUMP039I Processing dump event "gpf", detail "" at 2013/11/17 17:53:01 - please wait. . and the abend 0C4-0004: PIDS/5655I3500 Program id: 5655I3500 RIDS/BBOOPCRT#L Load module name: BBOOPCRT RIDS/BBOODCTX Csect name: BBOODCTX AB/S00C4 System abend code: 00C4 PRCS/00000004 Abend reason code: 00000004 REGS/C0188 Register/PSW difference for R0C:-0188 RIDS/BBOODCTX#R Recovery routine csect name: BBOODCTX . The 0C4 abend was caused by an attempt to clear the gtid of a non-existent native TaskTransactionInfo. The cleanup path that caused the failure was executed as a result of a misconception on the transaction manager's part about the knowledge of the transaction in the controller region.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Servant region terminates with a 0C4 * * abend in routine BBOODCTX during * * startup. * **************************************************************** * RECOMMENDATION: * **************************************************************** The servant region terminates with a 0C4 abend during servant/application startup. The abend takes place during transaction clean processing in routine BBOODCTX where there was an attempt to clear a transaction id field in a nonexistent object designed to hold task specific transaction information. The cleanup path that led to the failure was executed in error. The thread at the time of the abend shows the following stack: at com/ibm/ws390/tx/NativeGlobalTransactionContext. contextDisassociation at com/ibm/ws390/tx/NativeGlobalTransactionContext. cleanupTransaction at com/ibm/ws390/tx/NativeGlobalTransactionContext.rollback ... at com/ibm/ejs/csi/TransactionControlImpl.postInvoke ... at com/ibm/websphere/startupservice/_AppStartUp_Stub.start at com/ibm/ws/startupservice/StartBeanInfo.start ... at com/ibm/ws/startupservice/StartUpApplication.start The servant region logs show a transaction timeout leading to servant termination. It also shows further transaction processing while the servant awaits termination, but prior to the 0C4 abend: Trace: xxxx/xx/xx xx:xx:xx.xxx xx t=xxxxxx c=UNK key=P8 ... SourceId: com.ibm.tx.jta.impl.EmbeddableTranManagerImpl ExtendedMessage: BBOO0222I: WTRN0041I: Transaction x ... x has been rolled back. Trace: xxxx/xx/xx xx:xx:xx.xxx xx t=xxxxxx c=UNK key=P8 ... Description: Throw CORBA system exception exception id: CORBA::TRANSACTION_REQUIRED minor code: c9c2191f from filename: ./bbgtjexh.cpp The controller region logs show servant region termination being delayed and the 0C4 abend: BBOO0311I ABEND OF SERVANT, ASID=xxxx STOKEN=xxxxxxxxxxxxxxxx, HAS BEEN DEFERRED FOR xx SECONDS STC40450 IEA794I SVC DUMP HAS CAPTURED: DUMPID=xxx REQUESTED BY JOB (xxxxxxxx) DUMP TITLE=xxx, COMPID=5655I3500,ISSUER=BBOR ADMP,ABEND IN PC ROUTINE BBOODCTX BBOO0312I SERVANT, ASID=xxxx STOKEN=xxxxxxxxxxxxxxxx, IS BEING ABENDED BECAUSE OF A TIMEOUT.
Problem conclusion
Code was added to make sure the cleanup path taken under the circumstances shown above is the correct one. APAR PI08306 is currently targeted for inclusion in Fix Packs 8.0.0.9 and 8.5.5.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
PI08306
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-17
Closed date
2014-01-24
Last modified date
2014-01-24
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:
28 April 2022