Troubleshooting
Problem
On restarting Websphere Application Server, the messaging engine starts up successfully but CWSID0009E errors are written to the SystemOut.log:
Symptom
CWSID0009E: Destination XXX cannot be created.
FFDCS are produced with the following stack:
com.ibm.websphere.sib.exception.SIErrorException com.ibm.ws.sib.processor.impl.
DestinationManager.createDestinationLocalization 1:3000:1.461.1.14
Exception = com.ibm.websphere.sib.exception.SIErrorException
Source = com.ibm.ws.sib.processor.impl.DestinationManager.createDestinationLocalization
probeid =1:3000:1.461.1.14
Stack Dump = com.ibm.websphere.sib.exception.SIErrorException:
CWSIP0006E: An internal destination configuration error occurred to
destination XXX in DestinationManager,1:4115:1.461.1.14
at com.ibm.ws.sib.processor.impl.DestinationManager.
checkQueuePointContainsLocalME(DestinationManager.java:4112)
at com.ibm.ws.sib.processor.impl.DestinationManager.checkValid
LocalizationConfig(DestinationManager.java:3423)
Cause
The Bus/Messaging Engine was recreated in the configuration but the same database was used from a previous install. Only SIBOWNER table was cleared leaving the other sib tables as-is. Clearing just the SIBOWNER table will allow the messaging engine to start but it will not function correctly as old data still persists in the other tables.
Important Note: Modifying or deleting the datastore tables manually is not supported since there is
a risk of potential data loss . This must not be performed unless otherwise recommended by the IBM support team.
Resolving The Problem
Drop and recreate all the SIB tables for the messaging engine
Note: This solution must only be implemented if the SIBOWNER table was emptied or recreated while other SIB tables were left AS-IS
Product Synonym
WebSphere Application Server WAS SIB SIBUS SI BUS
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21608022