PM85931: RESET TIMEOUT VALUE ON ALARM REGISTRATION TO REMIT ALARM TIMEOUT WARNINGS

8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Repeated alarm timeout warning messages are logged to node
  agent SystemOut.log when node agent is waiting for dmgr
  sending notification within 1 min (waiting time).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  V8.0 and V8.5.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message UTLS0008W is written to the     *
  *                      log for a PullRemoteReceiver thread.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Message UTLS0008W is written to log for a PullRemoteReceiver
  thread. The warning is false in that the system is functioning
  normally.  The thread monitor that logs the warning does not
  allow enough time for the thread to complete. The message and
  accompanying stack trace look something like that shown below:
  AlarmThreadMo W   UTLS0008W: The return of alarm thread
  "Non-deferrable Alarm : 3" (00000007) to the alarm thread pool
  has been delayed for 10,218 milliseconds. This may be
  preventing normal alarm function within the application server.
  The alarm listener stack trace is as follows:
  at java.net.SocketInputStream.socketRead0(Native Method)
  at
  java.net.SocketInputStream.read(SocketInputStream.java:140)
  at com.ibm.jsse2.b.a(b.java:111)
  at com.ibm.jsse2.b.a(b.java:90)
  at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:384)
  at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:91)
  at com.ibm.jsse2.f.read(f.java:43)
  at
  java.io.BufferedInputStream.fill(BufferedInputStream.java:229)
  at
  java.io.BufferedInputStream.read(BufferedInputStream.java:248)
  at
  org.apache.soap.util.net.HTTPUtils.post(HTTPUtils.java:590)
  at
  org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPC
  onnection.java:425)
  at org.apache.soap.rpc.Call.WASinvoke(Call.java:451)
  at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient$8.run(S
  OAPConnectorClient.java:844)
  at
  com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
  troller.java:118)
  at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeT
  emplateOnce(SOAPConnectorClient.java:837)
  at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeT
  emplate(SOAPConnectorClient.java:682)
  at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeT
  emplate(SOAPConnectorClient.java:672)
  at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient.pullNot
  ifications(SOAPConnectorClient.java:1016)
  at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(
  SOAPConnectorClient.java:547)
  at $Proxy12.pullNotifications(Unknown Source)
  at
  com.ibm.ws.management.event.PullRemoteReceiver.getNotifications(
  PullRemoteReceiver.java:222)
  at
  com.ibm.ws.management.event.PullRemoteReceiver.alarm(PullRemoteR
  eceiver.java:183)
  at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:133)
  at
  com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690).
  The key method in the call stack that identifies this problem
  is
  com.ibm.ws.management.event.PullRemoteReceiver.getNotifications(
  ).
  

Problem conclusion

• Thread monitoring behavior was modified to eliminate the false
  warnings.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.7 and 8.5.5.1.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP