activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giovanni Toffetti (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1509) Duplicate topic messages received with network of brokers and selectors
Date Fri, 23 May 2008 13:23:54 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42974#action_42974
] 

Giovanni Toffetti commented on AMQ-1509:
----------------------------------------

Hi Rob,

I saw you committed the changes to fix issue AMQ-1509. I downloaded the latest svn snapshot
on may the 8th and tested it  on the (for me usual) 4-nodes-in-a-cycle topology. It seems
your patch improves the whole thing as now my test runs end nicely (before the duplication
was so massive clients were not able to finish their workload), alas, my clients keep receiving
duplicate messages.

I will attach the code of my clients for completeness, either there's something wrong with
them or the bug is still there for bigger cyclic topologies. 

> Duplicate topic messages received with network of brokers and selectors
> -----------------------------------------------------------------------
>
>                 Key: AMQ-1509
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1509
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Transport
>    Affects Versions: 4.1.1
>            Reporter: Howard Orner
>            Assignee: Rob Davies
>             Fix For: 5.2.0
>
>         Attachments: ActiveMQActor.java
>
>
> If you create a network of two brokers, A and B, one publisher publishing to A, and n
(where n is > 1) receivers with selectors, each receiver recieves n messages for every
1 message sent.  The key here is to have a selector.   It would appear that the conduitSubscriptions
flag does not work when using selectors.  The conduit does not properly reconcile consumers
if they have selectors.  A suggested soltuion would be that ather than process each selector
independantly, each selector should be or'ed together and if any selector results in true
then a single message should be sent to the other broker.
> In doing research, it would appear that this problem was introduced with bug fix AMQ-810.
 Another user reported it via email back to the assignee of AMQ-810 and a short dialog transpired.
 See http://www.mail-archive.com/activemq-users@geronimo.apache.org/msg05198.html.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message