If necessary, you can manually restart the object queue dispatcher from NexJ System Admin Console.
Only restart the object queue dispatcher if necessary, for example, when the dispatcher is experiencing problems. For example, restart the dispatcher as an alternative to restarting the dispatcher node or running manual SQL queries. Restarting the dispatcher results in the loss of transient messages that have not yet been delivered.
To restart the object queue dispatcher:
- In NexJ System Admin Console, navigate to the Statistics page.
Find and expand the node for your NexJ application, for example, expand nexj.finance.
This functionality is only available for the NexJ application.
- Select the Administration node. The statistics for the node display on top of the details area. Any available commands display on the bottom of the details area.
- Double-click on the restartDispatcher command. The Invoke restartDispatcher command dialog opens.
Click the Invoke button. Diagnostic information for the current node displays in the Result area.
You can view diagnostic dumps in application logs for the other nodes in the cluster.
- Click the Close button on the top right corner of the dialog. The Invoke restartDispatcher command dialog closes.
You have restarted the object queue dispatcher.
You can also restart the dispatcher from the Object Queues page in NexJ System Admin Console.