ok, perfect. thanks!
Gert Vanthienen wrote: > > L.S., > > Your two ServiceMix instances have discovered each other using > multicast packages. As soon as this happens, they will try to set up > a connection between the ActiveMQ brokers, which requires the names of > the machines to be known. Basically, this machine tries to find a > machine named smulv and it can't find the IP address for that machine > in the hosts file or using DNS. Adding an entry to the hosts file as > Ivan explained is one way to fix it. > > Unless you want to cluster your ServiceMix instances, you can also > just disable the multicast discovery in the first place. > http://servicemix.apache.org/javanetsocketexception-error-setting-options.html > explains you how to do this (it's about another exception, but you can > reuse the solution). > > Regards, > > Gert Vanthienen > ------------------------ > Open Source SOA: http://fusesource.com > Blog: http://gertvanthienen.blogspot.com/ > > > > 2009/3/5 MrNinni <[email protected]>: >> >> Hi, >> I work with my friend in the same net. >> If my friend uses ServiceMix in his PC, and I try to use ServiceMix in mi >> PC, ServiceMix responds with this message: >> >> WARN - DiscoveryNetworkConnector - Could not start network bridge >> between: vm://localhost and: tcp://smulv:61616 due to: >> java.net.UnknownHostEception: smulv >> >> where is the problem? thank you. bye. >> -- >> View this message in context: >> http://www.nabble.com/two-servicemix-in-the-same-net-tp22354022p22354022.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > ----- > --- > Gert Vanthienen > http://gertvanthienen.blogspot.com > -- View this message in context: http://www.nabble.com/two-servicemix-in-the-same-net-tp22354022p22368124.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
