activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kristoffer <sto...@gmail.com>
Subject Re: MulticastDiscoveryAgent - brokerName not set
Date Thu, 19 Oct 2006 09:22:32 GMT

Hi, 

Did your process hang? Mine did, here's my post on the problem:
http://www.nabble.com/Client-hangs-in-MulticastDiscoveryAgent-tf2471996.html 

regards,
-Kristoffer


Sanjiv Jivan wrote:
> 
> I've seen those warnings too when running in discovery mode even though
> I've
> set the broker name in the ActiveMQ config.
> 
> On 7/31/06, jcarreira <jcarreira@gmail.com> wrote:
>>
>>
>> I'm getting this error:
>>
>> 2006-07-31 11:02:17,469 [main] WARN
>> org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent-
>> brokerName not set
>>
>> Here's my broker configuration:
>>
>>    <amq:broker brokerName="cluster" useJmx="true">
>>        <!--  Use the following to set the broker memory limit (in bytes)
>> -->
>>        <amq:memoryManager>
>>            <amq:usageManager limit="1048576"/>
>>        </amq:memoryManager>
>>
>>        <amq:networkConnectors>
>>            <amq:networkConnector uri="multicast://nirvana-dev"/>
>>        </amq:networkConnectors>
>>
>>
>>        <amq:persistenceAdapter>
>>            <amq:memoryPersistenceAdapter/>
>>        </amq:persistenceAdapter>
>>
>>        <amq:transportConnectors>
>>            <amq:transportConnector uri="tcp://localhost:61616"
>> discoveryUri="multicast://nirvana-dev"/>
>>        </amq:transportConnectors>
>>
>>    </amq:broker>
>>
>> Can anyone clue me in to what I've configured incorrectly?
>> --
>> View this message in context:
>> http://www.nabble.com/MulticastDiscoveryAgent---brokerName-not-set-tf2028089.html#a5577527
>> Sent from the ActiveMQ - User forum at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/MulticastDiscoveryAgent---brokerName-not-set-tf2028089.html#a6893284
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message