You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org> on 2012/03/20 22:25:39 UTC

[jira] [Closed] (AMQ-3713) tmpDB.data file grows irreversibly

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

Timothy Bish closed AMQ-3713.
-----------------------------

    Resolution: Incomplete

No feedback from the reporter on test case or reproduction of the issue.  
                
> tmpDB.data file grows irreversibly
> ----------------------------------
>
>                 Key: AMQ-3713
>                 URL: https://issues.apache.org/jira/browse/AMQ-3713
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-camel
>    Affects Versions: 5.4.2, 5.5.1
>         Environment: linux, windows
>            Reporter: Sree Panchajanyam D
>
> Steps to replicate
> On a queue, produce non-persistent messages(message size can be 1Kb to 5kb ) with consumer down. There will be an increase in db-*.log files along with this there is an increase in the size of tmpDB.data file. Let the temp store percentage grow up to 90% without triggering the consumer. Once the temp store is 90% start the consumer. The log files are deleted once the messages are consumed but tmpDB.data file does not decrease in size and this causes  the temp store to be 60 - 70% full.  
> Issues with this with slow consumer, which does not call for a producer flow control, temp store % keeps growing and at one particular point of time hits 100% just because of tmpDB.data file and hence no messages can be produced on to AMQ without a restart of it.
> In my case this situation occurs very quickly when one of the consumer goes down as the load on AMQ is high.
> The above is the case with persistent store as well. Please suggest a solution or provide a patch for this problem.

--
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