IBM Support

PM69213: STOP HANGS, NO OTHER INDICATIONS OF STOP PROCESSING

Fixes are available

8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 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
Obtain the fix for this APAR.

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 PM69213 is currently targeted for inclusion WebSphere
    Application Server Fix Packs 6.1.0.47, 8.0.0.5, and 8.5.0.2.
    
    The fix will also be delivered as sysrouted APAR PM71182 in
    WebSphere Application Server V7.0 Fix Pack 7.0.0.27 for z/OS.
    
    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

    PM69213

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-19

  • Closed date

    2012-08-20

  • Last modified date

    2013-10-04

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

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

    PM71182

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R610 PSY UK97031

       UP13/09/07 P F309

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

More support for: WebSphere Application Server for z/OS
General

Software version: 6.1

Reference #: PM69213

Modified date: 04 October 2013