Properties for Transacted JMS Triggers

Integration Server and Designer provide different properties for a transacted JMS trigger than for a non-transacted JMS trigger. The following list identifies properties that are specific to transacted JMS triggers, specific to non-transacted JMS triggers, or apply to both but must be set to a particular value for transacted JMS triggers.

For transacted JMS triggers, message acknowledgement is handled by the transaction; the acknowledgement mode does not apply. Consequently, Designer does not display the Acknowledgement mode property for a transacted JMS trigger.

A transacted JMS trigger can only use Any (OR) joins, for which you do not need to specify a join time-out. Because All (AND) and Only one (XOR) joins cannot be used, Designer does not display the Join expires and Expire after properties for a transacted JMS trigger.

A transacted JMS trigger can be used for batch processing if the JMS connection alias used by the trigger connects to a JMS provider that supports reuse of transacted JMS sessions. If the JMS provider does not support reuse of transacted JMS sessions, set Max batch processing to 1.

Consult the documentation for your JMS provider to determine whether or not the JMS provider supports the reuse of transacted JMS sessions. Note that webMethods Broker version 8.2 and higher, webMethods Universal Messaging version 9.5 SP1 and higher, and webMethods Nirvana version 7 and higher support the reuse of transacted JMS sessions.

Because a transaction is an all or nothing situation, a trigger service cannot retry a message if a trigger service ends because of a transient error. Designer does not display the retry properties (Max retry attempts, Retry interval, and On retry failure) for a transacted JMS trigger.

You can specify how Integration Server handles a transient error that causes the transaction to be rolled back. Designer displays an On transaction rollback property that you can use to specify whether Integration Server simply recovers the message from the JMS provider or whether it suspends the JMS trigger in addition to recovering the message. For more information about transient error handling for transacted JMS triggers, see Transient Error Handling for Transacted JMS Triggers.