Troubleshooting
Problem
In WebSphere, if a bus member is removed and re-added to the same bus, the message engine will not start and errors will be seen in the systemout logs.
Symptom
The following error will be seen in the systemout.log:
CWSIS1535E: The messaging engine's unique id does not match that found in the data store. ME_UUID=E52AB8AEE2F05510, ME_UUID(DB)=A15FEDAF0185937C
Resolving The Problem
If you are using a JDBC store for your message engine data store, stop the WebSphere application server and log in to the database that hosts the tables for the data store. Drop all tables that are related to the message engine's data store. There are 8 tables and they will all start with the first 3 letters "SIBxxx".
Be aware that you will lose any messages currently stored in the data store.
The follow is the list of tables you will find that will need to be dropped:
SIB000
SIB001
SIB002
SIBCLASSMAP
SIBKEYS
SIBLISTING
SIBOWNER
SIBXACTS
Once these tables are dropped from the database, restart the WebSphere application server and WebSphere will recreate these tables automatically with the correct message engine data store's unique id.
If you are using the default cloudscape database for your message engine data stores, stop the WebSphere application server and navigate in your application server's file system to the folder:
IBM\WebSphere\AppServer\profiles\<your_profile_dir>\databases\com.ibm.ws.sib\
You will see a list of message engine names.
Delete the folder that corresponds to your message engine name that will not start and restart the WebSphere application server.
Be aware that you will lose any messages currently stored in the data store.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21328985