OK, I made the mods to the bundle mvn script and I'm no longer seeing the errors. Thanks for all the help.
________________________________ From: ant elder [mailto:[email protected]] Sent: Tuesday, April 14, 2009 00:35 To: [email protected] Subject: Re: Tuscany runtime linking up with other runtimes Ok looking in that build script its using the Tuscany bundle jar which in the 1.x trunk code includes all of the different binding.sca impls so thats where this is coming from, its not enough to remove binding-sca-jms from the modules folder you'd need to also take it out of the distribution/bundle/pom.xml. ...ant On Tue, Apr 7, 2009 at 4:43 PM, Phillips, Chad <[email protected]> wrote: Hi Simon, I'm using the manifest jar and my Server class creates a new domain via SCADomain.newInstance("test.composite"). If you want to look at a test program that can reproduce the error, see [1] below. I wrote it for TUSCANY-2853 which is unrelated but I can reproduce the same error by starting up the server (by running ant server) on Machines A/B. [1] https://issues.apache.org/jira/secure/attachment/12402183/test2.zip -----Original Message----- From: Simon Laws [mailto:[email protected]] Sent: Tuesday, April 07, 2009 03:27 To: [email protected] Subject: Re: Tuscany runtime linking up with other runtimes On Mon, Apr 6, 2009 at 4:49 PM, Phillips, Chad <[email protected]> wrote: > I removed tuscany-binding-sca-jms-1.5-SNAPSHOT.jar from the modules dir in both installs but I'm still getting the error. > > -----Original Message----- > From: ant elder [mailto:[email protected]] > Sent: Saturday, April 04, 2009 23:03 > To: [email protected] > Subject: Re: Tuscany runtime linking up with other runtimes > > 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 > Hi Chad I think Ant is suggesting that this is our JMS support (and more likely ActiveMQ on which it is built) trying to do something clever behind the scenes so we need to disable it. How are you actually starting up you application instances? Do you refer to the "all" jar or the "manifest" jar? Regards Simon
