Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of crackduoro@gmail.com
 designates 209.85.212.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKS7T5P4A2ZhzQ0Ak0Afi_vnWzL8DqdNYeYUcmwp1E6u8ZsZCA@mail.gmail.com>
References: 
 <CA+EL7oeBrTC8jN7hmhr=Kz+gS_pOa_y1r8wAUjOtPYhu+qNTmQ@mail.gmail.com>
	<CAF7Ov03m8YcuAZrGi5Qqumd2LZfhUH3VX5P9hegSTsX-scY3XQ@mail.gmail.com>
	<BA05F384-8AC2-4D3B-99A9-47DD0D0B7DB2@artnaseef.com>
	<CA+EL7of5qeFxP74qBhbpMVX4G_6Hzqe9pV4fULeVdf0fhZm4bQ@mail.gmail.com>
	<1391532479235-4677426.post@n4.nabble.com>
	<CA+EL7ocZ-xQS0qMN-gW=AgnnNg07d8tjz9wGZeQKA7OUmNwU4g@mail.gmail.com>
	<63eb8939ca74b04b3a657afeb440e839.squirrel@email.powweb.com>
	<CA+EL7oc8Stero7B-PifQo8WwkZKcePSyS6dy203v5yk=MAzwqw@mail.gmail.com>
	<CAKS7T5P4A2ZhzQ0Ak0Afi_vnWzL8DqdNYeYUcmwp1E6u8ZsZCA@mail.gmail.com>
Date: Thu, 6 Feb 2014 18:48:47 -0600
Message-ID: 
 <CA+EL7of7LEPcxvSa9uP+yEw=4c_weBqTD1nZAubvffjjV47TjA@mail.gmail.com>
Subject: Re: Purge Kahadb
From: Rodrigo Ramos <crackduoro@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=047d7bfd05fc4fdea104f1c65a04

--047d7bfd05fc4fdea104f1c65a04
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

If my main is not wrong, there are two ways for that. We can set up as
policy into the broker or we can set up on the message. Is this correct?


2014-02-06 Christian Posta <christian.posta@gmail.com>:

> Maybe your producers should send with at TTL so that they auto expire
> if they are not consumed in a reasonable amount of time.
>
> On Tue, Feb 4, 2014 at 7:38 PM, Rodrigo Ramos <crackduoro@gmail.com>
> wrote:
> > Its complicated, because the core of service is asyncronous tier. So, i
> > have to clean the queues before the incoming messages start.
> > El feb 4, 2014 7:53 PM, "artnaseef" <art@artnaseef.com> escribi=F3:
> >
> >> It sounds like there are producers constantly adding messages.  If so,
> >> stopping those producers is the only way to prevent the messages.
> >>
> >> >
> >> >
> >> > Yes, but those messages are different. Every days the incoming
> messages
> >> > has
> >> > different contents. I purged all messages into the queue, before the
> new
> >> > messages arrives, but it does not work. I must not delete data
> directory.
> >> > Is there another way?
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > 2014-02-04 artnaseef <art@artnaseef.com>:
> >> >
> >> >> Rodrigo Ramos wrote
> >> >> > There is a problem with web console. It says that the queue is
> without
> >> >> > messages, but, when I restart the broker, consumers begins to
> consume
> >> >> > messages again.
> >> >>
> >> >> Could there be more messages being added to that Queue on the broke=
r
> >> >> after
> >> >> the purge/delete?
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://activemq.2283324.n4.nabble.com/Purge-Kahadb-tp4677339p4677426.html
> >> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >> >>
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > If you reply to this email, your message will be added to the
> discussion
> >> > below:
> >> >
> >>
> http://activemq.2283324.n4.nabble.com/Purge-Kahadb-tp4677339p4677430.html
> >> > To start a new topic under ActiveMQ - User, email
> >> > ml-node+s2283324n2341805h3@n4.nabble.com
> >> > To unsubscribe from ActiveMQ - User, visit
> >> >
> >>
> http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=3Dun=
subscribe_by_code&node=3D2341805&code=3DYXJ0QGFydG5hc2VlZi5jb218MjM0MTgwNXw=
tMjA1NDcyNjY5MQ=3D=3D
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://activemq.2283324.n4.nabble.com/Purge-Kahadb-tp4677339p4677441.html
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
> --
> Christian Posta
> http://www.christianposta.com/blog
> twitter: @christianposta
>

--047d7bfd05fc4fdea104f1c65a04--