WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Mechanisms for stopping messaging engines

You can stop messaging engines using different mechanisms and with different degrees of urgency. Stopping a messaging engine prevents it from sending any messages.

You can stop messaging engines by:

You can stop a messaging engine in two modes:
Immediate
In immediate mode, the messaging engine is stopped on completion of all the messaging operations that are current at the time of the stop request. No notification is sent to the application to indicate that the messaging engine is stopping. After a stop command has been issued, the messaging engine does not allow any new operations to be started.

For each existing connection, the messaging engine waits for the current operation to complete, unless the operation blocks within the messaging engine, such as a receive operation. In this case, the operation is interrupted. Asynchronous consumers are allowed to complete even though they may take an arbitrary amount of time to process the current message. The messaging engine then backs out of active transactions and disallows any further operations on that connection. When all connections are in this invalidated state, the messaging engine stops.

Force
In force mode, the messaging engine is stopped so that any current transactions are pre-empted and applications are forcefully disconnected.

Force mode is like immediate mode, except that stopping the messaging engine interrupts messaging operations on application threads that are taking place at the time that the stop command is issued. Rather than allowing existing messaging operations to complete, the messaging engine interrupts them and then disallows any further operations. When all connections are in this state, the messaging engine stops.

Force mode completes the shutdown of the messaging engine as fast as possible. A subsequent restart of the messaging engine might take longer than if it had been stopped using immediate mode, because more recovery actions are needed. For example, force mode stop can leave messages in-doubt and you must deal with these messages as described in Resolving indoubt transactions.

You can escalate an immediate stop that is taking too long to force a stop.

The following stop modes are possible for the different stop mechanisms:
Stop mechanism Immediate Force
Administrative console Yes Yes
JMX stop command Yes Yes
stopServer command Yes No
Note: If the messaging engine reports isAlive=false to the HA Manager, the whole application server process is stopped without completions of current transactions or cleanup. This result is equivalent to a forced stop.
Related tasks
Learning about high availability and workload sharing
Starting a messaging engine
Stopping a messaging engine

Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/concepts/cjk0200_.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)