Hi Gary-

Thanks for the quick response, as I read that it's fixed in 5.6.0, however
I'm using 5.6.0... I'm only seeing the directory cleaned up during a
restart.

Jeremy

On Tue, Aug 28, 2012 at 11:03 AM, Gary Tully <gary.tu...@gmail.com> wrote:

> If you are sending non persistent messages see
> https://issues.apache.org/jira/browse/AMQ-3780
>
> On 28 August 2012 15:44, Jeremy Levy <jel...@gmail.com> wrote:
> > When using fileQueueCursor, as I understand it the data is written to the
> > tmp-storage directory.  When does this directory get cleaned up.  For
> > example I tested putting about 3 million messages on a queue and it
> > successfully wrote them to disk (as opposed to memory).  It took up about
> > 8.7GB.  I then deleted the queue from the web console, however the 8.7GB
> > remained.  Is there a job or something that I need to configure for this
> > space to be reclaimed?
> >
> > Thanks.
> >
> > Jeremy
> >
> >
> >  <destinationPolicy>
> >             <policyMap>
> >               <policyEntries>
> >                 <policyEntry topic=">" producerFlowControl="false"
> > memoryLimit="2mb">
> >                   <pendingSubscriberPolicy>
> >                     <vmCursor />
> >                   </pendingSubscriberPolicy>
> >                 </policyEntry>
> >
> >                 <policyEntry queue=">" producerFlowControl="false"
> > memoryLimit="2mb" prioritizedMessages="true">
> >                   <!-- Use VM cursor for better latency
> >                        For more information, see:
> >
> >                        http://activemq.apache.org/message-cursors.html
> >                    -->
> >                   <pendingQueuePolicy>
> >                     <!--vmQueueCursor/-->
> >                     <fileQueueCursor/>
> >                   </pendingQueuePolicy>
> >                 </policyEntry>
> >
> >               </policyEntries>
> >             </policyMap>
> >         </destinationPolicy>
> >
> >
> > --
> > Jeremy Levy
>
>
>
> --
> http://fusesource.com
> http://blog.garytully.com
>



-- 
Jeremy Levy

Reply via email to