PK95275: POSSIBLE DEADLOCK USING WEBSPHERE MQ SERVER MEMBERS OF A SERVICE INTEGRATION BUS

Fixes are available

APAR status

Closed as program error.

Error description

WSVR0605W messages are displayed in the JVM logs of a server
hosting a messaging engine, used to communicate with a WebSphere
MQ queue manager that has been made a member of the bus using
a WebSphere MQ Server object.

A javacore shows one thread stuck in:
  com.ibm.ws.sib.processor.impl.RMQLocalConsumerPoint.close()
Another thread is stuck in:
  com.ibm.ws.sib.processor.impl.
                         RMQLocalConsumerPoint.internalStop()

Local fix

Restart the server hosting the messaging engine.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server Version 7.0*
****************************************************************
* PROBLEM DESCRIPTION: Deadlock after a connection             *
*                      is lost between a messaging engine      *
*                      and a queue manager made a              *
*                      WebSphere MQ Server member of a bus     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A deadlock might occur when the connection to a queue manager
that has been made a WebSphere MQ Server member of a service
integration bus is lost at a particular stage during
consumption of messages.

The deadlock occurs because of incorrect exception handling
in a resource adapter thread that encounters the broken
connection at the point it is deleting a message before
calling into the message-driven bean, and a thread within the
messaging engine attempting to pass a new message to the
resource adapter for delivery to the message-driven bean.

Problem conclusion

The fix for this APAR corrects the exception handling so that
the deadlock does not occur.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK95275
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-02
Closed date
2009-10-20
Last modified date
2009-10-20

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
620800101

Applicable component levels

R300 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

PK95275: POSSIBLE DEADLOCK USING WEBSPHERE MQ SERVER MEMBERS OF A SERVICE INTEGRATION BUS

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

R300 PSY

Document Information

Share your feedback

Need support?