James,
thanks... So I just do the following (see below). Can you explain why it
was finding that particular IP address? Or can you point me to how discovery
is performed?
<networkConnectors>
<!-- by default just auto discover the other brokers -->
<!--
<networkConnector name="default-nc" uri="multicast://default"/>
-->
<!--
<networkConnector name="host1 and host2"
uri="static://(tcp://host1:61616,tcp://host2:61616)" failover="true"/>
-->
</networkConnectors>
James.Strachan wrote:
>
> There's no spyware! I suspect its the multicast discovery; you might
> wanna disable that.
>
> On 5/1/07, sparky2708 <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>> Our System Administrator was looking at the connections that my
>> out-of-the-box ActiveMQ installation was doing and we couldn't figure out
>> why it was trying to connect to the following IP address in PA (port
>> 61616):
>>
>> c-68-84-120-96.hsd1.pa.comcast.net (68.84.120.96)
>>
>> Can someone please investigate whethere there is spyware in ActiveMQ or
>> if
>> there is an issue with something in the config file? (I am just using
>> version 4.1.1 downloaded for Linux)
>> --
>> View this message in context:
>> http://www.nabble.com/Why-is-ActiveMQ-4.1.1-trying-to-make-a-connection-to-an-IP-address-in-PA--tf3675976s2354.html#a10271936
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
>
--
View this message in context:
http://www.nabble.com/Why-is-ActiveMQ-4.1.1-trying-to-make-a-connection-to-an-IP-address-in-PA--tf3675976s2354.html#a10272856
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
