Same behaviour occurs with ActiveMQ-4.1.1:
BrokerB Ignoring Subscription ConsumerInfo {commandId = 4, responseRequired
= false, consumerId = ID:xxx-4950-1194986413716-5:1:1:1, destination =
queue://TEST.FOO, prefetchSize = 1, maximumPendingMessageLimit = 0, browser
= false, dispatchAsync = false, selector = null, subscriptionName = null,
noLocal = false, exclusive = false, retroactive = false, priority = 0,
brokerPath = [ID:xxx-4950-1194986413716-2:1], optimizedAcknowledge = false,
noRangeAcks = false, additionalPredicate =
[EMAIL PROTECTED] restricted to 1
network hops only
Regards,
Holger
rajdavies wrote:
>
> I think the first step would be to upgrade to a later release: http://
> activemq.apache.org/activemq-411-release.html
>
> cheers,
>
> Rob
>
> http://open.iona.com/ -Enterprise Open Integration
> http://rajdavies.blogspot.com/
>
>
>
> On Nov 9, 2007, at 7:39 AM, hbruch wrote:
>
>>
>> Hi,
>>
>> we are using a star topology, having multiple 4.0.2-brokers
>> connected to one
>> central broker via a slow, unreliable network.
>>
>> Network connectors are configured with a networkTTL=1. However,
>> AdvisoryMessages
>> are sent over two hops before they get discarded:
>>
>> 2007-11-09 07:35:13,733 DEBUG DemandForwardingBridge -
>> Ignoring
>> Subscription ConsumerInfo {commandId = 3, responseRequired = false,
>> consumerId = ID:xxx-4397-1194590104420-5:1:1:1, destination =
>> queue://TEST.FOO, prefetchSize = 1, maximumPendingMessageLimit = 0,
>> browser
>> = false, dispatchAsync = false, selector = null, subcriptionName =
>> null,
>> noLocal = false, exclusive = false, retroactive = false, priority = 0,
>> brokerPath = [ID:xxx-4397-1194590104420-2:1], optimizedAcknowledge
>> = false,
>> noRangeAcks = false, additionalPredicate =
>> [EMAIL PROTECTED] restricted
>> to 1
>> network hops only
>>
>> Is there a way to restrict advisory messages to only one hop?
>> The network connector is configured to use the DemandForwardingBridge
>> (conduitSubscriptions=false):
>> <networkConnector name="B" uri="static:tcp://localhost:61001"
>> failover="true" prefetchSize="1" conduitSubscriptions="false"
>> dispatchAsync="false"/>
>>
>> It seems to me, that TopicSubscriptions from remote brokers don't have
>> NetworkBridgeFilter set as additionalPredicate. Is this correct?
>>
>> Currently we encounter many irrelevant advisory messages filling up
>> memory
>> pretty
>> fast since connections are unreliable and therefore consumers
>> connect/disconnect regularly.
>> As a result, the UsageManager.waitForSpace() steps in soon and
>> halts the
>> producer.
>>
>> Any help is appreciated,
>> thanks,
>> Holger
>> --
>> View this message in context: http://www.nabble.com/NetworkTTL-
>> filters-AdvisoryMessages-only-after-transmission-
>> tf4776251s2354.html#a13662640
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context:
http://www.nabble.com/NetworkTTL-filters-AdvisoryMessages-only-after-transmission-tf4776251s2354.html#a13734290
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
