Claus,
Please disregard my question. Based on your statements, I dug back even
further in the chain. I found a spot in my code that uses a
ProducerTemplate that was over-synchronized and causing every request to
hold until the response was complete. By fixing the synchronization in my
method, I
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,
&
el] <
ml-node+s465427n5714662...@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 <[h
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
This was user error on my part. What I was failing to account for was
exchanges that were already consumed by a handler thread and were waiting to
be serviced within the thread. Clearly those are no longer queued and
should not show as such. The SedaConsumer knows about the number of
inflight ex
Some additional information. I'm not seeing any difference using the
jconsole tool or using a VM endpoint instead of SEDA.
Any help appreciated.
Craig
--
View this message in context:
http://camel.465427.n5.nabble.com/SEDA-Queue-not-showing-contents-via-JMX-tp5713504p5713513.html
Sent from th
I'm in the process of updating our infrastructure dependencies to Camel 2.9.2
in large part to be able to see what is going on inside of our SEDA queues.
With the addition of the ManagedResource tagging and support, I'm seeing
significantly more information via JMX. However, at least via JBoss
JM
