watt.server.control.triggerInputControl.delayIncrementInterval = 10000watt.server.control.triggerInputControl.delayIncrementInterval = 10000watt.server.control.triggerInputControl.delays = 500,1000,1500,5000Stage | Description | ||
1 | The webMethods messaging trigger becomes inactive. Integration Server considers a webMethods messaging trigger to be inactive if the trigger did not receive any documents in the last request to the Broker. | ||
2 | Integration Server begins to delay polling requests using the formula inactiveTime/interval = delay to determine the length of the polling delay. Using the defaults for the server parameters as stated above, Integration Server determines the length of the polling delay using this equation: 0/1000 = 0 The delay at the zero index position of the watt.server.control.triggerInputControl.delays property is 500. Integration Server will wait 500 milliseconds and then poll the Broker for more documents. | ||
3 | If the polling request does not return any documents for the webMethods messaging trigger, Integration Server determines the length of the polling delay using this equation: 500/10000 = 0.05 Integration Server rounds the calculated delay of 0.05 down to 0. The delay at the zero index position of the watt.server.control.triggerInputControl.delays property is 500. Integration Server will wait 500 milliseconds and then poll the Broker for more documents. | ||
4 | If the trigger remains inactive Integration Server continues to determine the polling delay using the formula inactiveTime/interval = delay where the inactiveTime increases by 500 milliseconds each time. | ||
5 | When the trigger has been inactive for 10000 milliseconds, Integration Server determines the length of the polling delay using this equation: 10000/10000 = 1 The delay at the first index position of the watt.server.control.triggerInputControl.delays property is 1000. Integration Server will wait 1000 milliseconds and then poll the Broker for more documents. | ||
6 | If the trigger remains inactive Integration Server continues to determine the polling delay using the formula inactiveTime/interval = delay where the inactiveTime increases by 1000 milliseconds each time.
| ||
7 | When the trigger has been inactive for 20000 milliseconds, Integration Server determines the length of the polling delay using this equation: 20000/10000 = 2 The delay at the second index position of the watt.server.control.triggerInputControl.delays property is 1500. Integration Server will wait 1500 milliseconds and then poll the Broker for more documents. | ||
8 | If the trigger remains inactive Integration Server continues to determine the polling delay using the formula inactiveTime/interval = delay where the inactiveTime increases by 1500 milliseconds each time. | ||
9 | When the trigger has been inactive for 30000 milliseconds, Integration Server determines the length of the polling delay using this equation: 30000/10000 = 3 The delay at the third index position of the watt.server.control.triggerInputControl.delays property is 5000. Integration Server will wait 5000 milliseconds and then poll the Broker for more documents. | ||
10 | If the trigger remains inactive Integration Server continues to determine the polling delay using the formula inactiveTime/interval = delay where the inactiveTime increases by 5000 milliseconds each time. Because 5000 is the largest value specified in the array for watt.server.control.triggerInputControl.delays, the polling delay will never be more than 5000 milliseconds. Integration Server uses this polling delay until the trigger becomes active.
| ||
11 | When a polling request to the Broker returns one or more documents, Integration Server considers the trigger to be active and stops using a polling delay. |
