I would like 2 registries, one on each server. The 'client' can use the registry of the host running the other mmbase to perform the lookup.
I think it starts to makes sense.... Edwin -----Oorspronkelijk bericht----- Van: Kees Jongenburger [mailto:[EMAIL PROTECTED] Verzonden: woensdag 3 december 2003 17:23 Aan: [EMAIL PROTECTED] Onderwerp: Re: configuring RMI On Wednesday 03 December 2003 05:05 pm, Edwin van der Elst wrote: > Hi , > > I'm trying to configure 2 mmbase instances to access each others cloud. > It works fine if I deploy both war files on the same tomcat, but I have some > troubles getting it to work on multiple servers. http://www.mmbase.org/docs/backenddevelopers/ar01s05mmci.html There are 3 parties 1- the registry 2- cloud a 3- cloud b by default the registry binds to localhost if cloud "a" connects to the registry via localhost , the registry will get the local address of cloud a if after someone from the "outer" world connects to the registry the registry will tel that "person" the wrong ip number. Solution is to run the registry on the public address (therefore you need to configure the <property name="host"> in mmbaseroot.xml do you want to run 1 or 2 registries? If you run only one registry you need to also configure the RMIRegistryServer in rmmci.xml so that the "b" cloud does not create a registry but also binds to the existing registry. did you know it's also possible to run rmi over http? > > When one tomcat accesses the other, I get the following exception: > > mmlog4j-staging.log 2003-12-03 16:59:33,197 ERROR > nl.leeuwarden.builders.PublishingQueueBuilder run.115 - Throwable > error:Connection refused to host: 192.168.0 > .35; nested exception is: > java.net.ConnectException: Connection refused: connect rmi://localhost:4022/staging rmi://192.168.0.35:4022/live the ip number + port of the url part point to the registry so it looks like you are running 2 registies
