[
https://issues.apache.org/jira/browse/AMQ-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285607#comment-15285607
]
Patrik Dudits commented on AMQ-6209:
------------------------------------
Ok, so from the input, RMI registry port was already taken. I switched off
creation of JMX connector.
And for the actual cause of failure on JDK7, items in {{broker}} map were
returned in different order than on JDK 8, leading to incorrect failover URL to
be used in the test.
I updated the PR, please let me know if it works for you, I'll squash it right
after that.
> Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin
> in network of browsers
> ---------------------------------------------------------------------------------------------------
>
> Key: AMQ-6209
> URL: https://issues.apache.org/jira/browse/AMQ-6209
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.2
> Reporter: Patrik Dudits
> Attachments: testOuput.tx
>
>
> When using SubQueueSelectorCachePlugin to preserve consumers' selectors in
> network of brokers, the queues start matching all messages after consumers
> failover between brokers.
> The underlying reason is, that {{SubQueueSelectorCacheBroker}} would cache
> selector {{TRUE}} for connected demand subscription, and therefore will
> permanently match all messages even if actual consumer reconnects.
> Additionally, browsing the queue will also cause {{TRUE}} selector to be
> persisted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
