PH58250: DEFINE SERVERIOTIMEOUT > 66 000 SECS VIA ISC

APAR status

• Closed as new function.

Error description

• When changing an application server's read/write timeout to a
  value greater than what's acceptable for an integer, the
  admin console displays the error "The field, Read/Write
  timeout, should be in the range -65535 through 65535."
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Users can't change the serverIOTimeout  *
  *                      outside the range of -65535 through     *
  *                      65535.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When customers attempt to change the WebSphere application
  server's read/write timeout within the admin console to a value
  outside the range of -65535 through 65535 they get an error
  message "The field, Read/Write timeout, should be in the range
  -65535 through 65535.".
  The reason this happens is because Read/Write field within the
  admin console is restricted to this range.
  

Problem conclusion

• A new property has been introduced
  'overridePluginServerIOTimeout'.  When set
  properly, the override value will be put in place of the value
  set within the
  "Web server plug-in properties" Read/Write field of the admin
  console.
  
  This new property can be set in 2 places:
  1. Web servers > [your webserver] > Plug-in properties > Custom
  properties
  
  2. Application servers > [your server] > Web Container Settings
  > Web container
  > Custom properties
  
  When set at the Web Server level, this is consider to be a
  global setting.  Any
  cluster/servers associated to this web server will take on the
  value from the
  override property for its ServerIOTimeout.
  
  If set within an Application Server, then the cluster/servers
  associated to
  that server will have their ServerIOTimeout value set to the
  override value.
  
  Important notes:
  1. When setting this for a cluster of 2 or more servers, you
  should only set
  the value on any one server.  The value will be used for all
  servers within the
  cluster. If set on multiple servers of the same cluster, the
  last one set will
  be the value for all members.
  
  2.  If you set this property at both the webserver and
  application server
  levels, the application server value will take precedence over
  the global
  setting from within the web servers setting.
  
  3.  If you set a webserver level (global) override and wish to
  have the default
  value (900), you must set the new
  'overridePluginServerIOTimeout' to 900 within
  one of the servers of the affected cluster.
  
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.19, 8.5.5.26 . For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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