PM23626: A MEMORY LEAK WHEN PERFORMING A SYNCHRONOUS RECEIVES WITHIN A GLOBAL TRANSACTION THAT RETURNS NO MESSAGE

Fixes are available

APAR status

Closed as program error.

Error description

When using the Service Integration Bus a memory leak is observed
when using sychronous receives within a global transaction that
returns no message. This results in a large number of
com/ibm/ws/sib/comms/common/XidProxy objects, each owning 2
byte arrays, and owned by a java/util/HashMap$Entry object.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server Version 7.0
****************************************************************
* PROBLEM DESCRIPTION: A leak of XidProxy objects occurs       *
*                      for transactions where a messaging      *
*                      engine is enlisted, and returns         *
*                      XA_RDONLY to prepare.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem affects applications connecting to a messaging
engine over a network, and committing transactions after a
synchronous JMS receive call returns null.

The bus' network protocol is optimized to only enlist a
messaging engine into a transaction at the point where work is
about to be performed. This includes a synchronous JMS receive
call. If a synchronous JMS receive call does not return
a message, then no work is actually performed, and the
messaging engine correctly returns XA_RDONLY in the prepare
phase of the two-phase commit.

However, the messaging engine incorrectly fails to clean up an
internal XidProxy state object when it returns XA_RDONLY to
the network connected transaction manager in this scenario.

Problem conclusion

The fix for this APAR corrects the messaging engine code so
that it cleans up the XidProxy state object, when returning
XA_RDONLY to a network connected transaction manager after
becoming enlisted in a transaction.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.15.  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
PM23626
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
2010-09-30
Closed date
2010-12-02
Last modified date
2010-12-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
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

PM23626: A MEMORY LEAK WHEN PERFORMING A SYNCHRONOUS RECEIVES WITHIN A GLOBAL TRANSACTION THAT RETURNS NO MESSAGE

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?