camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From csete <cr...@mfoundry.com>
Subject Re: Asynchronous behavior of SEDA queue?
Date Tue, 19 Jun 2012 10:50:48 GMT
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&amp;timeout=60000&amp;size=100"/>
    <setExchangePattern pattern="InOut" id="setExchangePattern2"/>
    <bean id="bean2"/>
</route>

Any thoughts would be appreciated.
Thanks,
Craig


On Tue, Jun 19, 2012 at 4:08 AM, Claus Ibsen-2 [via Camel] <
ml-node+s465427n5714662h44@n5.nabble.com> wrote:

> Hi
>
> The concurrentConsumers option should be configured on the consumer side,
> eg
>
> from("seda:foo?concurrentConsumers=20")
>   ...
>
>
>
>
> On Mon, Jun 18, 2012 at 9:01 PM, csete <[hidden email]<http://user/SendEmail.jtp?type=node&node=5714662&i=0>>
> wrote:
>
> > 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.
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: [hidden email]<http://user/SendEmail.jtp?type=node&node=5714662&i=1>
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Asynchronous-behavior-of-SEDA-queue-tp5714635p5714662.html
>  To unsubscribe from Asynchronous behavior of SEDA queue?, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5714635&code=Y3JhaWdAbWZvdW5kcnkuY29tfDU3MTQ2MzV8MTg4NDU5NTQ1Mw==>
> .
> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
Craig Setera
Director, Product Engineering
mFoundry
p 415.324.5801
craig@mfoundry.com


--
View this message in context: http://camel.465427.n5.nabble.com/Asynchronous-behavior-of-SEDA-queue-tp5714635p5714663.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message