Good you could figure it out by yourself. Have a nice Camel ride, Christian
On Thu, May 24, 2012 at 10:39 PM, csete <cr...@mfoundry.com> wrote: > 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 exchanges, which is correct and showing me what I expected. > > Sorry for the false alarm and thanks for the Camel project... great stuff. > > Craig > > -- > View this message in context: > http://camel.465427.n5.nabble.com/SEDA-Queue-not-showing-contents-via-JMX-tp5713504p5713522.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
