Hello,

Currently we have a 2-node WebSphere ND 8.5 cluster with SIBus configuration. We are now migrating this setup to a new Hardware, similar to lift and shift.

Issue: When we stop the JVM's on the existing setup and then start the JVM's  on the new setup, the message engine does not start and we see below errors in the logs.

CWSIS1561E: The messaging engine's unique id does not match that found in the file store. ME_UUID=C0615BFF4468960F, ME_UUID(FS)=0791A2ABCDBD631C
CWSIS1567E: Messaging engine IS_SIB_A cannot obtain the lock on its file store, which ensures it has exclusive access to the data.
CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.TransactionException: CWSIS1099E: An unexpected exception has occurred. Exception: com.ibm.ws.sib.msgstore.MessageStoreUnavailableException: Operation not possible as MessageStore is unavailable!
CWSIS1589I: The file store has stopped successfully.
CWSID0035E: Messaging engine IS_SIB_A cannot be started; detected error reported during com.ibm.ws.sib.msgstore.impl.MessageStoreImpl start()


The important error here is 
CWSIS1561E: The messaging engine's unique id does not match that found in the file store. ME_UUID=C0615BFF4468960F, ME_UUID(FS)=0791A2ABCDBD631C

Since both our old & new setup have the same messaging engine name i.e. IS_SIB_A, i think there is a conflict due to entries in the message store due to old and new name being the same but with different ME_UUID.

We are using Message store as File store. Both old and new setup reference the same paths to the file store.

Searching online, most solutions point to shutting down old setup jvms, deleting the file store and then starting the new setup jvm's.

I wanted to ask if there is a more elegant way of doing the switch from an old to new setup, rather than deleting/backing up the old file store. We would ofcourse take care of consuming all the messages before the switch.

Thanks for your help !


------------------------------
Murtuza Matiwala
------------------------------

Hi, if the configurations are exactly the same then this should not happen.  Where all the JVMs in the cluster and on the hosts shutdown before lift and shift?  If not then it is trying to get a lock on file and will never succeed.  And unfortunately the only way to clear this up is to delete the files and restart.  I should note that best practice for production is to have the store in a database.

More info about your error here:
https://www.ibm.com/support/pages/cwsis1535e-messaging-engines-unique-id-meuuid-does-not-match-found-data-store


------------------------------
Brian S Paskin
Senior WebSphere and MQ Performance Architect
IBM
Cambridge MA
------------------------------

Original Message:
Sent: Thu February 25, 2021 08:48 AM
From: Murtuza Matiwala
Subject: WebSphere SIBus Migration

Hello,

Currently we have a 2-node WebSphere ND 8.5 cluster with SIBus configuration. We are now migrating this setup to a new Hardware, similar to lift and shift.

Issue: When we stop the JVM's on the existing setup and then start the JVM's  on the new setup, the message engine does not start and we see below errors in the logs.

CWSIS1561E: The messaging engine's unique id does not match that found in the file store. ME_UUID=C0615BFF4468960F, ME_UUID(FS)=0791A2ABCDBD631C
CWSIS1567E: Messaging engine IS_SIB_A cannot obtain the lock on its file store, which ensures it has exclusive access to the data.
CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.TransactionException: CWSIS1099E: An unexpected exception has occurred. Exception: com.ibm.ws.sib.msgstore.MessageStoreUnavailableException: Operation not possible as MessageStore is unavailable!
CWSIS1589I: The file store has stopped successfully.
CWSID0035E: Messaging engine IS_SIB_A cannot be started; detected error reported during com.ibm.ws.sib.msgstore.impl.MessageStoreImpl start()


The important error here is 
CWSIS1561E: The messaging engine's unique id does not match that found in the file store. ME_UUID=C0615BFF4468960F, ME_UUID(FS)=0791A2ABCDBD631C

Since both our old & new setup have the same messaging engine name i.e. IS_SIB_A, i think there is a conflict due to entries in the message store due to old and new name being the same but with different ME_UUID.

We are using Message store as File store. Both old and new setup reference the same paths to the file store.

Searching online, most solutions point to shutting down old setup jvms, deleting the file store and then starting the new setup jvm's.

I wanted to ask if there is a more elegant way of doing the switch from an old to new setup, rather than deleting/backing up the old file store. We would ofcourse take care of consuming all the messages before the switch.

Thanks for your help !


------------------------------
Murtuza Matiwala
------------------------------