PK72317: WS-RELIABLEMESSAGING CAN EXPERIENCE EFFICIENCY AND USABILITY ISSUES WHEN UNDER LOAD OR WHEN PERFORMING FAILOVER.

Fixes are available

APAR status

Closed as program error.

Error description

Issues with web services WS-ReliableMessaging.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server users  *
*                  of Web Services Reliable Messaging ( WS-RM )*
****************************************************************
* PROBLEM DESCRIPTION: Address a number of Web Services        *
*                      Reliable Messaging problems             *
*                      discovered during extended testing.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
(1) Multiple Web Services Reliable Messaging asynchronous
clients missing TerminateSequence at their exit.

(2) Sequences not restarted if they have timed out.

(3) Sandesha2 SenderWorker parser close request causes
corruption, due to a collision with XLXP Parser?s
unmarshalling of the message.

(4) After running some lengthy testing, threads started
hanging and the following messages were seen:
ThreadMonitor W   WSVR0605W: Thread "WebContainer : 11"
(0000006d) has been active for 644828 milliseconds and may be
hung.  There is/are 12 thread(s) in total in the server that
may be hung.
This appears to be because the application was stopped and
started while handling requests for a non-Persistent message
store.

(5) InMemoryTransaction should not try to enlist beans when no
longer active.

(6) A user modified the ping sample in the
JaxWSServicesSamples.ear to start a UserTransaction and set
the enableTransactionalOneWay property in the request context.
 This caused an IllegalStateException to be raised.

(7) NullPointerException was raised when a sequence had not
been used for 12 hours.

(8) Web Services-Reliable Messaging / Web
Services-Notification test client was losing notifications
(IndexOutOfBounds exception). This was being caused by
problems in the way tokens were being generated to identify
the messaging engines being used.

(9) Web Services Reliable Messaging service was unable to
recover persistent 1 way messages. This was caused by the
Messaging Engine accepting requests before the Messaging
Engine Reliable Messaging start-up code had been run. Requests
passed to the Messaging Engine during this time receive the
following message:
WSIP0801E: The command invocation failed because the key was
invalid WSRM Sequence Command Handler

Problem conclusion

(1) The Web Services Reliable Messaging service has been
changed to handle missing TerminateSequence messages.
(2) The Web Services Reliable Messaging service has been
changed to ensure that timed-out sequences are restarted.
(3) SenderWorker has been changed to remove a secondary close
of the parser, so eliminating the collision.
(4) The Web Services Reliable Messaging service has been
changed to handle the stopping and starting of an application
better.
(5) A check has been introduced to the Web Services Reliable
Messaging service to ensure that the transaction is active
before allowing any work to be done.
(6) Web Services Reliable Messaging service has been changed
to check the axis configuration for migrators before
registering a new one.
(7) Web Services Reliable Messaging service has been protected
against a null when timing out an unused sequence.
(8) Web Services Reliable Messaging service has changed the
mechanism for generating tokens so that they uniquely identify
the Messaging Engine being used.
(9) Web Services Reliable Messaging has been changed to retry
the requests when the Messaging Engine is starting up.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  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
PK72317
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
2008-09-17
Closed date
2008-11-18
Last modified date
2008-11-18

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

Tips

PK72317: WS-RELIABLEMESSAGING CAN EXPERIENCE EFFICIENCY AND USABILITY ISSUES WHEN UNDER LOAD OR WHEN PERFORMING FAILOVER.

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?