B2B Integration 10.5 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Managing JMS Triggers | Delaying Polling Requests for Concurrent JMS Triggers | How JMS Trigger Delays a Polling Request | Examples of Extended Polling Delay Configuration
 
Examples of Extended Polling Delay Configuration
To further illustrate how you might configure an extended polling delay for concurrent JMS triggers, consider the following examples.
Example 1
Suppose that the server configuration parameters for an extended polling delay and concurrent JMS trigger polling interval are set as follows. Keep in mind that the parameters are measured in milliseconds.
*watt.server.jms.trigger.extendedDelay.delays = 100, 200, 1000
*watt.server.jms.trigger.extendedDelay.delayIncrmentInterval = 5000
As soon as the JMS trigger becomes inactive, the JMS trigger waits the polling delay of 100 milliseconds and then polls the JMS provider for more messages. The JMS trigger continues polling, waiting the 100 milliseconds specified by the extended delay between polling requests. If 5000 milliseconds elapse and the JMS trigger remains inactive, the JMS trigger begins using a 200 millisecond delay between polling requests. After 5000 more milliseconds, if the JMS trigger remains inactive, the JMS trigger begins to use an extended delay of 1000 milliseconds. The JMS trigger continues to use the 1000 millisecond extended delay until a polling request returns one or more messages.
Example 2
When Integration Server is configured to use an extended polling delay for concurrent JMS triggers, the first delay takes place as soon as the JMS trigger becomes inactive. If you want the JMS trigger to use an extended delay only after the interval specified by watt.server.jms.trigger.extendedDelay.delayIncrementInterval elapses, use 0 as the first value in watt.server.jms.trigger.extendedDelay.delays.
Suppose that the server configuration parameters for an extended polling delay and concurrent JMS trigger polling interval are set as follows. Keep in mind that the parameters are measured in milliseconds.
*watt.server.jms.trigger.extendedDelay.delays = 0, 10000
*watt.server.jms.trigger.extendedDelay.delayIncrmentInterval = 3600000
After the JMS trigger has been inactive for an hour (3600000 milliseconds), the JMS trigger waits the polling delay of 10000 milliseconds and then polls the JMS provider for more messages. If the polling request does not return any messages, the JMS trigger waits 10000 milliseconds and then polls the JMS provider for more messages. The JMS trigger continues polling in this way until a polling request returns a message.

Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.