PM85854: ISSUES WITH MESSAGING ENGINE NOT STARTING UP DURING SERVER START

Fixes are available

APAR status

Closed as program error.

Error description

The problem is caused by the incorrect superclass constructor
being called by the constructor of the
DestinationSequenceItemStream when constructed as a child of a
parent DestinationSequenceItemStream.

On recovery this leads to a new child class being created for
the bottom child in the hierarchy.  Although this does not cause
a problem normally when running, when the sequence is deleted
(either because it  times out or is deleted administratively) th
will be removed from the administrative console's view).

The next time the app server is restarted it finds the partially
deleted sequence and will inspect the information on the sequenc

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  WS-ReliableMessaging                        *
****************************************************************
* PROBLEM DESCRIPTION: Deletion of a WS-RM destination         *
*                      sequence may fail leaving a partial     *
*                      data structure which prevents the ME    *
*                      from starting.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem is caused by the incorrect superclass constructor
being called by the constructor of the
DestinationSequenceItemStream when constructed as a child of a
parent DestinationSequenceItemStream.
On recovery this leads to a new child class being created for
the bottom child in the hierarchy.  Although this does not
cause
a problem  normally when running, when the sequence is deleted
(either because it  times out or is deleted administratively)
the sequence deletion process will fail (though the sequence
will be removed from the  administrative console's view).  The
next time the app server is restarted it finds the partially
deleted sequence and will inspect the information on  the
sequence which does not contain information that the ws-rm
component expects to find at which point it throws an error
during the SIB data restoration process.  This causes SIB to
make the ME unavailable.

Problem conclusion

The programming error that led to the creation of the
superfluous data structures in the destination sequence that
prevented its deletion from occuring successfully was fixed.
Function was also added to detect and remove the partially
deleted destination sequences at server initialization and
allow the messaging engine to continue startup.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.31, 8.0.0.8 and 8.5.5.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
PM85854
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-03-28
Closed date
2013-07-02
Last modified date
2013-07-02

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
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
11 January 2022

Tips

PM85854: ISSUES WITH MESSAGING ENGINE NOT STARTING UP DURING SERVER START

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?