The testcase is
There are 2 machines Machine A, B. Each of them running single brokers each
(BrokerA, BrokerB). The dispatch policy is setup on both brokers as follows
<dispatchPolicy>
<strictOrderDispatchPolicy />
</dispatchPolicy>
A Topic publisher is attached to BrokerA (PubA) is publishing 1000 messages
to 'MyTopic'. And the Durable topic subscriber (SubB) attached to BrokerB
reads the messages from BrokerB. Now to test the message order while PubA is
sending messages stop SubB (say after receiving 230 msgs). So that there are
messages left in the Topic for the durable subscriber SubB (1000-230). Now
when all the messages are published there are 1000-230 messages on the
MyTopic channel. When SubB connects to BrokerB again the messages received
on SubB is not in the order as messages send by PubA.
Kind regards
Matt
James.Strachan wrote:
>
> Could you post a test case that reproduces the issue?
>
> On 3/2/07, Mathulan <[EMAIL PROTECTED]> wrote:
>>
>> I tried in both 4.1 & 4.2-Snapshot
>>
>>
>>
>> James.Strachan wrote:
>> >
>> > Which version were you using?
>> >
>> > On 3/2/07, Mathulan <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Hi All,
>> >>
>> >> I am trying to get the ordered message delivery for durable Topic
>> >> subscriber. I have setup despatch policy as below
>> >> <policyEntry topic=">">
>> >> <dispatchPolicy>
>> >> <strictOrderDispatchPolicy />
>> >> </dispatchPolicy>
>> >> </policyEntry>
>> >> Also the publisher does Message grouping as well. But when the durable
>> >> subscriber goes offline and comes back the messages which are
>> published
>> >> when
>> >> the subscriber was offline are not delivered in the order as they are
>> >> published. Can some one help me to solve this problem. The bussiness
>> >> requirement is to have messages delivered in order as they are
>> published.
>> >> Usecase
>> >> 1) Run durable topic subscriber
>> >> 2) Run the topic publisher
>> >> 3) Stop the topic publisher in the middle
>> >> 4) Restart the topic subscriber
>> >>
>> >> At step 4 the message are not delivered in order.
>> >>
>> >> Please help.
>> >>
>> >> Thank you,
>> >> Kind Regards
>> >> Matt
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Durable-Topic-subscriber-tf3333938s2354.html#a9270599
>> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> >
>> > James
>> > -------
>> > http://radio.weblogs.com/0112098/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Durable-Topic-subscriber-tf3333938s2354.html#a9271048
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context:
http://www.nabble.com/Durable-Topic-subscriber-tf3333938s2354.html#a9271298
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
