PK87418: WHILE USING WS-RELIABLEMESSAGING, ONE WAY MESSAGES ARE NOT COMPLETING

Fixes are available

APAR status

Closed as program error.

Error description

While running the application with (WS-RM)
WS-ReliableMessaging, message sequences accumulate and never
complete.

The scenario is this:
- Using 5 clients each using 10 sequences (set to 1WaySync
inorder messaging)

The following error may be seen:
---------------------------------------------
org.apache.sandesha2. workers.InvokerWorker invokeMessage
Exception :
org.apache.axis2.AxisFault:
java.lang.NullPointerException
at org.apache.axis2. AxisFault.makeFault (AxisFault.java:430)
at org.apache.axis2 .jaxws.server.JAXWSMessageReceiver.receive
(JAXWSMessageReceiver.java:218)
at org.apache.axis2. engine.AxisEngine.resumeReceive
(AxisEngine.java:345)
at org.apache.sandesha2. workers.InvokerWorker.invokeMessage
(InvokerWorker.java:314)
at org.apache.sandesha2. workers.InvokerWorker.run
(InvokerWorker.java:111)
at com.ibm.ws.websvcs. rm.context.WSRMContextManager$1$1.run
(WSRMContextManager.java:156)
at java.security.AccessControlle r.doPrivileged
(AccessController.java:202)
at com.ibm.ws.websvcs.rm. context.WSRMContextManager$1.run
(WSRMContextManager.java:145)
at com.ibm.ws.asynchbeans.J2EEContext.run (J2EEContext.java:622)
at com.ibm.ws.asynchbeans. ExecutionContextImpl.go
(ExecutionContextImpl.java:86)
at com.ibm.ws.websvcs.rm.context.WSRMContextManager$2.run
(WSRMContextManager.java:179)
at java.util.concurrent. ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:896)
at java.util.concurrent. ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:918)
at java.lang.Thread.run (Thread.java:735)
Caused by: javax.xml.ws.WebServiceException:
java.lang.NullPointerException
at org.apache.axis2.jaxws.ExceptionFactory.
createWebServiceException (ExceptionFactory.java:175)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application                   *
*                  Server users of JAXWS with                  *
*                  WS-ReliableMessaging (WS-RM)                *
****************************************************************
* PROBLEM DESCRIPTION: WS-RM message sequences may not         *
*                      complete when sending oneWay messages   *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
A JAX-WS web service using WS-RM can receive message from
multiple WS-RM enabled clients.   The clients are sending
oneWay messages, and some of these messages are not completing.

The following error may be seen on the Websphere Application
Server where the JAX-WS web services is deployed:
---------------------------------------------
org.apache.sandesha2. workers.InvokerWorker invokeMessage
Exception :
org.apache.axis2.AxisFault:
java.lang.NullPointerException
at org.apache.axis2. AxisFault.makeFault (AxisFault.java:430)
at org.apache.axis2 .jaxws.server.JAXWSMessageReceiver.receive
(JAXWSMessageReceiver.java:218)
at org.apache.axis2. engine.AxisEngine.resumeReceive
(AxisEngine.java:345)
at org.apache.sandesha2. workers.InvokerWorker.invokeMessage
(InvokerWorker.java:314)
at org.apache.sandesha2. workers.InvokerWorker.run
(InvokerWorker.java:111)

Problem conclusion

The root of the problem is the JAX-WS runtime is incorrectly
unmarshaling the incoming message from the WS-RM clients.
Two-way messages use an unmarshaling algorithm that is working
correctly.  However due to a flaw in the logic, the one-way
messages were using a different algorithm.

The code is corrected so that the two-way and one-way messages
are now using the same unmarshaling algorithm.  This change
prevents the NullPointerException error, and the one-way
messages are now processed correctly.

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
PK87418
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-27
Closed date
2009-06-03
Last modified date
2009-06-03

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:
24 October 2021

Tips

PK87418: WHILE USING WS-RELIABLEMESSAGING, ONE WAY MESSAGES ARE NOT COMPLETING

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?