PH09034: SET DEFAULT CONNECTIONTTL TO 28 IF NOT PRESENT IN CONFIGURATION FOR THE WEBSPHERE WEBSERVER PLUGIN

9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• ConnectionTTL should always be present in the generated
  plugin-cfg.xml but if it is not, plugin uses 0 and should use
  a better default value when the setting is not present.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server web        *
  *                  server plugin users                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: If connectionTTL is not present in      *
  *                      the plugin-cfg.xml, stale transports    *
  *                      will not be detected until used.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the connectionTTL is not present in plugin's configuration
  (plugin-cfg.xml) for a transport, plugin will use a default
  value of 0. A value of zero tells plugin to always assume a
  transport is valid until a error is encountered.
  

Problem conclusion

• The code has been modified to use a default value of 28
  seconds when connectionTTL is not present. With this setting,
  if connectionTTL is not specified, transports between plugin
  and WebSphere which are inactive for 28 seconds or more will
  be removed from the connection pool and not re-used. The 28
  second default is chosen based off the default HTTP transport
  persistent timeout of 30 seconds minus 2 seconds for
  synchronization and transit delays which may occur. The
  connectionTTL should be configured such that plugin closes
  stale transport connections before the HTTP persistent timeout
  value expires on the transport to prevent plugin from using
  transports which WebSphere may have terminated.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.16 and 9.0.5.0.  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

• R850 PSY

     UP

• R900 PSY

     UP