PM24564: WEB SERVICES SOCKET TIMEOUT FOR JAX-RPC/JAX-WS WEB SERVICES CLIENTS MIGHT NOT BE HONORED.

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.37: WebSphere Application Server V6.1 Fix Pack 37
6.1.0.39: WebSphere Application Server V6.1 Fix Pack 39
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: WebSphere Application Server V6.1 Fix Pack 41
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: WebSphere Application Server V6.1 Fix Pack 43
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: WebSphere Application Server V6.1 Fix Pack 45
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• There are some scenarios where socket timeout for JAX-RPC/JAX-WS
  Web services clients (for example set via
  com.ibm.websphere.webservices.http.SocketTimeout JVM property)
  might not be honored. These scenarios usually involve heavy
  traffic or performance degradation on the Web Services provider
  with SSL transport enabled between the Web Services client and
  provider.
  .
  This problem was reported on WebSphere Application Server
  V6.1.0.29.
  

Local fix

• N/A.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Version    *
  *                  6.1 and 7.0 users                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: The SSL Handshake can last longer       *
  *                      than the TCP Channel Connect timeout    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The entire SSL Handshake might exceed the TCP Channel Connect
  timeout because it takes multiple reads or writes and the
  channel uses the default timeout for each operation
  

Problem conclusion

• The SSL Channel was modified to create a new custom property,
  useStrictSSLConnectTimeout(true/false(default)). This will
  tell the SSL Channel to keep track of how long each read or
  write operation takes to complete. This remaining time will be
  the new timeout for the next operation.This property can be
  set here on the administrative console:
  
  Application Servers > {Server Name} > Web Container Transport
  Chains > {Chain Name} > {SSL Channel Name} > Custom Properties
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.37 and 7.0.0.17.  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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R700 PSY

     UP