I have a simple route that reads incoming mesages from a JMS queue, sends
them to a webservice that hands back a response message that I then process
and record:
from("activemq:queueA").to("http://mywebservice";).process(new
DoSomething()).to("file://logs)

Currently, if the web service times out, this route blocks and doesn't
process other messages intended for the web service until the timeout period
ends at which point the held back messages get processed.

Is there a way to configure this route or a different kind of route to
accomplish the goal of allowing messages to continue moving through to the
web service even while one message is stilling being processed by the web
service?

I tried setting the MaxConnectionsPerHost to 5 as described under "Setting
MaxConnectionsPerHost" here:
http://camel.apache.org/http.html

However, I still saw the blocking behavior after making these configuration
changes.
-- 
View this message in context: 
http://old.nabble.com/Is-there-a-way-to-route-to-an-HTTP-Endpoint-without-blocking--tp26711302p26711302.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to