I don't know of another place where it would be configured, so I think the
more likely explanation is that there's a bug causing the second
subscription to not be conduited onto the first.
But let's first let's confirm that we actually have two subscriptions on A
(because if we don't, then something else is going on). Can you please
attach a JMX viewer such as JConsole to broker A, and navigate the MBeans
to find your topic, and drill into it within the tree to see how many
subscriptions are associated with it? You should see a single subscription
if conduitSubscriptions is working properly, but I expect that you'll see
two.
Tim
On Jul 26, 2017 8:04 AM, "tpavelka" <tomas.pave...@ca.com> wrote:
> I double checked just to make sure:
>
> There is this code in org.apache.activemq.network.NetworkBridgeFactory
>
> public static DemandForwardingBridge
> createBridge(NetworkBridgeConfiguration configuration,
> Transport
> localTransport, Transport remoteTransport,
> final
> NetworkBridgeListener listener) {
> DemandForwardingBridge result = null;
> if (configuration.isConduitSubscriptions()) {
> // dynamicOnly determines whether durables are auto bridged
> result = new DurableConduitBridge(configuration,
> localTransport,
> remoteTransport);
> } else {
> result = new DemandForwardingBridge(configuration,
> localTransport, remoteTransport);
> }
> if (listener != null) {
> result.setNetworkBridgeListener(listener);
> }
> return result;
> }
>
> I put a breakpoint in and made it display the result of
> configuration.isConduitSubscriptions(), it shows as true for every call
> for
> every end point.
>
> Can you think of any other place that I may have missed that could change
> the conduitSubscribers behavior?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-
> tp4728627p4728931.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
