I see only that the application try following: 011-04-07 15:14:14,780 | DEBUG | Executing SQL: DELETE FROM ACTIVEMQ_MSGS WHERE ( EXPIRATION<>0 AND EXPIRATION<?) OR (ID <= ( SELECT min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM ACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER ) ) | org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter | ActiveMQ Cleanup Timer 2011-04-07 15:14:14,780 | DEBUG | Deleted 0 old message(s). | org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter | ActiveMQ Cleanup Timer
But the query return as result null.After we restart activemq then not all but some of the messages deliver to the consumer. We had the following situation: 1. 57 Messages stuck in queue --> web console shows that but if we want to see in queue then there was no messages but in database we had all 57 messages. 2.We restart activemq and 54 of 57 deliver to the consumer and rest 3 messages stuck again. 3.But next restart the rest 3 messages delivered to consumer. -- View this message in context: http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-tp3244342p3433612.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
