[
https://issues.apache.org/jira/browse/AMQ-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270004#comment-17270004
]
Dee Moore commented on AMQ-3736:
--------------------------------
We hit the same issue on ActiveMQ 5.14.2. It was configured to delete inactive
destinations.
We solved this by reviewing our topics - we were making transient topics such
as /topic/topic.prefix.<uuid>.entry, which sent small amounts of data and then
became inactive. However, one of our subscribers was subscribing to
/topic/topic.prefix.>, and this was enough to keep every topic active, and
resulted in steady growth of db.data, with only one active .log file.
Even though we found a solution, it would be very nice to be able to mark a
channel as "This channel is inactive when messages have not been sent for x
amount of time and should be deleted, whether or not there are active
subscribers". I cannot find a way to do this - having a subscriber, even on a
wild card basis, is enough to keep a topic active.
> Kaha DB Db.data file is growing
> -------------------------------
>
> Key: AMQ-3736
> URL: https://issues.apache.org/jira/browse/AMQ-3736
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.1
> Environment: cent os 5.3, java 6 update 30
> Reporter: Krishnadasan T S
> Priority: Major
> Attachments: activemq.xml
>
>
> In our production and development environment db.data file is growing. Within
> few weeks it reaches GB's in size. When it grows larger broker hangs
> frequently. I have already reported a bug in 5.4.2(AMQ-3710) url
> https://issues.apache.org/jira/browse/AMQ-3710. In that case db.data had a
> size of 5 GB. When we cleared kaha db related files db.data,db.redo and
> db-735.log files, that issue solved.By further monitoring We noticed that
> db.data file is growing by day from MB to GB. And when the size become
> larger, the broker hanging issue is coming back.
> Now we have updated Our activemq broker to 5.5.1. But db.data is
> still growing. Every day we are monitoring it and if it is become big(200 mb)
> we are clearing all kaha related files before our business start.
> Other kaha related files are normal. db-*.log files are cleared by kaha db.
> db.redo file is not growing. Only db-data file is growing.
> I don't think this is a correct behavior. At certain point of time it
> should clear unwanted data write. I am using the same configuration without
> much change.
> I have attached active mq config file with this.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
