I'm struggling to understand SEDA queue behavior in terms of asynchronous
behavior.  My understanding from the documentation is that if
"concurrentConsumers > 1" it should spawn multiple threads to handle
requests.  However, it doesn't seem like this is currently working correctly
and I'm sure that I'm missing something stupid.  

I have a route that is configured to route
"seda://request_handler_tmb?concurrentConsumers=10&size=100&timeout=60000"
to a handler bean.  There is a single instance of that bean (if that
matters).  My logging shows that while the thread that does the (InOut)
request handling changes from one request to the next, that there is only
one outstanding request at a time.  The request handling is currently wired
to our test harness which is intentionally delaying responses for 20
seconds... in which case, I would expect to see multiple threads
outstanding.

2012-06-18 13:44:58,070 DEBUG [ProcessorBean] (Camel
(context_request_handler) thread #56 - seda://request_handler_tmb)
Processing request for exchange: ID-seteramac-56604-1340045015657-5-68
2012-06-18 13:44:58,127 DEBUG [ProcessorBean] (Camel
(context_request_handler) thread #56 - seda://request_handler_tmb)
Successfully processed request for exchange:
ID-seteramac-56604-1340045015657-5-68
2012-06-18 13:45:01,295 DEBUG [ProcessorBean] (Camel
(context_request_handler) thread #53 - seda://request_handler_tmb)
Processing request for exchange: ID-seteramac-56604-1340045015657-5-74
2012-06-18 13:45:01,340 DEBUG [ProcessorBean] (Camel
(context_request_handler) thread #53 - seda://request_handler_tmb)
Successfully processed request for exchange:
ID-seteramac-56604-1340045015657-5-74

Can anyone point me in the right direction on this?  I'm assuming this is
something that I'm doing wrong since I can see the executor service code in
the SEDA source code, but it is definitely not behaving as I would expect it
to behave.

Thanks,
Craig





--
View this message in context: 
http://camel.465427.n5.nabble.com/Asynchronous-behavior-of-SEDA-queue-tp5714635.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to