PK75981: THERE ARE SOME FUNCTIONAL ISSUES WITH WS-RELIABLEMESSAGING.

Fixes are available

APAR status

Closed as program error.

Error description

In some cases WS-ReliableMessaging can experience runtime
issues. These must be resolved.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server V7.0   *
*                  users of Web Services Reliable Messaging    *
*                  ( WS-RM ).                                  *
****************************************************************
* PROBLEM DESCRIPTION: Address a number of Web Services -      *
*                      Reliable Messaging ( WS-RM ) problems   *
*                      discovered during extended testing.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1. Currently the SPI set various options on the service
client. It did not undo these once the operation was finished.

2. When running Reliable Messaging Policy test the following
exception occurred when invocation was set to asynchronous :
java.util.concurrent.ExecutionException:
javax.xml.ws.WebServiceException:
org.apache.sandesha2.SandeshaException: Cannot handle
synchronous 2-way connections because MakeConnection is not
enabled. Either enable MakeConnection or reconfigure your
application to use asynchronous connections.
at
org.apache.axis2.jaxws.client.async.AsyncResponse.onError(AsyncR
esponse.java:115)
at
org.apache.axis2.jaxws.client.async.AsyncResponse.onError(AsyncR
esponse.java:95)
at
org.apache.axis2.jaxws.client.async.CallbackFutureTask.call(Call
backFuture.java:280)
...

3. Reliable Messaging Service does not allow services within
the same application to use different quality of service
levels. Reliable Messaging Policy did not apply this
restriction.

4. Multiple Reliable Messaging asynchronous clients missed
TerminateSequence at the exit of the client.

5. During recovery testing of synchronous 2-way messaging, the
following messages were seen on the server:
FaultManager  E org.apache.sandesha2.util.FaultManager
getOrSendFault Could not send the fault 'The
SequenceAcknowledgement violates the cumulative
Acknowledgement invariant.' due to the exception '{1}';
There were two problems: one was the fault itself, and one was
the incorrect population of the error message: {1}.

6. HTTP Error 500 occurred when using Web Services-Reliable
Messaging ( WS-RM ) provider-only policy.

7. Testing with the policy set of WSI-RSP with WS-Policy
resulted in the following error message:

CWWSS7202E: Issuing of Security Context Token fails. The
exception is :
com.ibm.ws.wssecurity.trust.client.impl.TrustException: A
request failed with the exception Sandesha2 got an exception
when processing an out message: java.lang.NullPointerException..

8. When combining Web Services Notification with Web Services
Reliable Messaging there was a failure to restart sequences
after a server restart.

9. Application deployed on a cluster with 2 members. The
client was running unmanaged, using 3 unique sequences to the
same endpoint (endpoint?seq1, endpoint?seq2, endpoint?seq3).
At the end of the test the Reliable Messaging state for all
but one of the sequences was shown to be in error on the
administrative console.

10. When testing the behaviour of InvalidAcknowledgement, the
expected AxisFault message was not propagated correctly.

11. Performance regression discovered during testing.

12. Extended tests failed with the error
"sequenceManager.waitUntilSequenceCompleted failed" during
Sync 1 Way and Sync 2 Way invocations.

Problem conclusion

The Reliable Messaging Service has been changed to address the
problems described.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.3.  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
PK75981
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
2008-11-19
Closed date
2009-03-12
Last modified date
2009-03-12

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
WEBS APP SERV N
Fixed component ID
5724H8800

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

Tips

PK75981: THERE ARE SOME FUNCTIONAL ISSUES WITH WS-RELIABLEMESSAGING.

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?