Fixes are available
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
A JAX-WS client might encounter the following when trying to send a request: Caused by: java.io.IOException: Async IO operation failed (1), reason: RC: 107 Transport endpoint is not connected at com.ibm.io.async.AsyncLibrary$IOExceptionCache.<init>(AsyncLibra ry.java:891) ... at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendChunked Request(SOAPOverHTTPSender.java:762) at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendSOAPReq uest(SOAPOverHTTPSender.java:679) at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.send(SOAPOv erHTTPSender.java:482) ... This error is more likely to happen if there is a non-IBM web server between the client and the web service it is trying to call.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of JAX-WS clients running in IBM * * WebSphere Application Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: A JAX-WS client might fail with * * "IOException: Async IO Operation * * failed" errors if it sends a Host * * header containing a port * **************************************************************** * RECOMMENDATION: Install a fixpack that contains this APAR * **************************************************************** A JAX-WS client might encounter the following when trying to send a request: Caused by: java.io.IOException: Async IO operation failed (1), reason: RC: 107 Transport endpoint is not connected at com.ibm.io.async.AsyncLibrary$IOExceptionCache.<init>(AsyncLibra ry.java:891) ... at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendChunked Request(SOAPOverHTTPSender.java:762) at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendSOAPReq uest(SOAPOverHTTPSender.java:679) at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.send(SOAPOv erHTTPSender.java:482) ... This error is more likely to happen if there is a non-IBM web server between the client and the web service it is trying to call. The intermediary server might not understand where to route the request to because of a port number in the request's HTTP Host header. For example, Host: lilygirl.austin.ibm.com:80
Problem conclusion
The JAX-WS runtime was changed to support a new custom property. If the user sets the custom JVM property "com.ibm.ws.websvcs.suppressHTTPRequestPortSuffix" to "true", the JAX-WS runtime will not append the port number to the HTTP Host header value. In other words, the Host header will only contain the hostname of the endpoint URL. For example, Host: lilygirl.austin.ibm.com The default value of the property is false. This means that by default, the port number will be appended to the Host header value. For information on how to set custom JVM properties, see the "Java virtual machine custom properties" article in the Information Center for your operating system. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.11. 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 number
PM10292
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-18
Closed date
2010-03-25
Last modified date
2011-08-17
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
R700 PSY
UP
Document Information
Modified date:
24 October 2021