PK75571: IMPROVEMENTS TO SERVICE INTEGRATION BUS BEHAVIOR IN RECOVERY SCENARIOS WITHIN COMPLEX TOPOLOGIES

Fixes are available

APAR status

Closed as program error.

Error description

Additional testing has been performed to validate the behaviour
of the default messaging provider for WebSphere Application
Sever under certain recovery scenarios in complex topologies.

As a result of this testing some improvements in the behaviour
of the default messaging provider have been implemented, and
this APAR includes those improvements in WebSphere
Application Server

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  WebSphere Application Server                *
*                  V6.0, V6.1 and V7.0                         *
****************************************************************
* PROBLEM DESCRIPTION: The issues described in this APAR can   *
*                      occur during recovery from a            *
*                      failure or restart of a component of    *
*                      the system, such as an application      *
*                      server or network.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following issues are resolved by this APAR:
- An individual message does not flow over a connection
  between messaging engines after the remote messaging
  engine is restarted. The message is only delivered once
  additional messages are sent over the connection, or the
  sending messaging engine is restarted.
- After a messaging engine is restarted, a thread within a
  messaging engine that is delivering messages to it can
  become stuck in a tight loop within the following method:
com.ibm.ws.sib.processor.io.impl.MessageBuffer.capacityChanged()
- An application thread connected to one messaging
  engine, sending messages to a destination on a remote
  messaging engine, can hang after the remote messaging
  engine in restarted.
  A javacore of the messaging engine the application is
  connected to shows a thread with the following stack:
  at java.lang.Object.wait(Native Method)
  at com.ibm.ws.sib.processor.utils.LockManager.
                             lockExclusive(LockManager.java:245)
    at com.ibm.ws.sib.processor.impl.PtoPOutputHandler.
                     reallocateMsgs(PtoPOutputHandler.java:2024)
    at com.ibm.ws.sib.processor.impl.PtoPOutputHandler.
             eventPostAdd(PtoPOutputHandler.java(Compiled Code))
    at com.ibm.ws.sib.processor.impl.PtoPOutputHandler.
     messageEventOccurred(PtoPOutputHandler.java(Compiled Code))
    at com.ibm.ws.sib.processor.impl.store.items.MessageItem.
             eventPostCommitAdd(MessageItem.java(Compiled Code))
    at com.ibm.ws.sib.msgstore.task.AddTask.postCommit
                                   (AddTask.java(Compiled Code))
    at com.ibm.ws.sib.msgstore.task.TaskList.
                      postComplete(TaskList.java(Compiled Code))
    at com.ibm.ws.sib.msgstore.transactions.
                           MSDelegatingLocalTransaction.commit(
               MSDelegatingLocalTransaction.java(Compiled Code))
    at com.ibm.ws.sib.processor.impl.PtoPOutputHandler.
                      put(PtoPOutputHandler.java(Compiled Code))
- If a messaging engine is stopped using the "Force" option (but
  the server it is running in is left running) MDBs running
  on other servers in the cluster do not reconnect and consume
  messages once the destination is available again.

This APAR also introduces additional debug information into
the message store dump facility of a messaging engine.
This can be used to provide runtime information to
IBM customer support about a messaging engine, and the
messages within it.

To gather a message store dump from all messaging engines
in a cell, issue the following JACL from a wsadmin
session for the deployment manager:

set mes [$AdminControl queryNames type=SIBMessagingEngine,*]
set cmd com.ibm.ws.sib.msgstore.*
foreach me $mes { $AdminControl invoke $me dump $cmd }

This will produce files in the with names as follows:
  SIBdump-Node.Server-Bus-20081119190050030.xml
These files will be located on the nodes where the messaging
engines were running, in the logs/<servername> directory
of the profile.

Problem conclusion

The fix for this APAR is currently targeted for inclusion in
fixpack 6.0.2.33, 6.1.0.23 and 7.0.0.3.
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
PK75571
Reported component name
PLAT MSG COM
Reported component ID
620400101
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-13
Closed date
2008-11-19
Last modified date
2008-11-19

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
PLAT MSG COM
Fixed component ID
620400101

Applicable component levels

R100 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":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK75571: IMPROVEMENTS TO SERVICE INTEGRATION BUS BEHAVIOR IN RECOVERY SCENARIOS WITHIN COMPLEX TOPOLOGIES

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

R100 PSY

Document Information

Share your feedback

Need support?