IBM Support

PH28733: SERVER NOT SHUTTING DOWN WHEN STARTED IN RECOVERY MODE WHEN USING HPEL

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When the server is configured to use hpel and clean up logs by
age limit, the server starts a non-daemon timer thread.  This
thread should be created as a daemon thread.  When the server
is started in recovery mode (started with REC=Y) which causes
it to shut down after recovery is complete, the server may not
come down because it's waiting for the non-daemon hpel timer
thread to shut down.

A dump will show this thread:
name:          Thread-12
Thread object: com/ibm/ws/logging/hpel/impl/
LogRepositoryManagerImpl$TimerThread @ 0x80cccbe0
Native info:   !j9vmthread 0x3735a800  !stack 0x3735a800
Daemon:        false
ID:            41 (0x29)
Priority:      5
Thread.State:  <no matching state>
JVMTI state:   ALIVE WAITING SLEEPING
Java stack frames:
  java/lang/Thread.sleep(long, int)  (Native Method)
  java/lang/Thread.sleep(long)  source: Thread.java:948
  com/ibm/ws/logging/hpel/impl
/LogRepositoryManagerImpl$TimerThread.run()  source:
LogRepositoryManagerImpl.java:778

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
*                  on z/OS                                     *
****************************************************************
* PROBLEM DESCRIPTION: Server will not shut down when started  *
*                      in                                      *
*                      Recovery Mode when using HPEL on z/OS.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the server is configured to use HPEL logging and to clean
up
logs by age limit, the server starts a non-daemon HPEL timer
thread.  When the server is started in Recovery mode (started
with
REC=Y) which causes it to shut down after recovery is completed,
the server may not come down because it's waiting for the non-
daemon HPEL timer thread to shut down.
A dump will show this thread:
name:          Thread-12
Thread object: com/ibm/ws/logging/hpel/impl/
LogRepositoryManagerImpl$TimerThread @ 0x80cccbe0
Native info:   !j9vmthread 0x3735a800  !stack 0x3735a800
Daemon:        false
ID:            41 (0x29)
Priority:      5
Thread.State:  <no matching state>
JVMTI state:   ALIVE WAITING SLEEPING
Java stack frames:
java/lang/Thread.sleep(long, int)  (Native Method)
java/lang/Thread.sleep(long)  source: Thread.java:948
com/ibm/ws/logging/hpel/impl
/LogRepositoryManagerImpl$TimerThread.run()  source:
LogRepositoryManagerImpl.java:778

    



Problem conclusion


    

  • The non-daemon HPEL timer thread was changed to be a daemon thre
to avoid this issue.

The fix for this APAR is targeted for inclusion in fix pack
8.5.5.19 and 9.0.5.6. For more information, see 'Recommended
Updates for WebSphere Application Server':
https://www.ibm.com/support/pages/node/715553

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PH28733
    • 

  • Reported component name
    WEBSPHERE FOR Z
    • 

  • Reported component ID
    5655I3500
    • 

  • Reported release
    900
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2020-08-21
    • 

  • Closed date
    2020-09-03
    • 

  • Last modified date
    2020-09-03
    • 





    

  • 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


    








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            04 September 2020
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback