Fixes are available
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
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
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
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
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
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
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 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
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
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
WAS has an exit that runs at process termination that attempts to detect if there are hung threads. Normally, process termination happens because our main TCB calls the C++ exit() function, at which point the main TCB is the only WAS TCB that is left. Our hung thread detection iterates over all TCBs in the address space and if there are any WAS TCBs other than the main thread left, we ABEND the region due to a hung thread. In this case, the fact that a thread other than the main thread called System.exit(...) confused our hung thread detection code. This is NOT actually a hung thread. The hung thread detection code is actually detecting the presence of TCB 9C7080, which is the thread that CALLED System.exit(...). So to reiterate, there is NOT a hung thread. This is a case of our hung thread detection getting confused by the fact that a TCB other than our main TCB droves the process exit routine.
Local fix
The dump for this diagnostic ABEND can be disabled by setting the WAS environment variable suppress_hung_thread_dump=1 and the ABEND itself can be completely disabled by setting suppress_hung_thread_abend=1
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0, V8.0, and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Certain error conditions result in * * the immediate termination of the * * WebSphere Application Server for z/OS * * Control or Servant region. * **************************************************************** * RECOMMENDATION: * **************************************************************** As part of the handling of certain unexpected exceptions WebSphere is deliberately terminating the region. An example stack trace might look like this. void java/lang/Shutdown.halt0(int) (Native Method) void java/lang/Shutdown.halt(int) source: Shutdown.java:116 void java/lang/Shutdown.exit(int) source: Shutdown.java:190 void java/lang/Runtime.exit(int) source: Runtime.java:90 void java/lang/System.exit(int) source: System.java:299 Object com/ibm/ws390/orb/ORB$1.run() source: ORB.java:392 Object com/ibm/ws/security/util/AccessController.doPrivileged(ja va.security.PrivilegedAction) source: AccessController.java:63 void com/ibm/ws390/orb/ORB.set_parameters(String[], java.util.Pr operties) source: ORB.java:389 org.omg.CORBA.ORB org/omg/CORBA/ORB.init(String[], java.util.Pro perties) source: ORB.java:364 org.omg.CORBA.ORB javax/management/remote/rmi/RMIConnector.resol veOrb(java.util.Map) source: RMIConnector.java:1721 javax.management.remote.rmi.RMIServer javax/management/remote/rm i/RMIConnector.findRMIServer(javax.management.remote.JMXServiceU RL, java.util.Map) source: RMIConnector.java:1851 void javax/management/remote/rmi/RMIConnector.connect(java.util. Map) source: RMIConnector.java:255 javax.management.remote.JMXConnector javax/management/remote/JMX ConnectorFactory.connect(javax.management.remote.JMXServiceURL, java.util.Map) source: JMXConnectorFactory.java:248 void com/ibm/ws/management/connector/jsr160rmi/JSR160RMIConnecto rClient.reconnect(java.util.Properties) source: JSR160RMIConnec torClient.java:284 void com/ibm/ws/management/connector/jsr160rmi/JSR160RMIConnecto rClient.reconnect() source: JSR160RMIConnectorClient.java:178 void com/ibm/ws/management/connector/jsr160rmi/JSR160RMIConnecto rClient.<init>(java.util.Properties) source: JSR160RMIConnector Client.java:168 Object sun/reflect/NativeConstructorAccessorImpl.newInstance0(re flect.Constructor, Object[]) (Native Method) Object sun/reflect/NativeConstructorAccessorImpl.newInstance(Obj ect[]) source: NativeConstructorAccessorImpl.java:44 Object sun/reflect/DelegatingConstructorAccessorImpl.newInstance (Object[]) source: DelegatingConstructorAccessorImpl.java:27 Object java/lang/reflect/Constructor.newInstance(Object[]) sour ce: Constructor.java:516
Problem conclusion
Immediate termination of the region has been determined to be too strict for all cases. Code has been added to avoid terminating the region immediately and instead to propagate the error back to the caller for more appropriate handling. Depending on the scenario, termination may still occur, but in other cases the region may be able to recover. APAR PI14978 is currently targeted for inclusion in Fix Packs 7.0.0.35, 8.0.0.10, 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
PI14978
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-02
Closed date
2014-05-23
Last modified date
2015-01-15
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
R700 PSY UI21695
UP14/10/10 P F410
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:
28 April 2022