PK49515: PING MECHANISM CAUSES THREAD HANGS IN ROUTING TABLE BECAUSE OF SYNCHRONIZATION BLOCKS.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Ping mechanism causes thread hangs in routing table because of
  synchronization blocks
  
  The following message is found in the nodeagent log file, when
  the nodeagent was stuck .
  
  [6/21/07 8:03:37:049 CDT] 000066fe NodeSync      E
  ADMS0005E: The system is unable to generate synchronization
  request:  .
  [6/21/07 8:03:37:195 CDT] 000066fe NodeSyncTask  A
  ADMS0036E: The configuration synchronization failed.
  [6/21/07 8:13:26:048 CDT] 00006782 PidWaiter     W
  ADML0063W: The tool cannot contact server "TUFNAjvm". Force
  stop this server if it is still running.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application server versions    *
  *                 6.0.2 and 6.1 users.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Ping mechanism causes thread hangs in   *
  *                      routing table because of                *
  *                      synchronization blocks                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Ping mechanism causes thread hangs in routing table because of
  synchronization blocks and you can see the following the
  exceptions in SystemOut.log from nodeagent:
  
  6/21/07 8:03:37:049 CDT] 000066fe NodeSync
  
  E ADMS0005E: The system is unable to generate synchronization
  request:
  com.ibm.websphere.management.exception.ConnectorException:
  ADMC0009E:
  The system failed to make the SOAP RPC call: invoke at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient.
  invokeTemplate(SOAPConnectorClient.java(Compiled Code))
  caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read
  timed out;
  targetException=java.net.SocketTimeoutException: Read timed
  out]
   at
  org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown
  Source)
  
  [6/21/07 8:03:37:195 CDT] 000066fe NodeSyncTask  A
  ADMS0036E: The configuration synchronization failed.
  
  
  [6/21/07 8:13:26:048 CDT] 00006782 PidWaiter     W
  ADML0063W: The tool
  cannot contact server "TUFNAjvm". Force stop this server if it
  is still running.
  
  
  [6/21/07 8:13:28:058 CDT] 00006785 PidWaiter     W
  ADML0063W: The tool
  cannot contact server "EOMPCjvm". Force stop this server if it
  is still running.
  

Problem conclusion

• Modified the code to avoid the hang for servers by removing
  the synchronization.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpack 6.0.2.25 and 6.1.0.15.
  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

  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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP