PM61615: MEMORY LEAK WHEN WAS V8.0 SERVICE INTEGRATION BUS MESSAGING ENGINE IS CONFIGURED TO USE A FILESTORE AS ITS MESSAGESTORE

Fixes are available

APAR status

Closed as program error.

Error description

In WebSphere Application Server v8.0.x, when a Service
Integration Bus messaging engine is configured to use a
filestore and "Share data source with CMP" property is
enabled on the activation specification then a
memory leak is observed . Heap dump analysis shows primary
leak suspect as:com.ibm.ws.sib.processor.impl.ConnectionImpl
The following error is written to the SystemOut.log:

javax.resource.spi.ResourceAdapterInternalException:
CWSIV1203E: The transaction com.ibm.ws.sib.msgstore.
transactions.MSDelegatingLocalTransaction@b5674af returned
from the connection did not implement the expected interface
javax.transaction.Synchronization.
at com.ibm.ws.sib.ra.inbound.impl.SibRaSynchronizedDispatcher.
getTransactionForDelete(SibRaSynchronizedDispatcher.
java:381)
at com.ibm.ws.sib.ra.inbound.impl.SibRaSynchronizedDispatcher.
beforeDelivery(SibRaSynchronizedDispatcher.java:279)
at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch
(SibRaDispatcher.java:861)
at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener
$SibRaWork.run(SibRaSingleProcessListener.java:552)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:608)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server            *
****************************************************************
* PROBLEM DESCRIPTION: When using the default messaging        *
*                      provider (Service Integration Bus) of   *
*                      WebSphere Application Server, with file *
*                      store as the Datastore if activation    *
*                      specification is configured with the    *
*                      option "Share data source with CMP"     *
*                      selected ,then exception CWSIV1203E is  *
*                      observed in traces and this setting was *
*                      observed to be causing a memory leak in *
*                      com.ibm.ws.sib.processor.impl.Connectio *
*                      nImpl.                                  *
****************************************************************
* RECOMMENDATION:  "Share data source with CMP" option in the  *
*                  activation specification should not be      *
*                  enabled                                     *
*                  for a messaging engine that uses file store *
*                  as                                          *
*                  its datastore.                              *
****************************************************************
When "Share data source with CMP" is enabled in the activation
specification for a messaging engine that uses filestore as its
datastore, then a memory leak is observed in the
"com.ibm.ws.sib.processor.impl.ConnectionImpl" objects because
we create SibRaSynchronizedDispatcher but we cannot use it since
the SibRaSynchronizedDispatcher does not apply for a file store.
Along with the memory leak, the following exception is also
observed:
(com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener)
[:/b555200]
Tracing exception:
javax.resource.spi.ResourceAdapterInternalException: CWSIV1203E:
The transaction
com.ibm.ws.sib.msgstore.transactions.MSDelegatingLocalTransactio
n@b5674af returned from the connection did not implement the
expected interface
javax.transaction.Synchronization.
at
com.ibm.ws.sib.ra.inbound.impl.SibRaSynchronizedDispatcher.getTr
ansactionForDelete(SibRaSynchronizedDispatcher.java:381)
at
com.ibm.ws.sib.ra.inbound.impl.SibRaSynchronizedDispatcher.befor
eDelivery(SibRaSynchronizedDispatcher.java:279)
at
com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDis
patcher.java:861)
at
com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaW
ork.run(SibRaSingleProcessListener.java:552)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:608)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659)

Problem conclusion

The code has been modified to ensure that there is a check
being
made to ensure that "SibRaSynchronizedDispatcher" is created
only when the messaging engine uses database as its data store
and  whenever the property "Share data source with CMP" is
enabled in the activaiton specification. This ensures that
there
is no memory leak or the above exception "CWSIV1203E" observed.

The fix for this APAR is currently targeted for inclusion in
fix
pack 7.0.0.25, 8.0.0.6 and 8.5.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
PM61615
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-02
Closed date
2012-07-10
Last modified date
2012-07-10

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
WAS SIB & SIBWS
Fixed component ID
620800101

Applicable component levels

R300 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:
28 October 2021

Tips

PM61615: MEMORY LEAK WHEN WAS V8.0 SERVICE INTEGRATION BUS MESSAGING ENGINE IS CONFIGURED TO USE A FILESTORE AS ITS MESSAGESTORE

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?