thanks gary for the reply. you are right that camel route is consuming all messages. so i can not see messages in DB. but when i chang my route to some wrong endpoint which does not exist. which mean i am sending my message to a wrong consumer e.g <to uri="activemq:queue:recieverQueue" /> on place of this if i write <to uri="activemq:queue:recieverQueue12345" /> then message will be fail. In this situation i can see message in DB, it means persistance is working well. so when <to uri="activemq:queue:recieverQueue12345" /> it will be available broker will deliver the persist message from db.
until here everything is fine.. but if i restart broker or my application context gets down after unit test. in that case i can not see that fail persist message in db. it clears from there. BTW thanks for the previous suggestion i'll try by chcking the logs also. -- View this message in context: http://activemq.2283324.n4.nabble.com/message-clears-from-db-if-application-or-activemq-restarts-tp3491807p3501807.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
