From 46114ab4cbb66cfd84fa99dcb6e8c6373ca7fb2f Mon Sep 17 00:00:00 2001 From: Oleg Zhurakousky Date: Wed, 7 Sep 2011 08:23:42 -0400 Subject: [PATCH] INT-2109 updated JMS schema documentation to document DMLC attributes --- .../jms/config/spring-integration-jms-2.1.xsd | 108 +++++++++++++++--- 1 file changed, 94 insertions(+), 14 deletions(-) diff --git a/spring-integration-jms/src/main/resources/org/springframework/integration/jms/config/spring-integration-jms-2.1.xsd b/spring-integration-jms/src/main/resources/org/springframework/integration/jms/config/spring-integration-jms-2.1.xsd index 40966cad29..f01f48e1a7 100644 --- a/spring-integration-jms/src/main/resources/org/springframework/integration/jms/config/spring-integration-jms-2.1.xsd +++ b/spring-integration-jms/src/main/resources/org/springframework/integration/jms/config/spring-integration-jms-2.1.xsd @@ -451,14 +451,11 @@ - - - - + - - - + + + @@ -679,14 +676,10 @@ - - - - - - - + + + @@ -1182,5 +1175,92 @@ + + + + + + Specify the number of concurrent consumers to create. Default is 1. + Specifying a higher value for this setting will increase the standard + level of scheduled concurrent consumers at runtime: This is effectively + the minimum number of concurrent consumers which will be scheduled + at any given time. This is a static setting; for dynamic scaling, + consider specifying the "maxConcurrentConsumers" setting instead. + Raising the number of concurrent consumers is recommendable in order + to scale the consumption of messages coming in from a queue. However, + note that any ordering guarantees are lost once multiple consumers are + registered + + + + + + + Specify the maximum number of concurrent consumers to create. Default is 1. + If this setting is higher than "concurrentConsumers", the listener container + will dynamically schedule new consumers at runtime, provided that enough + incoming messages are encountered. Once the load goes down again, the number of + consumers will be reduced to the standard level ("concurrentConsumers") again. + Raising the number of concurrent consumers is recommendable in order + to scale the consumption of messages coming in from a queue. However, + note that any ordering guarantees are lost once multiple consumers are + registered. + + + + + + + Specify the level of caching that this listener container is allowed to apply: + CACHE_NONE = 0 + CACHE_CONNECTION = 1 + CACHE_SESSION = 2 + CACHE_CONSUMER = 3 + + + + + + + Specify the maximum number of messages to process in one task. + More concretely, this limits the number of message reception attempts + per task, which includes receive iterations that did not actually + pick up a message until they hit their timeout + + + + + + + + Interval in miliseconds between the recovery attempts + + + + + + + Specify the limit for the number of consumers that are allowed to be idle at any given time. + This limit is used to determine if a new invoker should be created. Increasing the limit causes + invokers to be created more aggressively. This can be useful to ramp up the + number of invokers faster. + The default is 1, only scheduling a new invoker (which is likely to + be idle initially) if none of the existing invokers is currently idle. + + + + + + + Specify the limit for idle executions of a consumer task, not having + received any message within its execution. If this limit is reached, + the task will shut down and leave receiving to other executing tasks. + The default is 1, closing idle resources early once a task didn't + receive a message. + + + + + \ No newline at end of file