Issues when suspeding JMSConsumers with "receiveTimeout"

[jpeschke <pe...@etone.de>]

Hello,
I followed Claus' suggestion about implementing an own route policy for
throttling the reception of incoming JMS messages if there is too much work
to be done (see  Limit number of JMS messages when processing asynchronously
<http://camel.465427.n5.nabble.com/Limit-number-of-JMS-messages-when-processing-asynchronously-td5774822.html> 
).
Actually, this works like a charm (Again, thank you Claus!) :).

The only issue I still have is with the "receiveTimeout" setting of the JMS
Consumer:
When I suspend the consumer via the "stopConsumer" method of the 
RoutePolicySupport
<https://camel.apache.org/maven/camel-2.15.0/camel-core/apidocs/org/apache/camel/impl/RoutePolicySupport.html> 
, it seems that Camel waits for the blocking  receive(long timeout)-Method
<http://docs.oracle.com/javaee/6/api/javax/jms/MessageConsumer.html#receive(long))>  
before it completely suspends the consumer.
So if I choose a high value for the "receiveTimeout" setting to prevent too
many reconnects, the suspension can take a lot of time.


Is there any way of working around this issue? We are still using Camel
2.13.1 (switching to a later version is planned), maybe there are
workarounds in a later Camel version?

Thank you in advance for any thoughts, ideas and suggestions.

Best regards,
Joerg






--
View this message in context: http://camel.465427.n5.nabble.com/Issues-when-suspeding-JMSConsumers-with-receiveTimeout-tp5776663.html
Sent from the Camel - Users mailing list archive at Nabble.com.