-
1. Re: STOMP messages stuck delivering indefinitely
gaohoward Jun 13, 2013 4:06 AM (in response to marrrck)If the client don't send back 'ACK' the message won't be considered as 'delivered', so the delivering count won't decrease for each of such un-acked message. Stomp clients don't use any (jms) connection factories.
-
2. Re: STOMP messages stuck delivering indefinitely
marrrck Jun 13, 2013 12:01 PM (in response to gaohoward)Thanks for the Reply!
So what happens to the message that is never ACK'd? Does it ever stop waiting for an ACK message? Also, is the consumer tied up waiting for the ACK? I am seeing this message a lot in my logs when my delivering-count keeps steadily increasing
16:00:18,311 DEBUG [org.hornetq.core.server.impl.QueueImpl] (Thread-4 (HornetQ-server-HornetQServerImpl::serverUUID=723e04c3-ccb5-11e2-ba73-c77d31915799-1529650781)) QueueImpl[name=jms.queue.mm.to, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=723e04c3-ccb5-11e2-ba73-c77d31915799]]@7b7b3da0 doing deliver. messageReferences=15
16:00:18,312 DEBUG [org.hornetq.core.server.impl.QueueImpl] (Thread-4 (HornetQ-server-HornetQServerImpl::serverUUID=723e04c3-ccb5-11e2-ba73-c77d31915799-1529650781)) QueueImpl[name=jms.queue.mm.to, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=723e04c3-ccb5-11e2-ba73-c77d31915799]]@7b7b3da0::All the consumers were busy, giving up now