Enabling, Disabling and Suspending a JMS Trigger
You can manage JMS triggers and the amount of resources they consume by changing the state of a JMS trigger.
Using the Command Central, you can:
Enable, disable, or suspend all JMS triggers
Enable, disable, or suspend all the JMS triggers of a specific type (standard or SOAP-JMS)
Enable, disable, or suspend specific JMS triggers
You might want to change the state of all JMS triggers at once as a quick way of freeing up server resources. This can be especially helpful in a situation in which Integration Server is functioning under heavy load and additional resources are needed immediately.
To enable, disable, or suspend JMS triggers
1. Select the Integration Server environment from the Environment pane, then click the instance from the Instances tab.
2. Click the Administration tab.
3. Select the JMS Trigger Management configuration type from the drop-down list.
4. If you want to change the state of all JMS triggers, do the following:
a. On the Instances > Administration > JMS Trigger Management screen, click Edit All JMS Triggers.
The Edit All screen appears.
b. Select the state that you want to apply to all JMS triggers.
5. If you want to change the state of a specific JMS trigger, do the following:
a. Under Individual JMS Trigger Controls, in the row for the JMS trigger that you want to enable, disable, or suspend, click the text enabled, disabled, or suspended in the State column.
b. On the Instances > Administration > JMS Trigger Management > Edit Triggers State screen, in the New State list, select the state that you want to apply to this JMS trigger.
6. Click Save Changes.
Notes:
If you want to disable a JMS trigger, first suspend the JMS trigger and wait for all the processing threads complete. Then, disable the JMS trigger. You can view the number of threads currently used by a JMS trigger on the
Instances > Administration > JMS Trigger Management screen.
When you disable a JMS trigger,
Integration Server does the following:
If the JMS trigger is waiting before making a retry attempt,
Integration Server interrupts processing for the JMS trigger.
If the JMS trigger is currently processing messages,
Integration Server waits a specified amount of time before forcing the JMS trigger to stop processing messages. If it does not complete in the allotted time,
Integration Server stops the message consumer used to receive messages for the JMS trigger and closes the JMS session. At this point the server thread for the JMS trigger continues to run to completion. However, the JMS trigger will not be able to acknowledge the message when processing completes. If the delivery mode of the message is set to persistent, this can lead to duplicate messages.
The time Integration Server waits between the request to disable the JMS trigger and forcing the trigger to stop is specified by the watt.server.jms.trigger.stopRequestTimeout property.
Because administered objects, like destinations, are configured outside of
Integration Server, disabling a JMS trigger has no impact on the subscription.
If a JMS trigger is processing messages at the time it is suspended, the JMS trigger will complete processing of those messages. The JMS trigger also acknowledges the messages to the JMS provider.
