PK85799: A JAX-WS client might fail with an asynchronous timeout error.

Fixes are available

APAR status

Closed as program error.

Error description

A JAX-WS client might fail when sending a large, asynchronous
request. The following is an example of what might appear in
the client's log file:

[4/23/09 11:36:35:895 CDT] 00000035 SystemErr     R
javax.xml.ws.WebServiceException: java.io.IOException: Request
not finished yet
...
[4/23/09 11:41:32:870 CDT] 00000024 SystemErr     R Caused by:
java.net.SocketTimeoutException: Async operation timed out
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.process
SyncReadRequest(AioTCPReadRequestContextImpl.java:189)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPRe
adRequestContextImpl.java:111)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.http.channel.outbound.impl.HttpOutboundServiceContext
Impl.parseResponseMessageSync(HttpOutboundServiceContextImpl.jav
a:1656)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.http.channel.outbound.impl.HttpOutboundServiceContext
Impl.readSyncResponse(HttpOutboundServiceContextImpl.java:724)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.http.channel.outbound.impl.HttpOutboundServiceContext
Impl.startResponseReadSync(HttpOutboundServiceContextImpl.java:1
774)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.http.channel.outbound.impl.HttpOutboundServiceContext
Impl.finishRequestMessage(HttpOutboundServiceContextImpl.java:11
94)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.out.HttpOutSyncWriter.finishBu
fferRequest(HttpOutSyncWriter.java:94)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.out.HttpOutWriter.writeBuffer(
HttpOutWriter.java:136)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.out.HttpOutByteBufferOutputStr
eam.finish(HttpOutByteBufferOutputStream.java:468)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendChunked
Request(SOAPOverHTTPSender.java:757)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendSOAPReq
uest(SOAPOverHTTPSender.java:674)
[4/23/09 11:41:32:872 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.send(SOAPOv
erHTTPSender.java:477)
...

You may also see the following error in an FFDC log:

getRequestBodyBuffer(async): exception:
com.ibm.wsspi.http.channel.exception.IllegalHttpBodyException:
Missing chunk LF

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server V7.0   *
*                  users of JAX-WS clients sending             *
*                  asynchronous requests.                      *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-WS client might fail with an      *
*                      asynchronous timeout error.             *
****************************************************************
* RECOMMENDATION:  Install a FixPack containing this APAR      *
****************************************************************
A JAX-WS client might fail when sending a large, asynchronous
request. The following is an example of what might appear in
the client's log file:

[4/23/09 11:36:35:895 CDT] 00000035 SystemErr     R
javax.xml.ws.WebServiceException: java.io.IOException: Request
not finished yet
...
[4/23/09 11:41:32:870 CDT] 00000024 SystemErr     R Caused by:
java.net.SocketTimeoutException: Async operation timed out
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.process
SyncReadRequest(AioTCPReadRequestContextImpl.java:189)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPRe
adRequestContextImpl.java:111)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.http.channel.outbound.impl.HttpOutboundServiceContext
Impl.parseResponseMessageSync(HttpOutboundServiceContextImpl.jav
a:1656)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.http.channel.outbound.impl.HttpOutboundServiceContext
Impl.readSyncResponse(HttpOutboundServiceContextImpl.java:724)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.http.channel.outbound.impl.HttpOutboundServiceContext
Impl.startResponseReadSync(HttpOutboundServiceContextImpl.java:1
774)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.http.channel.outbound.impl.HttpOutboundServiceContext
Impl.finishRequestMessage(HttpOutboundServiceContextImpl.java:11
94)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.out.HttpOutSyncWriter.finishBu
fferRequest(HttpOutSyncWriter.java:94)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.out.HttpOutWriter.writeBuffer(
HttpOutWriter.java:136)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.out.HttpOutByteBufferOutputStr
eam.finish(HttpOutByteBufferOutputStream.java:468)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendChunked
Request(SOAPOverHTTPSender.java:757)
[4/23/09 11:41:32:871 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendSOAPReq
uest(SOAPOverHTTPSender.java:674)
[4/23/09 11:41:32:872 CDT] 00000024 SystemErr     R     at
com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.send(SOAPOv
erHTTPSender.java:477)
...

You may also see the following error in an FFDC log:

getRequestBodyBuffer(async): exception:
com.ibm.wsspi.http.channel.exception.IllegalHttpBodyException:
Missing chunk LF

Problem conclusion

The error occurs because the JAX-WS runtime did not read the
entire incoming message when the connection is cleaned
up as part of the HTTP 202 acknowledgment processing.  This
error is intermittent and most likely to occur when the
message is large.

The JAX-WS runtime is corrected to read the entire incoming
message and store it prior to the 202 acknowledgment
processing.  This should eliminate the AsyncTimeoutException.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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
PK85799
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-01
Closed date
2009-05-13
Last modified date
2010-09-03

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

PM00480

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

PK85799: A JAX-WS client might fail with an asynchronous timeout error.

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?