Yes, send the camel route and broker configs, etc. Your description seems to be mixing camel "consumer" with jms "consumer".. if you send a test case, i can explain to you what's happening.
On Fri, May 10, 2013 at 9:17 AM, deepak_a <angesh...@gmail.com> wrote: > Not sure why consumers are blocked. Are they acking? > > ------------------- > > No, they are not acking at all, they seem to be blocked. > I ran 2 sets of tests. > For both tests following is the route set up > > <from uri="file:/opt/share/EventFileInput?move=.event-done"/> > <setHeader headerName="messageType"> > <simple>MICS</simple> > </setHeader> > <to uri="jms:queue:queue.incomingEvents"/> > > Test1 <without setting producerWindowSize>: > > In this test, I notice that producer/consumer stalls. I also see that the > route attempted to deliver the file to JMS Queue and it got stalled (I can > see a lock still held on the file in my disk) > > Test2 <with producerWindowSize> > > In this test I notice that consumer is definitely stalled. But I see that > messages have been removed from the disk, i.e. looks like Producer has > attempted to publish the messages to the Queue (but no evidence of messages > in the Queue) - but the looks like broker has properly acked. > > So I see 2 issues here > > 1. Why was consumer blocked > 2. What happened to the messages (that broker acked) - I have checked the > DLQ - its not there either. > > Christian - would it help if I send my camel broker-config.xml, > applicationContext, routes.xml for you to take a look at? > > regards > D > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Query-around-ActiveMQ-DLQ-tp4666277p4666903.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
