Are messages being delivered to your MDB, just not consumed? That would indicate that you're failing to ack the messages, perhaps because you're using INDIVIDUAL_ACK mode and not explicitly acking your messages.
Or are they never being delivered to your MDB at all? The fact that you see them in the pending queue means they've been dispatched to the ActiveMQ client code, so that would indicate that you're successfully connecting to the broker, at least. You might want to post your MDB code, in case someone sees a problem. Tim On Wed, Aug 17, 2016 at 7:57 AM, Poonam Bhatia < poonam.c.bha...@fisglobal.com> wrote: > Hi, > > I am working on one of the projects where I am facing an issue with > messages > getting stuck in pending queue and not getting dequeued with Async > consumer. > > My JMS producer is running on one Websphere instance where as my consumer > is > running on another Websphere instance. I am publishing the messages when my > subscriber is down. The messages go and sit in the pending queue. On > starting my consumers, the messages dont get dequeued. I am using an Async > Message Consumer in ActiveMQ. My Producer works just fine and send message > to the Queue. Now, my async message consumer is just waiting for the > onMessage() to be called on, which never happens. So, the problem is: > > Messages are not consumed by the Async Consumer. > Messages get piled up in the pending messages for the Queue. > > Please help. > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Aysnc-ActiveMQ-MDB-unable-to-consume-messages-tp4715582.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
