activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-6209) Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin in network of browsers
Date Thu, 12 May 2016 18:44:12 GMT


Timothy Bish commented on AMQ-6209:

I gave the patch a quick spin and the test fails with the below:

	at com.sun.proxy.$Proxy4.selectorsForDestination(Unknown Source)
	at org.apache.activemq.usecases.TwoBrokerVirtualTopicSelectorFailoverTest.testLeaksAtFailover(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at junit.framework.TestCase.runTest(
	at junit.framework.TestCase.runBare(
	at org.apache.activemq.CombinationTestSupport.runBare(
	at org.apache.activemq.CombinationTestSupport.runBare(
	at junit.framework.TestResult$1.protect(
	at junit.framework.TestResult.runProtected(
	at junit.framework.TestSuite.runTest(
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(
Caused by: org.apache.activemq:type=Broker,brokerName=BrokerA,service=plugin,virtualDestinationSelectoCache=virtualDestinationCache
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(
	... 23 more


So you might need to do some more work on the test to ensure it's sound. 

> Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin in network
of browsers
> ---------------------------------------------------------------------------------------------------
>                 Key: AMQ-6209
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.13.2
>            Reporter: Patrik Dudits
> 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

View raw message