PK95659: SERVICE INTEGRATION BUS REPORTS CWSIA0067E AND CWSIK0027E (CORRUPT TOPIC) AT MESSAGING ENGINE STARTUP.

Fixes are available

APAR status

Closed as program error.

Error description

WebSphere Applicaiton Server ND 6.1.0.21. Service Integration
Bus.

You have multiple application servers as individual bus members,
each having a message engine using a file store as the message
store.  Some of them fail with CWSIA0067E, CWSIK0027E and
CWSIP0251E (High message threshold), these messages are in
SystemOut.log.

The output of printSIBusSummary.py confirms that several of the
topic destinations have 50,000 or more messages. The one that is
identified as corrupted, has an additional error:

depth="50000" highMessageThreshold="0" sendAllowed="0"
error="[1]: com.ibm.ws.scripting.ScriptingException:
com.ibm.ws.scripting.ScriptingException:
javax.management.MBeanException: Exception thrown in
RequiredModelMBean while trying to invoke operation
getSubscriptions"

Local fix

Increase the log size for the filestore from 100MB to 150MB.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server Version 6.1*
*                  or Version 7.0, using publish/subscribe     *
*                  messaging with with multiple messaging      *
*                  engines in a service integration bus        *
****************************************************************
* PROBLEM DESCRIPTION: Corrupt publication point after         *
*                      a CWSOM0005W warning is logged          *
*                      indicating a transaction rollback       *
*                      during messaging engine startup         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Exceptions containing the following message are thrown to
applications, indicating a corrupt publication point:
com.ibm.ws.sib.processor.exceptions.
SIMPDestinationCorruptException: CWSIK0027E: The destination
with name TOPIC_SPACE_NAME is corrupt.

There are multiple messaging engines in the bus, and the
messaging engine the application is connected to is using a
file store for the message store.

Inspection of the JVM shows the following warning logged
during startup of the messaging engine:
CWSOM0005W: The ObjectManager found that the logFile was too
full and will back out transaction
InternalTransaction(4.31)/ActivePersistent/38643864.

An FFDC is found as follows:
Exception = com.ibm.wsspi.sib.core.exception.SIRollbackException
Source = com.ibm.ws.sib.processor.impl.store.itemstreams.
              SourceProtocolItemStream.reconstituteSourceStreams
Stack Dump =
com.ibm.wsspi.sib.core.exception.SIRollbackException:
CWSIS1002E: An unexpected exception was caught during
transaction completion. Exception:
com.ibm.ws.sib.msgstore.PersistenceException: Exception caught
deleting from object store: CWSOM1011E: An invalid operation
was attempted on
Object=InternalTransaction(4.32)/Inactive/38643864 while it
was in state=16(int) Terminated(String).

The problem is caused by the messaging engine attempting to
delete a large number of publications within a single
transaction, during startup. The transaction is rolled back
because it is too large, and the resulting exception causes
the publication point to be marked corrupt.

The messages are being deleted, as they were queued for
delivery other messaging engines in the bus that no longer
require a copy of those publications (the proxy subscriptions
from those messaging engines have been deleted).

Problem conclusion

The fix for this APAR limits the size of the transaction used
by the messaging engine to delete publications queued for
delivery to remote messaging engines during startup.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.29 and 7.0.0.9.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

The failure might be intermittent, and restarting server
hosting the messaging engine with the corrupt publication
point might resolve the problem.

Comments

APAR Information

APAR number
PK95659
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-08
Closed date
2009-09-29
Last modified date
2009-11-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
620600101

Applicable component levels

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

Document Information

Modified date:
29 December 2021

Tips

PK95659: SERVICE INTEGRATION BUS REPORTS CWSIA0067E AND CWSIK0027E (CORRUPT TOPIC) AT MESSAGING ENGINE STARTUP.

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

R200 PSY

Document Information

Share your feedback

Need support?