I did find something, but need some advice: We are using ActiveMQ 5.11.1 in our environments. The behaviour we noticed was that ActiveMQ wrote the messages to a new kahadb file (journal log) after every 32 mb (default configuration). This lead to the message and its corresponding ack ending up in different files. It resulted in a chain of such journal logs which couldn't be cleaned up by ActiveMQ. It eventually filled up the disk causing ActiveMQ to shutdown.
Is it a good idea to increase the log size to avoid having the message and its ACK in different files? Any suggestions here? Regards, Barry -----Original Message----- From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain Sent: Tuesday, September 29, 2015 1:14 AM To: ActiveMQ Users Subject: Re: Nothing on queues, Journal files not getting cleaned up I trust you've confirmed that there are no messages pending on topics as well as queues? JMX is the easiest way I know to confirm that if you haven't already done so. Are some but not all journal files being deleted, or none at all? On Sep 28, 2015 8:44 AM, <barry.barn...@wellsfargo.com> wrote: > Hello, > > How is it that our journal files continue to grow, yet no messages are on > the queues? > > ActiveMQ 5.11.1, Using KahaDB (not levelDB). > > How can you tell if a kahaDB scheduler is waiting, and in need of clearing? > > Nothing on the Advisory queues (no network of brokers), nothing on the > DLQ. Where else can I look? Our txlogs are very large as well. > Application Teams advise their transaction processing IS committing on gets > and puts, etc.. > > Regards, > > Barry > > >
