IBM Support

PM04043: SERVER DOES NOT COME DOWN AFTER STOP WAS ISSUED. CONTROLLER IS WAITING FOR UNOWNED LOCK

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When Stop is issued on a server, some servants may not come down
    and server appears hang.  Servant region will show WebSphere
    main thread which PCed to Controller asid and is waiting for
    Controller's response:
    
    com/ibm/ws390/recoverylog/spi/ServantRequestDispatcher.
                                                 driveRequestNative
    com/ibm/ws390/recoverylog/spi/ServantRequestDispatcher.driveRequ
      estNative      ServantRequestDispatcher.java
    com/ibm/ws390/recoverylog/spi/ServantRequestDispatcher.driveRequ
      est            ServantRequestDispatcher.java:63
    com/ibm/ws390/recoverylog/spi/ServantRecoveryLogImpl.closeLog
                     ServantRecoveryLogImpl.java:190
    com/ibm/ws/cscope/CScopeComponentImpl.destroy
                     CScopeComponentImpl.java:476
    com/ibm/ws/runtime/component/ContainerImpl.destroyComponents
    com/ibm/ws/runtime/component/ContainerImpl.destroy
    com/ibm/ws/runtime/component/ApplicationServerImpl.destroy
    com/ibm/ws/runtime/component/ContainerImpl.destroyComponents
    com/ibm/ws/runtime/component/ContainerImpl.destroy
    com/ibm/ws/runtime/component/ServerImpl.destroy
    com/ibm/ws/runtime/WsServerImpl.stop
    com/ibm/ws/runtime/WsServer.stop
    com/ibm/ws390/orb/CommonBridge.pre_deregister_Term
    com/ibm/ws390/orb/ORBEJSBridge.pre_deregister_Term
    
    One or more controller threads will have the following
    traceback:
    
    java/lang/Object.wait
    com/ibm/ws/recoverylog/spi/Lock.attemptExclusiveLock
             Lock.java:340
    com/ibm/ws/recoverylog/spi/MultiScopeRecoveryLog.keypoint
             MultiScopeRecoveryLog.java:1585
    com/ibm/ws/recoverylog/spi/MultiScopeRecoveryLog.closeLog
             MultiScopeRecoveryLog.java:1101
    com/ibm/ws/recoverylog/spi/RecoveryLogImpl.closeLog
             RecoveryLogImpl.java:83
    com/ibm/ws390/recoverylog/spi/ControllerRequestProcessor.driveRe
      coveryLogMethod ControllerRequestProcessor.java:227
    com/ibm/ws390/recoverylog/spi/ControllerRequestProcessor.process
             ControllerRequestProcessor.java:132
    
    The threads in the controller with above traceback are all
    waiting for an "unowned" lock:
    
    sys_mon_t:0x672A8298 infl_mon_t: 0x672A82D8:
      com/ibm/ws/recoverylog/spi/Lock@41B029B0/41B029BC: <unowned>
         Waiting to be notified:
            "WebSphere t=009c0a48" (0x5CAAB900)
            "WebSphere t=009c0608" (0x5CAABD00)
            "WebSphere t=009b8e88" (0x5CB32C00)
            "WebSphere t=009ba360" (0x5CB33400)
            "WebSphere t=009b8488" (0x5CC8A300)
            "WebSphere t=009ba9c0" (0x5CC99E00)
    

Local fix

  • cancel the application server.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Users of IBM WebSphere Application       *
    *                 Server on z/OS                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Server cannot stop because controller   *
    *                      waiting for an unowned lock.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When Stop is issued on a server, some servants may not come down
    
    
    
    and server appears hung.  Servant region will show WebSphere
    main thread which PCed to Controller asid and is waiting for
    Controller's response:
    
    com/ibm/ws390/recoverylog/spi/ServantRequestDispatcher.
    driveRequestNative
    com/ibm/ws390/recoverylog/spi/ServantRequestDispatcher.driveRequ
    
    
    
    estNative      ServantRequestDispatcher.java
    com/ibm/ws390/recoverylog/spi/ServantRequestDispatcher.driveRequ
    
    
    
    est            ServantRequestDispatcher.java:63
    com/ibm/ws390/recoverylog/spi/ServantRecoveryLogImpl.closeLog
    ServantRecoveryLogImpl.java:190
    com/ibm/ws/cscope/CScopeComponentImpl.destroy
    CScopeComponentImpl.java:476
    com/ibm/ws/runtime/component/ContainerImpl.destroyComponents
    com/ibm/ws/runtime/component/ContainerImpl.destroy
    com/ibm/ws/runtime/component/ApplicationServerImpl.destroy
    com/ibm/ws/runtime/component/ContainerImpl.destroyComponents
    com/ibm/ws/runtime/component/ContainerImpl.destroy
    com/ibm/ws/runtime/component/ServerImpl.destroy
    com/ibm/ws/runtime/WsServerImpl.stop
    com/ibm/ws/runtime/WsServer.stop
    com/ibm/ws390/orb/CommonBridge.pre_deregister_Term
    com/ibm/ws390/orb/ORBEJSBridge.pre_deregister_Term
    
    One or more controller threads will have the following
    traceback:
    
    java/lang/Object.wait
    com/ibm/ws/recoverylog/spi/Lock.attemptExclusiveLock
    Lock.java:340
    com/ibm/ws/recoverylog/spi/MultiScopeRecoveryLog.keypoint
    MultiScopeRecoveryLog.java:1585
    com/ibm/ws/recoverylog/spi/MultiScopeRecoveryLog.closeLog
    MultiScopeRecoveryLog.java:1101
    com/ibm/ws/recoverylog/spi/RecoveryLogImpl.closeLog
    RecoveryLogImpl.java:83
    com/ibm/ws390/recoverylog/spi/ControllerRequestProcessor.driveRe
    
    
    
    coveryLogMethod ControllerRequestProcessor.java:227
    com/ibm/ws390/recoverylog/spi/ControllerRequestProcessor.process
    
    
    
    ControllerRequestProcessor.java:132
    
    The threads in the controller with above traceback are all
    waiting for an "unowned" lock:
    
    sys_mon_t:0x672A8298 infl_mon_t: 0x672A82D8:
    com/ibm/ws/recoverylog/spi/Lock@41B029B0/41B029BC: <unowned>
    Waiting to be notified:
    "WebSphere t=009c0a48" (0x5CAAB900)
    "WebSphere t=009c0608" (0x5CAABD00)
    "WebSphere t=009b8e88" (0x5CB32C00)
    "WebSphere t=009ba360" (0x5CB33400)
    "WebSphere t=009b8488" (0x5CC8A300)
    "WebSphere t=009ba9c0" (0x5CC99E00)
    
    This situation was caused by the recovery service resuming
    internal locks that had not been suspended, resulting in
    threads waiting indefinitely.
    

Problem conclusion

  • Ensure that recovery service only resumes valid internal locks.
    
    APAR PM04043 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.9 of WebSphere Application Server V7.0.
    
    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

    PM04043

  • 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

    2009-12-22

  • Closed date

    2010-03-01

  • Last modified date

    2010-04-03

  • APAR is sysrouted FROM one or more of the following:

    PK96860

  • 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 UK55155

       UP10/03/26 P F003

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.

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

Document Information

Modified date:
10 February 2022