activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3736) Kaha DB file is growing
Date Fri, 02 Mar 2012 14:09:58 GMT


Gary Tully commented on AMQ-3736:

there is no explicit cleanup of, it holds the binary tree index, the expectation is
that it will reach a maximum when the maximum depth of a queue is reached or the max number
of destinations are created. 
The only solution may be a periodic rebuild of the index through a stop,delete, restart
Does your use case require unlimited numbers of destinations or durable consumers or just
really large queue depths?
> Kaha DB file is growing
> -------------------------------
>                 Key: AMQ-3736
>                 URL:
>             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: Blocker
>         Attachments: activemq.xml
> In our production and development environment 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  In that case had a size of 5 GB. When we cleared kaha db related files,db.redo and db-735.log
files, that issue solved.By further monitoring  We noticed that 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 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message