activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Teja sandeep (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6265) Version 5.9.0 | KahaDB files not getting cleaned up automatically.
Date Thu, 28 Apr 2016 15:13:13 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262305#comment-15262305
] 

Teja sandeep commented on AMQ-6265:
-----------------------------------

Hi [~tabish121]

Can you kindly provide some pointer to similar kind of tickets and their resolutions so that
we can decide on the stable version to upgrade with,

> Version 5.9.0 | KahaDB files not getting cleaned up automatically.
> ------------------------------------------------------------------
>
>                 Key: AMQ-6265
>                 URL: https://issues.apache.org/jira/browse/AMQ-6265
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-pool, KahaDB
>    Affects Versions: 5.9.0
>            Reporter: Teja sandeep
>
> Hi Team
> We have recently faced a Blocker at our end where KahaDB files did not get cleaned up
automatically and queued up for couple of days.
> Unfortunately we did not notice this and the shared disk size became 100% full. 
> - This was a master/slave architecture where both are using the same shared drive. Hence
ActiveMQ was unresponsive at this situation.
> - We have moved the kahadb location to a temporary storage and got the disk cleaned up
and pointed it back. Now the journal files are getting cleaned up automatically.
>  <persistenceAdapter>
>                         <kahaDB directory="/data02/apphome/Broker" journalMaxFileLength="100mb"
cleanupInterval="5000"/>
>  </persistenceAdapter>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message