On Thu, Apr 2, 2009 at 6:30 PM, Phillips, Chad <[email protected]> wrote: > I'm running multiple instances of an application which creates a new SCA > domain like this: SCADomain.newInstance("foo.composite"). I'm using the > 1.x branch at r755721 (w/ core-databinding and databinding-jaxb at > r756209). > > Each instance of the application is running on a different physical > machine. The setup/scenario is pretty straight forward: > > 1.) Start AppInstance1 on MachineA > 2.) Start AppInstance2 on MachineB > > What I'm noticing is that AppInstance2 finds AppInstance1 and tries to > link up with it. Is there a way to disable this feature? The main > problem is that MachineB can't resolve MachineA's hostname and seems to > get stuck in an endless loop like this: > > [java] - Establishing network connection between from > vm://localhost to tcp://foobar:50656 > [java] - Connector vm://localhost Started > [java] - Connector vm://localhost Stopped > [java] - Could not start network bridge between: vm://localhost > and: tcp://foobar:50656 due to: java.net.UnknownHostException: foobar > [java] - localhost bridge to Unknown stopped > > This message repeats every few seconds on AppInstance2. I know I could > update MachineB's hosts file for my testing purposes but that solution > would not be acceptable in my target environment. Really what I want to > do is disable any communication between the runtimes. > > - Chad Phillips >
Are you including the jar tuscany-binding-sca-jms and if so could you try removing it? ...ant
