IBM Support

PM71182: STOP HANGS, NO OTHER INDICATIONS OF STOP PROCESSING

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a stop is issued there are no other indications of the
    stop being processed other that the stop message in the CR job
    log. This is prior even to the jvm being told to terminate.
    It was found that there were no active transactions but there
    were Activities active. Activities can span a very long time
    frame. They can include multiple tranactions which are
    normally much shorter. The wait on Activities is to be
    addressed. Sample message to identify Activities follows.
    .
     Trace: 2012/06/30 00:01:43.404 01 t=9B1AD0 c=UNK key=S2
    (04064028)
       Description: traceActivityRegistry
       Number of Traced Activities: 2
    .
     Trace: 2012/06/30 00:07:58.952 01 t=9B1AD0 c=UNK key=S2
    (04064028)
       Description: traceActivityRegistry
       Number of Traced Activities: 2
    .
    

Local fix

  • The server must be cancelled to terminate.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM WebSphere Application       *
    *                 Server V6.1, V8.0, and V8.5 for z/OS         *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      Control region hung after a stop        *
    *                      command was issued.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The stop processing for a server on z/OS waits for current
    requests, Transactions, and Activities to complete before
    shutting down.
    Activities, by design, are long running units of work.  An
    activity may take days or weeks to complete.  The controller
    was waiting for Activities to complete before progressing with
    the shutdown of the server.
    

Problem conclusion

  • Code has been modified in the stop command function to allow the
    shutdown of the server when there are no active requests or
    Transactions.  Active Activities will not inhibit the server
    from shutting down from a stop command.
    
    APAR PM71182 is currently targeted for inclusion WebSphere
    Application Server Fix Pack 7.0.0.27.
    
    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

    PM71182

  • 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

    2012-08-20

  • Closed date

    2012-12-20

  • Last modified date

    2013-02-04

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

    PM69213

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

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK90578

       UP13/01/18 P F301

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