Re: jms limiting

[Michal]

Instead of controlling target endpoint (cpu intensive) you could control the
endpoint that sends the message: jms in this case. jms:consumer by default
sends only one message at a time - and waits for the response from the
target endpoint.
-- 
View this message in context: 
http://www.nabble.com/jms-limiting-tp15070635s12049p15154974.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.