Why does my messaging engine fail to start after restarting WAS?
I am seeing the following error in the SystemOut.log:
CWSIS1561E:The messaging engine's unique id does not match that found in the filestore. ME_UUID=A85B64156006973D, ME_UUID(FS)=AAF19AC8C805638A
Answer by Geeta Nadella (1052) | Apr 23, 2015 at 12:22 PM
CWSIS1561E errors are usually caused by deleting the messaging engine, without deleting its filestore, then recreating the messaging engine with the same name. To fix the issue, you will have to delete the existing filestore files for the messaging engine and restart the JVM. A new filestore will be created during the messaging engine startup.
Note1: You must treat the log file, the temporary store file, and the permanent store file as one unit; that is, delete operation must be performed on all three files.
Note2:By performing the suggested action, all the messages in the filestore will be lost.
Why do we get ArrayIndexOutOfBoundsException after a messaging engine failover in WAS 8.5.5? 1 Answer
Why does my SIBUS messaging engine fail to start after a restart of WAS server? 1 Answer
How Can I publish messages to multiple nodes at the same time and avoid single point of failure? 1 Answer
Why is my WAS 8.5 messaging engine not starting after database restart? 1 Answer
In WebSphere Application Server, how to enable the disabled messaging Engine via the admin console? 1 Answer