On Tue, Jun 19, 2012 at 6:24 AM, Claus Ibsen-2 [via Camel] < ml-node+s465427n5714667...@n5.nabble.com> wrote:
> On Tue, Jun 19, 2012 at 12:50 PM, csete <[hidden > email]<http://user/SendEmail.jtp?type=node&node=5714667&i=0>> > wrote: > > > Claus, > > > > I believe that that is what I'm doing? Here is the route as XML, dumped > > from the route object in JMX: > > > > <route group="com.mfoundry.mb.qos.QOSFIRouteBuilder" > > id="route_request_handler_tmb" xmlns=" > http://camel.apache.org/schema/spring > > "> > > <from > > > uri="seda:request_handler_tmb?concurrentConsumers=10&timeout=60000&size=100"/> > > > <setExchangePattern pattern="InOut" id="setExchangePattern2"/> > > <bean id="bean2"/> > > </route> > > > > Any thoughts would be appreciated. > > Thanks, > > Craig > > Look at the producer side which sends the message to the seda queue. > > It may not be quick enough, or if you do request/reply over SEDA, then > the producer > will at some point await for the exchange to be done, so it can get > the result message. > > It depends a bit how you are doing this (sending to the seda queue). > See the waitForTaskToComplete option > http://camel.apache.org/seda > > Thanks Claus, Maybe I can explain a bit more about what I'm trying to accomplish and what the overall routing looks like to see if you have ideas for me. The overall goal of this routing is to segregate multiple backend server hosts from each other such that a slow back-end host won't hold up other hosts. There is a SEDA queue route to the processing bean for each of these backend hosts. In addition, there is a single SEDA "input" queue that uses a recipient list (based on a header) to select which back-end queue is next in the routing. The goal, if this is set up correctly, would be that the "input" processing handle moving the incoming requests to the back-end queues as quickly as possible to clear the way for incoming requests that may be for other back-end queues that are not slow. However, in this case, it seems like the back-end queueing is acting single-threaded. Any thoughts with this extra information on where things might be going wrong? Thanks, Craig -- Craig Setera Director, Product Engineering mFoundry p 415.324.5801 cr...@mfoundry.com -- View this message in context: http://camel.465427.n5.nabble.com/Asynchronous-behavior-of-SEDA-queue-tp5714635p5714674.html Sent from the Camel - Users mailing list archive at Nabble.com.
