Also, to state the obvious, depending on the load on your broker this could be a massive amount of logging. Be sure you configure your logging system appropriately (log roll-over in place, a sufficiently large disk to store the volume of logs at the point where they start to roll over, etc.).
Tim On Thu, May 21, 2020, 5:59 AM Tim Bain <tb...@alumni.duke.edu> wrote: > You could write a plugin that would log the content of each message as > it's received; just log it and then call the corresponding > super.messageDelivered() method. Relevant information is at > https://activemq.apache.org/interceptors and > https://activemq.apache.org/developing-plugins. > > Tim > > On Thu, May 21, 2020, 1:09 AM Jean-Baptiste Onofre <j...@nanthrax.net> > wrote: > >> Not directly. You can always use advisory to be notify when a message is >> consumed. >> >> But again, once it has been consumed, the message is gone. >> >> Regards >> JB >> >> > Le 21 mai 2020 à 09:05, skao <simonkao2...@gmail.com> a écrit : >> > >> > Hi François, >> > >> > Thanks a lot for your reply. >> > >> > Like JB mention earlier, if the consumer de-queue the message and then >> it >> > won't show up in kahaDB. >> > Then there is no way for me to see the hahadb file to review the >> en-queue >> > messages. >> > >> > I would like to see all messages even though they have been de-queued by >> > consumers. >> > >> > Is that possible ? >> > >> > Thanks, >> > Samuel >> > >> > >> > >> >>> Hi, >> > >> >>> You should understand better how ActiveMQ and JMS works. >> > >> >>> Once a consumer consumed a message, the message is not in KahaDB >> anymore. >> > >> >>> Regards >> >>> JB >> > >> > >> > >> > -- >> > Sent from: >> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >> >>
