Version: ActiveMQ 5.2 OS: Linux Producer: persisent messages sent to queue Consumer: uses Spring DMLC with Spring JmsTransactionManager Persistence - using default AMQPersistenceAdapter (no config in broker.xml)
Producer/Consumer and ActiveMQ are deployed on the same linux server We have a customer incident where the journal folder grew to over 31GB. We had to restart all our java services because the file system was running out of space (we had other files not related to amq that grew too large as well). Upon restart I noticed these messages in the activemq.log, which indicate a LARGE number of messages being recovered from the journal. If we are using a transaction manager and the DMLC does a commit after receiving every message, why are any messages still being retained in the journal? Is there some configuration options I can use to avoid this problem? I've read some posts whereby the workaround the user found was to not use transactions and use client acknowledge. The DMLC does not do an acknowledge when transactions are in use (session.commit() is called rather than message.acknowledge()). Not sure if this is related to how AMQ determines to keep the message active in the persistent store. This seems a lot like this AMQ issue: https://issues.apache.org/activemq/browse/AMQ-1926 2010-01-29 15:38:39,442 [main ] INFO AMQPersistenceAdapter - Active data files: [] 2010-01-29 15:38:39,444 [main ] WARN AMQPersistenceAdapter - The ReferenceStore is not valid - recovering ... 2010-01-29 15:38:39,454 [main ] INFO KahaStore - Kaha Store successfully deleted data directory /opt/teradata/cam/activemq/apache-activemq-5.2.0/data/TeradataCamActiveMQ/kr-store/data 2010-01-29 15:38:39,455 [main ] INFO AMQPersistenceAdapter - Journal Recovery Started from: DataManager:(data-) 2010-01-29 15:38:39,477 [main ] INFO KahaStore - Kaha Store using data directory /opt/teradata/cam/activemq/apache-activemq-5.2.0/data/TeradataCamActiveMQ/kr-store/data 2010-01-29 15:46:45,946 [main ] INFO BrokerService - Using Persistence Adapter: AMQPersistenceAdapter(/opt/teradata/cam/activemq/apache-activemq-5.2.0/data/TeradataCamActiveMQ) 2010-01-29 15:46:45,978 [main ] INFO AMQPersistenceAdapter - AMQStore starting using directory: /opt/teradata/cam/activemq/apache-activemq-5.2.0/data/TeradataCamActiveMQ 2010-01-29 15:46:46,051 [main ] INFO KahaStore - Kaha Store using data directory /opt/teradata/cam/activemq/apache-activemq-5.2.0/data/TeradataCamActiveMQ/kr-store/state 2010-01-29 15:46:46,107 [main ] INFO AMQPersistenceAdapter - Active data files: [] 2010-01-29 15:46:46,109 [main ] WARN AMQPersistenceAdapter - The ReferenceStore is not valid - recovering ... 2010-01-29 15:46:46,120 [main ] INFO KahaStore - Kaha Store successfully deleted data directory /opt/teradata/cam/activemq/apache-activemq-5.2.0/data/TeradataCamActiveMQ/kr-store/data 2010-01-29 15:46:46,121 [main ] INFO AMQPersistenceAdapter - Journal Recovery Started from: DataManager:(data-) 2010-01-29 15:46:46,139 [main ] INFO KahaStore - Kaha Store using data directory /opt/teradata/cam/activemq/apache-activemq-5.2.0/data/TeradataCamActiveMQ/kr-store/data 2010-01-29 16:47:22,248 [main ] INFO AMQPersistenceAdapter - Recovered 37735485 operations from redo log in 3636.125 seconds. 2010-01-29 16:47:22,254 [main ] INFO AMQPersistenceAdapter - Finished recovering the ReferenceStore 2010-01-2 -- View this message in context: http://old.nabble.com/broker-journal-data-files-grew-to-31GB-tp27519610p27519610.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
