Avoiding locked event or in-doubt status when shutting down and restarting servers
To avoid a locked event or transaction in doubt status when shutting down IBM® Business Monitor servers, you must shut down and restart the servers and clusters in the correct order. The shutdown and restart steps are required in a multi-clustered IBM Business Monitor environment.
- Messaging engine
- Common Event Infrastructure (CEI) Note: The Common Event Infrastructure is deprecated in IBM Business Monitor 8.5.7.
- Server monitor model applications (includes monitor model logic and moderator modules)
A locked event situation can occur when the messaging engine cannot resolve the acknowledgment of the transactions initiated by the other components. Messages are marked as locked or in-doubt in the messaging engine database. When the servers are back up and running, and when a locked or an in-doubt state exists in the messaging engine database, you can select either a rollback or a commit for the affected transactions. Rollback refers to the in doubt transactions being rolled back on the other participants, as well as on the messaging engine, to be consistent. Commit means that the in-doubt transaction is committed for the other participants and that the messaging engine must also be committed for consistency.