Have you specified the tcp://localhost:61616 url when creating the JMS flow
?
Like
<sm:container flow="jms?jmsURL=tcp://localhost:61616"
Else, you will create an embedded broker with a multicast discovery (peer://
protocol)
Cheers,
Guillaume Nodet
On 6/14/06, William Blackburn <[EMAIL PROTECTED]> wrote:
We are using JMSflow. Our developers are working independently on
testing and development, and I want to stop the ActiveMQ brokers from
discovering each othe
r and trying to link up. My activeMQ file has a
broker section that looks like:
<broker id="broker" useJmx="false">
<persistenceAdapter>
<journaledJDBC journalLogFiles="5"
dataDirectory="#dataDir" dataSource="#postgres-ds"/>
</persistenceAdapter>
<transportConnectors>
<transportConnector uri="tcp://localhost:61616"/>
</transportConnectors>
</broker>
I've just received confirmation from the ActiveMQ user list that
leaving the networkconnector config out, as above, should be enough
to diable discovery, yet when I start my servicemix app, I see:
Multicast Discovery Agent Notifier 2006-06-14 11:26:31,452 INFO
[DemandForwardingBridge:start] Starting a network connection between
vm://peer-fastgt-local-49667-1150309582986-4-0#2 and tcp://null:0 has
been established.
Multicast Discovery Agent Notifier 2006-06-14 11:26:31,464 WARN
[NetworkConnector:onServiceAdd] Could not start network bridge
between: vm://peer-fastgt-local-49667-1150309582986-4-0?network=true
and: tcp://T43-Kiev2:2378 due to: java.net.UnknownHostException: T43-
Kiev2
java.net.UnknownHostException: T43-Kiev2
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:430)
at java.net.Socket.connect(Socket.java:507)
at org.apache.activemq.transport.tcp.TcpTransport.doStart
(TcpTransport.java:294)
...
indicating that discovery is still active. Is it possible that our
use of JMSflow is triggering this behavior?
Thanks,
B.J.
