Starting and Stopping Message-Driven Beans 

Use

Use this procedure when you want to set a server process in debug mode.

Message-driven beans whose destination type is Topic always run on only one server process in the cluster because they have only one registered message listener. Therefore, if you intend to debug a server process (in this case all applications running on that server process will be stopped), you must first ensure that there are no message-driven beans running on that server process and then proceed with the debug process. In case the applications contain message-driven beans, first you have to stop all message-driven beans on that server process and then start them on another server process in the cluster (which is not in debug mode). After you have finished debugging the corresponding server process, you can either leave the message-driven beans to run on the other server process, or you can stop them and restart them on the initial server process that has been debugged.

Message-driven beans whose destination type is Queue usually run on all server nodes in the cluster. Therefore, if your applications contain only message-driven beans with destination type Queue and you want to debug a server process, you only have to stop the message-driven beans on that server process, you do not have to start them on another server process in the cluster.

Prerequisites

·        You are going to debug a server process.

·        Your applications contain message-driven beans.

Procedure

Stopping Message-Driven Beans

Use the STOP_MDB shell command from the EJB group of shell commands.

The message-driven beans are stopped on that server process. Make sure that your message-driven beans are running on another server process in the cluster.

Starting Message-Driven Beans

Use the START_MDB shell command from the EJB group of shell commands.

If the message-driven beans are running on another server process, this command will be ignored and the message-driven beans whose destination type is Topic will not be started on the server process on which you execute the command. If the message-driven beans are already running on the same server process on which you execute the shell command, the command will be ignored.

 

For more information about the EJB group of shell commands, see EJB (in the Reference Manual).

For more information about using shell commands, see Connecting and Working Using Telnet.

For more information how to set a server process in debug mode, see Config Tool.