You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by smo <SM...@micropole-univers.com> on 2007/06/27 11:56:06 UTC
KAHA messages not consumed
Hi!
I have a persistent file "data-queue-data-1" that seems to contain messages
(serialized JavaBean). May I assume these messages haven't been consumed
yet. In that case, how to force ActiveMQ to warn clients that messages are
waiting for being consumed?
In the case they have already been consumed, why this file isn't empty? And
so, how to empty this file?
--
View this message in context: http://www.nabble.com/KAHA-messages-not-consumed-tf3987317s2354.html#a11321516
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: KAHA messages not consumed
Posted by smo <SM...@micropole-univers.com>.
OK, thanx for your responses!
rajdavies wrote:
>
>
> On Jun 28, 2007, at 8:47 AM, smo wrote:
>
>>
>> OK, so the messages may have been delivered and then marked as
>> delivered in
>> this file.
>> Since they are still in the persistence file, is there any way to
>> "remove"
>> this mark so that ActiveMQ deliver them a second time?
>>
> Not currently - we are considering building in replay features in
> post 5.0 though
>>
>>
>> Tom Samplonius-2 wrote:
>>>
>>>
>>> ----- "smo" <SM...@micropole-univers.com> wrote:
>>>> Hi!
>>>> I have a persistent file "data-queue-data-1" that seems to contain
>>>> messages
>>>> (serialized JavaBean). May I assume these messages haven't been
>>>> consumed
>>>> yet. In that case, how to force ActiveMQ to warn clients that
>>>> messages
>>>> are
>>>> waiting for being consumed?
>>>> In the case they have already been consumed, why this file isn't
>>>> empty? And
>>>> so, how to empty this file?
>>>
>>>
>>> Kaha uses a log, so you should expect new messages are appended
>>> to the
>>> the log. So while old messages may be visible, they are probably
>>> also
>>> marked as delivered.
>>>
>>> Your file layout seems strange. Normally Kaha adds messages to
>>> "data-1", and then creates "data-2", etc. "data-1" will be deleted
>>> sometime after it no longer contains any unconsumed messages.
>>>
>>> Tom
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/KAHA-messages-
>> not-consumed-tf3987317s2354.html#a11338542
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/KAHA-messages-not-consumed-tf3987317s2354.html#a11342954
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: KAHA messages not consumed
Posted by Rob Davies <ra...@gmail.com>.
On Jun 28, 2007, at 8:47 AM, smo wrote:
>
> OK, so the messages may have been delivered and then marked as
> delivered in
> this file.
> Since they are still in the persistence file, is there any way to
> "remove"
> this mark so that ActiveMQ deliver them a second time?
>
Not currently - we are considering building in replay features in
post 5.0 though
>
>
> Tom Samplonius-2 wrote:
>>
>>
>> ----- "smo" <SM...@micropole-univers.com> wrote:
>>> Hi!
>>> I have a persistent file "data-queue-data-1" that seems to contain
>>> messages
>>> (serialized JavaBean). May I assume these messages haven't been
>>> consumed
>>> yet. In that case, how to force ActiveMQ to warn clients that
>>> messages
>>> are
>>> waiting for being consumed?
>>> In the case they have already been consumed, why this file isn't
>>> empty? And
>>> so, how to empty this file?
>>
>>
>> Kaha uses a log, so you should expect new messages are appended
>> to the
>> the log. So while old messages may be visible, they are probably
>> also
>> marked as delivered.
>>
>> Your file layout seems strange. Normally Kaha adds messages to
>> "data-1", and then creates "data-2", etc. "data-1" will be deleted
>> sometime after it no longer contains any unconsumed messages.
>>
>> Tom
>>
>>
>
> --
> View this message in context: http://www.nabble.com/KAHA-messages-
> not-consumed-tf3987317s2354.html#a11338542
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: KAHA messages not consumed
Posted by smo <SM...@micropole-univers.com>.
OK, so the messages may have been delivered and then marked as delivered in
this file.
Since they are still in the persistence file, is there any way to "remove"
this mark so that ActiveMQ deliver them a second time?
Tom Samplonius-2 wrote:
>
>
> ----- "smo" <SM...@micropole-univers.com> wrote:
>> Hi!
>> I have a persistent file "data-queue-data-1" that seems to contain
>> messages
>> (serialized JavaBean). May I assume these messages haven't been
>> consumed
>> yet. In that case, how to force ActiveMQ to warn clients that messages
>> are
>> waiting for being consumed?
>> In the case they have already been consumed, why this file isn't
>> empty? And
>> so, how to empty this file?
>
>
> Kaha uses a log, so you should expect new messages are appended to the
> the log. So while old messages may be visible, they are probably also
> marked as delivered.
>
> Your file layout seems strange. Normally Kaha adds messages to
> "data-1", and then creates "data-2", etc. "data-1" will be deleted
> sometime after it no longer contains any unconsumed messages.
>
> Tom
>
>
--
View this message in context: http://www.nabble.com/KAHA-messages-not-consumed-tf3987317s2354.html#a11338542
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: KAHA messages not consumed
Posted by Tom Samplonius <to...@samplonius.org>.
----- "smo" <SM...@micropole-univers.com> wrote:
> Hi!
> I have a persistent file "data-queue-data-1" that seems to contain
> messages
> (serialized JavaBean). May I assume these messages haven't been
> consumed
> yet. In that case, how to force ActiveMQ to warn clients that messages
> are
> waiting for being consumed?
> In the case they have already been consumed, why this file isn't
> empty? And
> so, how to empty this file?
Kaha uses a log, so you should expect new messages are appended to the the log. So while old messages may be visible, they are probably also marked as delivered.
Your file layout seems strange. Normally Kaha adds messages to "data-1", and then creates "data-2", etc. "data-1" will be deleted sometime after it no longer contains any unconsumed messages.
Tom