any message selectors? Is it just one consumer that does not get messages? Are they stomp/operwire?
I think the best bet to understand what is going is to capture full trace logging. Also trace=true on the openwire (or relevant) tcp transport url. Possibly a broker side thread dump. Any chance the os is low on file descriptors? On 20 March 2014 15:07, lookers <colm.oloughn...@gmail.com> wrote: > > There is no ttl on the messages. I have not tried browsing with JMS when > they are stuck. I can try that when it fails again > No there is nothing in the DLQ for this queue. > It is happening quiet regularly. At lease twice a day. I have similar > environment set up of different instance and it does not behave like this. > > > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-5-9-0-tp4679266p4679287.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
