[ 
https://issues.apache.org/jira/browse/AMQ-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krishnadasan T S updated AMQ-3736:
----------------------------------

    Description: 
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.


 

  was:
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. 



 

    
> 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

        

Reply via email to