IBM Support

PI34033: WAS Z/OS LOCAL COMMUNICATION CLIENT MAY HANG IN TERMINATION.

Subscribe

You can track all active APARs for this component.

 

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

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022