activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Netlancer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5410) Out of order messages received in MQTT network of brokers
Date Fri, 31 Oct 2014 14:46:33 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Netlancer updated AMQ-5410:
---------------------------
    Description: 
broker network setup with mqtt enabled.

scenario:

Client (C1) connects to MQ1
C1 publishes message M1 to topic T1
C1 receives the message M1 by doing receive using mqtt client. 
C1 publishes message M2,M3 to topic T1 and disconnects.

C1 connects back to MQ2
C1 does a receive. Now M3 is received first instead of M2.

  was:
broker network setup with mqtt enabled.

scenario:

Client (C1) connects to MQ1
Client (C2) sends a message (M1) to C1
Mq1 receives the message M1. 
Mq1 initiates publishing of M1 to C1.
In between the publish process (PUB/PUB REC/PUB REL/PUB COM) , C1 disconnects
C1 connects back to MQ2
C2 sends a message (M2) . M2 reaches MQ2 and MQ2 immediately starts the publish process 
MQ1 starts the process of publishing  M1, which now gets routed to MQ2 and then get published
to C1
C1 receives M2 and then M1.


> Out of order messages received in MQTT network of brokers
> ---------------------------------------------------------
>
>                 Key: AMQ-5410
>                 URL: https://issues.apache.org/jira/browse/AMQ-5410
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 5.11.0
>            Reporter: Netlancer
>
> broker network setup with mqtt enabled.
> scenario:
> Client (C1) connects to MQ1
> C1 publishes message M1 to topic T1
> C1 receives the message M1 by doing receive using mqtt client. 
> C1 publishes message M2,M3 to topic T1 and disconnects.
> C1 connects back to MQ2
> C1 does a receive. Now M3 is received first instead of M2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message