PI66695: JAVA.IO.IOEXCEPTION: ASYNC IO OPERATION FAILED

8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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

• Users get exception while calling the service to WebSphere
  application
  servers.exception  java.io.IOException: Async IO operation
  failed (1),
  reason: RC: 76  Socket is not connected;
  
  It only happens when access through the CSS VIP and http
  server.  No  issue with direct call to jvm port.
  
  It looks like a non-regression bug in mod_reqtimeout.
  

Local fix

• Increasing the Body timeout of RequestReadTimeout
  to be over worst-case response time for the slowest resources.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM HTTP Server (powered by        *
  *                  Apache)                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Keep-Alive requests can timeout         *
  *                      early for slow responses when using     *
  *                      mod_reqtimeout.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  mod_reqtimeout will take response times into account when
  timing out a request. This can cause Keep-Alive requests to
  timeout early if the response time is greater than the
  configured body RequestReadTimeout.
  This behavior is incorrect as the timeout should only consider
  the time spent to receive the request's headers or body.
  

Problem conclusion

• mod_reqtimeout was modified to not include response times when
  determining whether to timeout the request or not.
  
  This fix is targeted for IBM HTTP Server fix packs:
  - 7.0.0.43
  - 8.0.0.14
  - 8.5.5.11
  

Temporary fix

• Increase the RequestReadTimeout body timeout to accomodate
  slow responses.
  

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

  IBM HTTP SERVER

• Fixed component ID

  5724J0801

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP

• R900 PSY

     UP