[
https://issues.apache.org/jira/browse/AMQ-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221521#comment-13221521
]
Krishnadasan T S commented on AMQ-3736:
---------------------------------------
Hi,
thanks for a quick reply
We are using fixed number of queues. Is it applicable to topics also. In the
case of topics there is such a scenario like we are creating a topic for each
login by appending login id and a newly created session key. so this will be
different for each login for a same client. This is not queue but topic. Is
this can create the above issue. One thing is that previous topics created for
a client will not be used again, so will it be automatically deleted from the
binary tree index or I need to explicitly delete it. How to delete topic, i
could not see api for delete in jms spec.
Although now this system is not that large, we really want to scale number of
clients. We have a working system, which has nearly 30000 clients base perday,
which uses proprietory technologies like Tibco Rendezvous Messaging
system,Oracle DB etc. Our goal of this application, which uses open source
technologies (activemq, mysql, jboss etc) is to replace that big system with in
a 1 year of target. So your support in solving such issues will be very helpful
to me.
> 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: Blocker
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
