WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer messaging enginesStopping a messaging engine
We can either stop a messaging engine directly or stop it by stopping the server that hosts the messaging engine. A messaging engine can stop in two ways:
- Immediate
- The messaging engine is stopped on completion of all messaging operations that are being carried out at the time of the stop request.
- Force
- The messaging engine is stopped without allowing messaging operations to complete and applications are forcefully disconnected.
To stop a messaging engine, use the dmgr console to complete the following steps.
- In the navigation pane, click Service integration -> Buses.
- In the content pane, click the name of the bus the messaging engine belongs to.
- Do one of the following to display a list of messaging engines:
- For a list of messaging engines in the bus, in the content pane, under Topology, click Messaging engines.
- For a list of messaging engines for a server, in the content pane, under Topology, click Bus Members. Click the name of the required server.
- For a list of messaging engines for a cluster, in the content pane, under Topology, click Bus Members. Click the name of the required cluster.
- Select the messaging engine to stop.
- Select Immediate or Force from the Stop mode drop-down list.
- Click Stop.
If an immediate stop is taking too long, we can escalate it to a force stop by selecting the Force option. This overrides your previous selection of the Immediate option.
Related concepts:
Messaging engines
Mechanisms for stopping messaging engines
Related
Display the runtime properties of a messaging engine
Related information:
Messaging engine troubleshooting tips