you can listen to advisory messages and keep running counts or do the same via a broker plugin.
But if you want to ensure that the journal reflects the state, enable archiving with archiveDataLogs=true on the kahadb persistence adapter. You will then need to look at the kahaDB journal api to parse the journal to find acked and unacked messages on the set of active and archived journal data files. Looking at the kahadb persistence adapter recovery source code will give you some simple pointers into that. The index only reflects the current unconsumed or pending message. On 25 April 2011 18:33, kar <jaskaran1...@gmail.com> wrote: > > Hello, > > I am using ActiveMQ 5.4 and the database is set to kahadb. My application is > using the Spring framework. > > I needed a way to get the below information : > 1) All messages that were sent to a particular queue(since the creation of > the queue) > 2) Messages that were consumed from the queue(since the creation of the > queue) > 3) Messages that were removed from the queue(since the creation of the > queue) > > Basically i need the message transactions/history to be permanently stored. > So that i can get the history(via code) of any message or queue and show in > my application UI. > > Thanks > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-5-4-Message-transactions-history-to-be-permanently-stored-tp3473678p3473678.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com http://fusesource.com
