[
https://issues.apache.org/jira/browse/AMQ-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073468#comment-13073468
]
James Green commented on AMQ-3424:
----------------------------------
This was a known issue that was fixed in the 5.5 release (and verified by many
reporting it). The only other reason I have found for log files not to be
removed is stale durable subscribers.
To isolate the problem you can switch on tracing of the vacuuming process. This
should verify whether kahadb "knows" about the logs you can see and if so,
whether it is making a conscious decision not to delete them.
Read
http://activemq.2283324.n4.nabble.com/KahaDB-storage-size-grows-despite-almost-no-pending-messages-td3573894.html
for more information.
> AMQ data dir not cleaning up even after messages getting consumed.
> ------------------------------------------------------------------
>
> Key: AMQ-3424
> URL: https://issues.apache.org/jira/browse/AMQ-3424
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Reporter: Hariharan
>
> Hi,
> We are using ActiveMQ 5.3 (in UNIX) and use both queues and topics (durable
> and non-durable).
> The messages are published by the publishers in persistent delivery and auto
> acknowledge mode.
> I can see that the consumers are actively able to consume the messages.
> However, even after the messages getting consumed successfully, the data dir
> size is not coming down.
> I tried :
> 1. Using both amqPersistenceAdapter and kahaDB.
> 2. Upgrading the AMQ to 5.5
> But none of them is bringing down its size.
> snapshot:
> {code:xml}
> *After starting the broker.*
> du -h activemq_data_kahadb ; ls -l /activemq_data_kahadb
> 48K /activemq_data_kahadb
> total 44
> -rw-rw-r-- 1 manih manih 9961472 Jul 29 05:06 db-1.log
> -rw-rw-r-- 1 manih manih 12288 Jul 29 05:06 db.data
> -rw-rw-r-- 1 manih manih 12304 Jul 29 05:06 db.redo
> -rw-rw-r-- 1 manih manih 0 Jul 29 05:04 lock
> *After messages getting delivered.*
> du -h /activemq_data_kahadb ; ls -l /activemq_data_kahadb
> 1.7M /activemq_data_kahadb
> total 1652
> -rw-rw-r-- 1 manih manih 9961472 Jul 29 05:24 db-1.log
> -rw-rw-r-- 1 manih manih 364544 Jul 29 05:24 db.data
> -rw-rw-r-- 1 manih manih 332416 Jul 29 05:24 db.redo
> -rw-rw-r-- 1 manih manih 0 Jul 29 05:04 lock
> {code}
> Here are my config details:
> {code:xml}
> <amq:persistenceAdapter>
> <amq:kahaDB directory="activemq_data_kahadb" journalMaxFileLength="10mb"/>
> </amq:persistenceAdapter>
> <amq:systemUsage>
> <amq:systemUsage>
> <amq:memoryUsage>
> <amq:memoryUsage limit="20 mb"/>
> </amq:memoryUsage>
> <amq:storeUsage>
> <amq:storeUsage limit="1 gb"/>
> </amq:storeUsage>
> <amq:tempUsage>
> <amq:tempUsage limit="100 mb"/>
> </amq:tempUsage>
> </amq:systemUsage>
> </amq:systemUsage>
> {code}
> I do understand that the messages are persisted until consumed by the
> consumers, but after that shouldn't the file size be coming down?
> Please let me know if there are any config changes that I need to do to get
> this working fine.
> Thanks in advance
> Hari
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
