PM10292: A JAX-WS CLIENT MAY FAIL WITH "IOEXCEPTION: ASYNC IO OPERATION FAILED" ERROR IF ITS HOST HEADER CONTAINS A PORT

Fixes are available

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:

PM45918

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM10292: A JAX-WS CLIENT MAY FAIL WITH "IOEXCEPTION: ASYNC IO OPERATION FAILED" ERROR IF ITS HOST HEADER CONTAINS A PORT

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?