You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/05/05 13:22:33 UTC
[jira] Created: (AMQ-2720) Duplicate messages delivery after
restart for topics with network of brokers + kahaDB
Duplicate messages delivery after restart for topics with network of brokers + kahaDB
-------------------------------------------------------------------------------------
Key: AMQ-2720
URL: https://issues.apache.org/activemq/browse/AMQ-2720
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.3.1
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.4.0
After restart, a network connector with default dynamicOnly=false will auto bridge any topic with durable subscribers. KahaDB is reporting all topics as durable through the list of destinations that it returns, the result being a duplicated durable (and phantom) consumer on the bridge.
Disabling auto durable topic bridging with ddynamicOnly=true will work around this issue.
problem:
getDestinations in kahaDB persistence adapter should only return a list of destinations that include topics with durable subs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2720) Duplicate messages delivery after
restart for topics with network of brokers + kahaDB
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-2720.
-----------------------------
Resolution: Fixed
resolved in r941281
> Duplicate messages delivery after restart for topics with network of brokers + kahaDB
> -------------------------------------------------------------------------------------
>
> Key: AMQ-2720
> URL: https://issues.apache.org/activemq/browse/AMQ-2720
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.1
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.4.0
>
>
> After restart, a network connector with default dynamicOnly=false will auto bridge any topic with durable subscribers. KahaDB is reporting all topics as durable through the list of destinations that it returns, the result being a duplicated durable (and phantom) consumer on the bridge.
> Disabling auto durable topic bridging with ddynamicOnly=true will work around this issue.
> problem:
> getDestinations in kahaDB persistence adapter should only return a list of destinations that include topics with durable subs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.