IC99311: TPC-R ON ZOS THREADS CONTINUE RUNNING AFTER STOP HAS BEEN ISSUED FOR WEBSPHERE ADDRESS SPACE

Refresh Pack 5.2.2 (June 2014) for Tivoli Storage Productivity Center
Refresh Pack 5.2.3 (August 2014) for Tivoli Storage Productivity Center
Fix Pack 5.2.4 (November 2014) for Tivoli Storage Productivity Center
Fix Pack 5.2.4.1 (December 2014) for Tivoli Storage Productivity Center
Refresh Pack 5.2.5 (March 2015) for Tivoli Storage Productivity Center (withdrawn)
Fix Pack 5.2.5.1 (April 2015) for Tivoli Storage Productivity Center (withdrawn)
Refresh Pack 5.2.6 (June 2015) for Tivoli Storage Productivity Center
Refresh Pack 5.2.7 (August 2015) for Tivoli Storage Productivity Center
IBM Spectrum Control V5.2.8 (December 2015)
IBM Spectrum Control V5.2.9 (February 2016)
IBM Spectrum Control V5.2.10 (May 2016)
IBM Spectrum Control V5.2.10.1 (July 2016)
IBM Spectrum Control V5.2.11 (August 2016)
IBM Spectrum Control V5.2.12 (November 2016)
IBM Spectrum Control V5.2.13 (March 2017)
IBM Spectrum Control V5.2.14 (May 2017)
IBM Spectrum Control V5.2.15 (August 2017)
IBM Spectrum Control V5.2.15.2 (November 2017)
IBM Spectrum Control V5.2.16 (March 2018)
IBM Spectrum Control V5.2.17 (May 2018)
Fix Pack 5.2.7.1 (February 2016) for Tivoli Storage Productivity Center

APAR status

• Closed as program error.

Error description

• A stop is issued to the WebSphere Address space that is running
  the TPC-R application. Threads can
  remain running and prevent WebSphere from completely shutting
  down. The thread responsible for this
  is:
  
  TCB: 0x77ae88
  associated Java thread:
  name: Thread-143
  Thread object:
  com/ibm/storage/csm/gui/event/EventServiceﾽEventPostingThread @
  0x483279bb68
  Daemon: false
  Thread.State: WAITING
  JVMTI state: ALIVE WAITING WAITING_INDEFINITELY IN_OBJECT_WAIT
  waiting to be notified on: java/util/LinkedList@0x483279c070
  owner
  name: <unowned>
  Java stack frames:
  java/lang/Object.wait
  java/lang/Object.wait()
  com/ibm/storage/csm/gui/event/EventService&#65469;EventPostingThread.ru
  n()
  
  On shut down the method stop()
  is never called, and further this Thread is not defined as a
  daemon thread therefore may continue
  running indefinitely.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users who require the TPC for Replication server to be       *
  * restarted                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * | fix pack | 5.1.1-TIV-TPC-FP0004 - target 2Q 2014 |         *
  * | release  | 5.2.1-TIV-TPC-FP0000 - target 1Q 2014 |         *
  *                                                              *
  * http://www-01.ibm.com/support/docview.wss?&uid=swg21320822   *
  *                                                              *
  * The target dates for future fix packs do not represent a     *
  * formal                                                       *
  * commitment by IBM. The dates are subject to change without   *
  * notice.                                                      *
  * When attempting to shut down the WebSphere Application       *
  * Server on zOS certain threads may fail to close properly.    *
  * These threads will continue to run and keep the WebSphere    *
  * Address space on zOS open. On AIX and Unix systems the       *
  * problem may be seen when the user tries to issue             *
  * stopServer.sh and the java process continues to run for a    *
  * long time. stopServer.sh may fail to fully bring down the    *
  * processes. The threads may run indefinitely, thus require    *
  * the address space or java process to be cancelled.           *
  * This issue may not be seen on windows because of the way     *
  * that the windows service handles shutdown terminates the     *
  * errant threads after some time.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to pick up the fix                                   *
  ****************************************************************
  

Problem conclusion

• The threads will now be shut down properly.
  

Temporary fix

• If experiencing long stop times or failures to stop the server
  in a timely manner:
  Using windows use the task manager to manually kill the java
  process (select the command line column under "View" and look
  for the java process that belongs to *ReplicationServer*)
  Using AIX / Linux, use the ps command to determine the pid for
  ReplicationServer and issue the kill command
  Using zOS, in the console or SDSF panel issue the D A,L command
  to determine if the WebSphere address space continues even after
  stop has been issued. Issue cancel to the address space and
  associated servant and daemon addresses.
  

Comments

APAR Information

• 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

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels

• R510 PSY

     UP

• R520 PSY

     UP