gt;>> >>> E.g.
>>> >>> Publisher puts message 1 to 10 on topic. Consumer opens a session,
>>> gets
>>> >>> message 1, makes a client acknowledment, gets message 2, makes a
>>> client
>>> >>> acknowledment, and so on.
nowledment, and so on. On message 3 a runtime exception occurs and
>> no
>> >>> client acknowledment is done, but the session and the connection are
>> >>> closed.
>> >>> The next time the consumer opens a session message 4 gets delivered
>>
e the consumer opens a session message 4 gets delivered
> >>> before
> >>> message 3.
> >>>
> >>> What do we have to do to get message 3 (and not 4) as the first message?
> >>> Do
> >>> we have to use a special redelivery pol
t message?
>>> Do
>>> we have to use a special redelivery policy?
>>
>> It should just work; though FWIW I'd recommend you switch from using
>> acknowledge to using JMS transactions. They are typically faster as
>> well as allowing you to do a rollback
i-use-transactions.html
>
>
>> PS: We're using ActiveMQ 4.1.0
>
> I'd also recommend you upgrade to 4.1.1
> --
> James
> ---
> http://macstrac.blogspot.com/
>
>
--
View this message in context:
http://www.nabble.com/Strict-order-of-messages-with-redelivery-tf4391491s2354.html#a12538047
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 9/6/07, Juergen Mayrbaeurl <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> Our application has to make sure that all consumers with durable topic
> subscriptions get messages in strict order even when a message has to be
> delivered.
> E.g.
> Publisher puts message 1 to 10 on topic. Consumer opens a sess
) as the first message? Do
we have to use a special redelivery policy?
Kind regards
Juergen
PS: We're using ActiveMQ 4.1.0
--
View this message in context:
http://www.nabble.com/Strict-order-of-messages-with-redelivery-tf4391491s2354.html#a12520552
Sent from the ActiveMQ - User mailing
