On 10/26/2010 4:24 AM, Gary Tully wrote:
That looks like a bug in the peer transport factory. I uses
localhost:0 as the tcp transport url, but localhost maps to the
loopback address since 5.3[1] so the connection is refused.
The peer transport factory should use the wildcard address, 0.0.0.0
Fo
Jira case created as https://issues.apache.org/activemq/browse/AMQ-2999
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-with-simple-peer-configuration-my-config-or-AMQ-issue-tp3013268p3013457.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> Shouldn't PC1 see the port on PC1 and otherway around? I'd expect the
> embedded brokers on PC1 and PC2 trying to connect to each others ports and
> not to localhost???
>
> Is this an AMQ issue or is the problem in my config...??? Any way around it?
>
> NOTE: WL100103 is the name of the consumer side PC and WD080208 is the name
> of the producer side PC and both are in DNS and each one can ping the other
> with those names. Both machines are on the same subnet and actually
> connected to the same LAN-switch.
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Problem-with-simple-peer-configuration-my-config-or-AMQ-issue-tp3013268p3013268.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://blog.garytully.com
http://fusesource.com
the name
of the producer side PC and both are in DNS and each one can ping the other
with those names. Both machines are on the same subnet and actually
connected to the same LAN-switch.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-with-simple-peer-configuration-my
