> I know that I will get the result when the request is solved in queue, but
> for example, when I am processing big amount of data, I don't want to wait
> 20 seconds.
You won't wait. :) You will submit task to the queue and immediately
return control to the "response" bean at the end of the route
Write two routes: one that writes to a JMS queue and one that picks up data
off the queue and processes it:
from("direct:input").to("activemq:queue:inbox");
from("activemq:queue:inbox"). .
to("activemq:queue:results");
This manner you can shove data in as fast as you want and even have
concurren
Hi hekonsek,
I know that I will get the result when the request is solved in queue, but
for example, when I am processing big amount of data, I don't want to wait
20 seconds. I can use "to("direct:foo")" for this purpose. I just want add
the requests to the queue and return result right away(like
> If you are not using InOnly pattern
If you *are* using InOnly pattern
Hi Roman,
> I simply need to send request to add user and immediately
> receive response that it was added in the queue and is being processed
Your route seems to do it :) . If you are not using InOnly pattern
(just as you do), Camel will proceed to bean:response as soon as the
JMS message will b
