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

APAR status

• Closed as duplicate of another APAR.

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

Problem conclusion

Temporary fix

Comments

• PM45918 is a sysroute of APAR PM10292. APAR PM45918 was taken to
  deliver a ++APAR. APAR PM45918 is being closed DUP of APAR
  PM15830 because PM15830 documents the delivery of APAR
  PM10292 in Service Level (Fix Pack) 7.0.0.11 of WebSphere
  Application Server V7.0 for z/OS.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM10292

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels