Fixes are available
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
A WebSphere Application server for z/OS Local Communication (LCOM) Client may hang in termination. The LCOM Client, client and server local to the same system using Program Call (PC) / Program Return (PR) communication, may hang after exiting the main(). There is a termination path in the Connection cleanup code that attempts to attach the JVM to the current thread to drive JVM services. The caller of the attach call is waited and the termination of the client address space is hung. The client will have to be cancelled manually.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application server for z/OS * * Local Communication Client may hang in * * termination. * **************************************************************** * RECOMMENDATION: * **************************************************************** A WAS z/OS Client using Local Communication may hang with the following stack trace: CEEOPCW() pthread_cond_wait() j9thread_monitor_enter() allocateVMThread() protectedInternalAttachCurrentThread() j9sig_protect() AttachCurrentThreadAsDaemon() getJavaEnv() BOSS_JavaEnv::getEnv(JavaVM_*)() CF_Local_Connection::cancelAll_io()() CF_Local_Connection_Object_Manager::cleanUp(_jobject*)() CleanUpSessionManager() CleanUpList::call_cleanup_routines(btcb*)() CallCleanUpRoutines(RasExit_Type,btcb*)() RasAtProcessExit() The hang is caused by attempting to attach the JVM to the current thread during termination. In this scenario the calling thread is waited and the client termination is hung.
Problem conclusion
Local Communication termination code has been updated to not drive the code to attach the JVM during termination of the client environment. 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
PI34033
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
2015-02-03
Closed date
2015-02-05
Last modified date
2015-02-05
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