there is a periodic checkpoint of broker state that writes to the journal. You can configure a longer checkpointInterval to verify that this is what is happening. see: http://activemq.apache.org/kahadb.html
The checkpoint state contains a producer audit it that is written even if it is not modified which should not be the case. I have opened https://issues.apache.org/jira/browse/AMQ-3833 to track this. The journal files get reclaimed so the impact is low, but I agree, it does indeed look a little odd and is a waste of cycles. On 9 May 2012 00:03, mikmela <mikm...@yahoo.com> wrote: > I'm observing the behavior that looks strange to me - for some reason, > broker keep deleting existing journal log files and creates a new ones with > incremented number even though there is no active producers running. > I'm doing acceptance testing on 5.5.1 > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/journal-log-file-gets-incremented-while-there-is-no-activity-tp4618976.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com
