James, this is related to a bug:
https://issues.apache.org/jira/browse/AMQ-4210
Will have a fix in shortly.
On Tue, Oct 30, 2012 at 8:52 AM, James Green wrote:
> Gary,
>
> Spoke config:
>
>name="plenty-hub-01"
>duplex="true"
>c
Gary,
Spoke config:
On the hub, I captured this: http://pastebin.co
that does seem odd, enable trace=true on the tcp transport to see the
advisory consumer subscription command from the bridge, and the
corresponding advisory composite destination. This will all be part of
bridge setup and should be informative.
you need to enable debug logging for
org.apache.activ
Gary,
On our test cluster one of our spokes has been configured thus:
.117 is our test hub.
Against the spoke we subscribed to the Outbound.
there are two different filters involved.
The bridge gets notification of demand on a destination, ie:
consumers, using an advisory consumer.
To reduce the advisory traffic, the set of matching advisory
destinations subscribed to can be filtered. Using the
destinationFilter property or generated f
http://activemq.apache.org/networks-of-brokers.html states for
dynamicallyIncludedDestinations that "destinations that match this list *
will* be forwarded across the network *n.b.* an empty list means all
destinations not in the exluded list will be forwarded".
This reads to me that, given an emp
in your case you need to provide a destinationFilter b/c it is only
auto built from not excluded
destinations.
Do you know up front what you want to bridge or just what you want to ignore?
A the moment, afaik, we don't have a way of providing a negative
filter which seems to be what you want.
We are running 5.7.0 on hub and spokes, forgot to mention.
On 30 October 2012 12:08, James Green wrote:
> Gary,
>
> I think you're saying that subscription advisories for excluded
> destinations should be suppressed.
>
> On the hub we're seeing advisories for queues on that spoke. Is there
> the
Gary,
I think you're saying that subscription advisories for excluded
destinations should be suppressed.
On the hub we're seeing advisories for queues on that spoke. Is there
therefore a bug?
James
On 30 October 2012 11:58, Gary Tully wrote:
> the destinationFilter does the job of narrowing t
the destinationFilter does the job of narrowing the list of
interesting consumers by limiting the advisory consumer to a subset of
destinations.
This is auto generated if it is not configured from 5.6.0, but needs
both ends of the networkconnector to be => 5.6
Have a peek at:
https://issues.apache
Part of my intention of declaring excluded destinations was to reduce the
amount of traffic over the ADSL line that exists between hub and the spokes.
However, despite the instruction to ban messaging on these destinations,
the amount of traffic and instructions that the hub receives has not
chang
>
> I was expecting to see no traffic of any kind on our hub concerning
> Outbound.Account.>, yet sub requests are still flooding in.
Can you explain more what you mean? Do you see subs being created for that
dest on the networked brokers?
If what you mean is you're seeing the logs below, that's
12 matches
Mail list logo
