Fixes are available
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
In a mixed cell environment with Daemon at V7 of WebSphere Application Server, and Node at V6.1, a V6.1 application server servant region (SR) may terminate unexpectedly with abend S0C4. This problem is more likely to occur during STOP processing of the server, but it could also occur during normal server runtime. In the reported case, a TDUMP was taken for the 0C4 abend. The failing thread had the following traceback: Native traceback: _TDUMP j9dump_create doSystemDump protectedDumpFunction j9sig_protect runDumpFunction triggerDumpAgents dumpCrashData j9sig_protect structuredSignalHandler masterSynchSignalHandler __zerro __zerros CEEHDSP CEEOSIGJ CELQHROD CEEOSIGG CELQHROD CurrentRequestLanguage::btcb_Java_RMI_On() Java_com_ibm_ws390_orb_ClientDelegate_createRequestCFW RUNJAVATHREAD javaProtectedThreadProc j9sig_protect javaThreadProc thread_wrapper CELQPCMM Java traceback: com/ibm/ws390/orb/ClientDelegate.createRequestCFW com/ibm/ws390/orb/ClientDelegate.createRequest com/ibm/ws390/orb/ClientDelegate.request org/omg/CORBA/portable/ObjectImpl._request ObjectImpl.java:458 com/ibm/ws/management/_ControlAdminService_Stub.handleServantNot ifications _ControlAdminService_Stub.java:247 com/ibm/ws/management/event/PushToControlNotificationSender.hand leNotifications PushToControlNotificationSender.java:93 com/ibm/ws/management/event/PushRemoteSender.pushNotifications PushRemoteSender.java:56 com/ibm/ws/management/event/AbstractPushRemoteSender.alarm AbstractPushRemoteSender.java:191 com/ibm/ejs/util/am/_Alarm.run _Alarm.java:90 com/ibm/ws/util/ThreadPool$Worker.run . In a second reported case, the nodeAgent hit an abend A78 RC=10 during the Freemain to release storage related to control blocks BBOOTRD and BBO3BTCB. The problem occurred because, at first, more storage was released than intended due to an invalid length of TRDI (bbootrdi.mac). Subsequent storage release resulted an abend A78 RC=10 because the storage to be freed overlaps the free storage which was incorrectly released earlier. In a third reported case, the abend surfaced while starting applications in a WebSphere V6.1 application server as part of migrating to a newer release of WebSphere. As a workaround, the abend was avoided by disabling autostart of applications in the deployment manager on server startup to allow the WebSphere V6.1 application server to start. Upon completing the migration, autostart of applications could be re-enabled in the newer WebSphere release.
Local fix
See third reported case in problem description if applicable.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 occurred in WebSphere * * for z/OS Application Server Servant * * Region when running in a mixed * * cell environment. * **************************************************************** * RECOMMENDATION: * **************************************************************** The servant (SR) is running daemon level code for its Task related recovery code. The size of a task related piece of storage has changed between the daemon level of code and the node level of code. The storage is internally called the TRDI (bbootrdi.mac). In the SR, the node level of code obtains and initializes the TRDI, but the daemon level of code releases the TRDI. This resulted in releasing more storage than was intended, and corrupted structures in the related storage. This caused the ABENDS0C4 in CurrentRequestLanguage::btcb_Java_RMI_On() which attempts to write into the TRDI. Also, to confirm this problem, ABEND378 REASON=24 abends have been observed in the LOGREC.
Problem conclusion
Code has been modified in the servant environment to use the node level of code for task recovery. APAR PM04551 requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/library The following changes to the WebSphere Application Server Version 6.1 Information Center will be made available in May, 2010. The table "WebSphere Application Server for z/OS abend codes" that is contained in the topic "Abend reason codes" will be updated to include the following new EC3 ABEND reason code: Abend Code Abend Reason Explanation Suggested Action EC3 04010011 Internal IBM Internal Only product error APAR PM04551 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.31 of WebSphere Application Server V6.1. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM04551
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-07
Closed date
2010-01-28
Last modified date
2011-09-01
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
R610 PSY UK56378
UP10/05/08 P F005
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
29 December 2021