PK85344: JAX-WS WEB MODULES WITH RM POLICY SET APPLIED ARE UNABLE TO SEND MESSAGES

Fixes are available

APAR status

Closed as program error.

Error description

Any JAX-WS web module with predefined servlets and RM policy
set applied are sometimes unable to send messages. This only
seems to happen when the application is stopped prior to any
messages being sent. If the application is then restarted, the
messages will not be sent. The only workaround for this is to
restart the server.

Error message segment after restarting application:
------------------------------
[30/01/09 16:50:53:552 GMT]     FFDC
Exception:java.net.SocketTimeoutException
SourceId:com.ibm.ws.websvcs.transport.http.
SOAPOverHTTPSender.send ProbeId:409
Reporter:com.ibm.ws.websvcs.transport.http.
SOAPOverHTTPSender@180c180c
java.net.SocketTimeoutException: Async operation timed out
at com.ibm.ws.tcp.channel.impl.
AioTCPReadRequestContextImpl.processSyncReadRequest
(AioTCPReadRequestContextImpl.java:189)
at com.ibm.ws.tcp.channel.impl.
TCPReadRequestContextImpl.read
(TCPReadRequestContextImpl.java:111)
at com.ibm.ws.http.channel.outbound.impl.
HttpOutboundServiceContextImpl.parseResponseMessageSync
(HttpOutboundServiceContextImpl.java:1656)
at com.ibm.ws.http.channel.outbound.impl.
HttpOutboundServiceContextImpl.readSyncResponse
(HttpOutboundServiceContextImpl.java:724)
at com.ibm.ws.http.channel.outbound.impl.
HttpOutboundServiceContextImpl.startResponseReadSync
(HttpOutboundServiceContextImpl.java:1774)
at com.ibm.ws.http.channel.outbound.impl.
HttpOutboundServiceContextImpl.finishRequestMessage
(HttpOutboundServiceContextImpl.java:1194)
at com.ibm.ws.websvcs.transport.http.out.
HttpOutSyncWriter.finishBufferRequest
(HttpOutSyncWriter.java:94)
at com.ibm.ws.websvcs.transport.http.out.
HttpOutWriter.writeBuffer (HttpOutWriter.java:136)
at com.ibm.ws.websvcs.transport.http.out.
HttpOutByteBufferOutputStream.finish
(HttpOutByteBufferOutputStream.java:468)
at com.ibm.ws.websvcs.transport.http.
SOAPOverHTTPSender.sendChunkedRequest
(SOAPOverHTTPSender.java:755)
at com.ibm.ws.websvcs.transport.http.
SOAPOverHTTPSender.sendSOAPRequest (SOAPOverHTTPSender.java:672)
at com.ibm.ws.websvcs.transport.http. SOAPOverHTTPSender.send
(SOAPOverHTTPSender.java:475)
at com.ibm.ws.websvcs.transport.http.
HTTPTransportSender.invoke (HTTPTransportSender.java:311)
at org.apache.axis2.engine.AxisEngine. resumeSend
(AxisEngine.java:374)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application               *
*                  Server users of JAX-WS web modules          *
*                  with a RM policy set applied.               *
****************************************************************
* PROBLEM DESCRIPTION: Stopping and then restarting web        *
*                      application prevents any new            *
*                      messages from being sent                *
****************************************************************
* RECOMMENDATION:  Install a FixPack containing this APAR      *
****************************************************************
A JAX-WS module with a RM policy set applied is unable
to send messages. This only seems to happen when the
application is stopped prior to any messages being sent. If the
application is then restarted, the messages will not be sent.
The only workaround for this is to restart the server.

Error message segment after restarting application:
------------------------------
[30/01/09 16:50:53:552 GMT]     FFDC
Exception:java.net.SocketTimeoutException
SourceId:com.ibm.ws.websvcs.transport.http.
SOAPOverHTTPSender.send ProbeId:409
Reporter:com.ibm.ws.websvcs.transport.http.
SOAPOverHTTPSender@180c180c
java.net.SocketTimeoutException: Async operation timed out
at com.ibm.ws.tcp.channel.impl.
AioTCPReadRequestContextImpl.processSyncReadRequest
(AioTCPReadRequestContextImpl.java:189)
at com.ibm.ws.tcp.channel.impl.
TCPReadRequestContextImpl.read
(TCPReadRequestContextImpl.java:111)
at com.ibm.ws.http.channel.outbound.impl.
HttpOutboundServiceContextImpl.parseResponseMessageSync
(HttpOutboundServiceContextImpl.java:1656)
at com.ibm.ws.http.channel.outbound.impl.
HttpOutboundServiceContextImpl.readSyncResponse
(HttpOutboundServiceContextImpl.java:724)
at com.ibm.ws.http.channel.outbound.impl.
HttpOutboundServiceContextImpl.startResponseReadSync
(HttpOutboundServiceContextImpl.java:1774)
at com.ibm.ws.http.channel.outbound.impl.
HttpOutboundServiceContextImpl.finishRequestMessage
(HttpOutboundServiceContextImpl.java:1194)
at com.ibm.ws.websvcs.transport.http.out.
HttpOutSyncWriter.finishBufferRequest
(HttpOutSyncWriter.java:94)
at com.ibm.ws.websvcs.transport.http.out.
HttpOutWriter.writeBuffer (HttpOutWriter.java:136)
at com.ibm.ws.websvcs.transport.http.out.
HttpOutByteBufferOutputStream.finish
(HttpOutByteBufferOutputStream.java:468)
at com.ibm.ws.websvcs.transport.http.
SOAPOverHTTPSender.sendChunkedRequest
(SOAPOverHTTPSender.java:755)
at com.ibm.ws.websvcs.transport.http.
SOAPOverHTTPSender.sendSOAPRequest (SOAPOverHTTPSender.java:672)
at com.ibm.ws.websvcs.transport.http. SOAPOverHTTPSender.send
(SOAPOverHTTPSender.java:475)
at com.ibm.ws.websvcs.transport.http.
HTTPTransportSender.invoke (HTTPTransportSender.java:311)
at org.apache.axis2.engine.AxisEngine. resumeSend
(AxisEngine.java:374)

The root cause is the JAX-WS runtime is failing to cleanup
application data during application shutdown.

Problem conclusion

The JAX-WS runtime was failing to clean up some of the
application data in the cases where the application was never
called.  This was due to a invalid assumption incorporated
into the original design of the runtime.  The code is changed
to clean up all application data when the application is
shutdown.

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
PK85344
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-04-24
Closed date
2009-05-07
Last modified date
2009-09-04

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

[{"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:
25 October 2021

Tips

PK85344: JAX-WS WEB MODULES WITH RM POLICY SET APPLIED ARE UNABLE TO SEND MESSAGES

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?