ok thank you very much for the explanation :)
Gary Tully ha scritto:
> Both A and B are listening on advisories from each other. When A gets
> a subscription, it fires an advisory which B picks up. B responds by
> creating a corresponding subscription on B which results in an
> advisory. The advisory on B is picked up by the listener on A but the
> TTL of 1 kicks in and the advisory is ignored. It is the TTL that
> provides the first barrier to circular looping of subscription info
> when every broker knows about every other. The other barrier is that a
> subscription that already exists on a local broker is ignored also.
> So while the TTL is correctly effecting subscription info in this
> case, it typically is relevant to message dispatch, restricting how
> many hops a message will traverse before stagnating.
>
> 2008/10/31 Yari Marchetti <[EMAIL PROTECTED]>:
>
>> Hi,
>> i have a network of brokers composed by 2 broker connected to each
>> other; all clients (producer and consumers )are attached to broker 'A'.
>> Network TTL is set to 1.
>>
>> In broker 'A' log file i find some:
>>
>> A Ignoring Subscription ConsumerInfo {commandId = 141717,
>> responseRequired = false, consumerId =
>> ID:xxx-38175-1223457148842-2:1:1:70861, destination = queue://test,
>> prefetchSize = 1000, maximumPendingMessageLimit = 0, browser = false,
>> dispatchAsync = true, selector = null, subscriptionName = null, noLocal
>> = false, exclusive = false, retroactive = false, priority = 0,
>> brokerPath = [ID:xxxx-40277-1223456997662-0:0], optimizedAcknowledge =
>> false, noRangeAcks = false, additionalPredicate =
>> [EMAIL PROTECTED] restricted to
>> 1 network hops only
>>
>> but i dont get what's happening. I tried to google a bit but i didn't find
>> an exhaustive answer.
>>
>> regards,
>> Yari
>>
>>
