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 Sat, 26 Apr 2008 15:53:43 GMT

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

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

Thank you Howard.

I'm afraid the temporary fix you propose wouldn't be of much use in my case. I am currently
working at comparing how well our in-house distributed pub/sub solution routes packets  with
respect to ActiveMQ on a generic network of brokers: if I implement the temporary fix ActiveMQ
performance wouldn't probably be as good as it should invalidating my test. I guess I'll have
to find another MOM for the experiments while ActiveMQ gets fixed. Did any of you ever use
any other JMS implementation supporting generic (cyclic) networks of brokers? 

Using pub/sub on networks of brokers must not be so common after all, I would have expected
this bug to receive much more comments.

Thank you again.

> 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.1.0
>
>
> 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