PK68716: Unable to stop AppServer from administrative console fails with error: "ServerName is not running"

APAR status

• Closed as program error.

Error description

• When trying to stop an application server from the
  administrative console, the AppServer fails to stop with error:
  "Servername is not running". After enabling traces with
  trace string *=info:Admin=all:com.ibm.ws.management.*=all,
  you see this in the trace:
  
  
  
  [6/25/08 10:10:25:068 CEST] 00000074 PidWaiter     <
  ContactThread.run
  contact / returntrue  true Exit
  [6/25/08 10:10:25:068 CEST] 0000006c PidWaiter     3    Expected
  Exception Recieved
                                   java.lang.InterruptedException:
  operation interrupted
   at java.lang.Thread.sleep(Native Method)
   at
  com.ibm.ws.management.nodeagent.PidWaiter.contact(PidWaiter.java
  :1069)
   at
  com.ibm.ws.management.nodeagent.PidWaiter.run(PidWaiter.java:392
  )
   at java.lang.Thread.run(Thread.java:570)
  
  [6/25/08 10:10:25:068 CEST] 0000006c PidWaiter     3   Sleep
  Interval
  300000
  
  All the above 3 steps happened during same timestamp. So somehow
  Pidwaiter code goes to sleep method though the PidWaiter
  contact() thread returns true on that time itself.
  
  Then pidwaiter needlessly sleeps for 5 mins during this case.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Delay in NodeAgent's PidWaiter          *
  *                      contact() method.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Delay in returning pidwaiter contact() thread.
  
  In the following nodeagent's PidWaiter trace, the 5 minute
  sleep is not required. Contact() method returns at the
  exact timestamp where Thread.sleep() starts.
  
  [6/25/08 10:10:25:068 CEST] 00000074 PidWaiter     <
  ContactThread.run
  contact / return true  true Exit
  
  [6/25/08 10:10:25:068 CEST] 0000006c PidWaiter     3
  Expected Exception Recieved
  java.lang.InterruptedException:operation interrupted
  at java.lang.Thread.sleep(Native Method)
  at com.ibm.ws.management.nodeagent.PidWaiter.contact
  (PidWaiter.java:1069)
  at com.ibm.ws.management.nodeagent.PidWaiter.run(PidWaiter
  .java:392)
  at java.lang.Thread.run(Thread.java:570)
  
  [6/25/08 10:10:25:068 CEST] 0000006c PidWaiter     3   Sleep
  Interval    300000
  

Problem conclusion

• Source code has been modified to a add wait statement before
  Thread.sleep().
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.0.2.33.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  Note that this problem is specific to V6.0.2 and does not
  occur in V6.1.
  

Temporary fix

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP