Dev - Issue with RMI Registry
Locked
 
|
During our most recent ofbiz upgrade, we encountered a problem where I can only run one ofbiz instance on our development server. We am running multiple instances on one speedy box and ran into a conflict where the newly added NamingServiceContainer no longer respects the host configured in the configured file - where with CAROL we could start our containers on different RMI hosts.
It appears that the call to LocateRegistry.createRegistry on line 62 in org.ofbiz.base.container.NamingServiceContainer is called with only a port. Does anyone know an easy way to configure this with a host as well? Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - Issue with RMI Registry
|
|
Tim, Did you try changing the value in the ofbiz-containers.xml file? -David Tim Ruppert wrote: > During our most recent ofbiz upgrade, we encountered a problem where I can only run one ofbiz instance on our development server. We am running multiple instances on one speedy box and ran into a conflict where the newly added NamingServiceContainer no longer respects the host configured in the configured file - where with CAROL we could start our containers on different RMI hosts. > > It appears that the call to LocateRegistry.createRegistry on line 62 in org.ofbiz.base.container.NamingServiceContainer is called with only a port. Does anyone know an easy way to configure this with a host as well? > > Cheers, > Tim > _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - Issue with RMI Registry
|
|
I have not. I am sure that changing the ports will fix the issue - it's
almost foolproof. What I'm trying to do is have that NamingServiceContainer aware of something other than localhost. I will try to pass in a host, but the call doesn't pass it it in the Java class, so there's little hope there - don't you agree? Wouldn't this cause a large issue in other, shared environments unless everyone just came up with their own ports? Is it possible to make this service more aware? Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 David E Jones wrote: > Tim, > > Did you try changing the value in the ofbiz-containers.xml file? > > -David > > > Tim Ruppert wrote: > >> During our most recent ofbiz upgrade, we encountered a problem where I can only run one ofbiz instance on our development server. We am running multiple instances on one speedy box and ran into a conflict where the newly added NamingServiceContainer no longer respects the host configured in the configured file - where with CAROL we could start our containers on different RMI hosts. >> >> It appears that the call to LocateRegistry.createRegistry on line 62 in org.ofbiz.base.container.NamingServiceContainer is called with only a port. Does anyone know an easy way to configure this with a host as well? >> >> Cheers, >> Tim >> >> > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev > _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - Issue with RMI Registry
|
|
So, as expected changing the ports made it work and all is groovy. As I
said below in this thread, most (if no all) of the other containers allow you to configure the host that the port is connecting to. It would be a huge help if someone could let me know how configurability could be exposed on this service. Cheers, Tim Tim Ruppert wrote: > I have not. I am sure that changing the ports will fix the issue - > it's almost foolproof. What I'm trying to do is have that > NamingServiceContainer aware of something other than localhost. I > will try to pass in a host, but the call doesn't pass it it in the > Java class, so there's little hope there - don't you agree? > > Wouldn't this cause a large issue in other, shared environments unless > everyone just came up with their own ports? Is it possible to make > this service more aware? > > Cheers, > Tim > > -- > Tim Ruppert > HotWax Media > http://www.hotwaxmedia.com > > o:801.649.6594 > f:801.649.6595 > > > > David E Jones wrote: >> Tim, >> >> Did you try changing the value in the ofbiz-containers.xml file? >> >> -David >> >> >> Tim Ruppert wrote: >> >>> During our most recent ofbiz upgrade, we encountered a problem where >>> I can only run one ofbiz instance on our development server. We am >>> running multiple instances on one speedy box and ran into a conflict >>> where the newly added NamingServiceContainer no longer respects the >>> host configured in the configured file - where with CAROL we could >>> start our containers on different RMI hosts. >>> >>> It appears that the call to LocateRegistry.createRegistry on line 62 >>> in org.ofbiz.base.container.NamingServiceContainer is called with >>> only a port. Does anyone know an easy way to configure this with a >>> host as well? >>> >>> Cheers, >>> Tim >>> >>> >> >> _______________________________________________ >> Dev mailing list >> [hidden email] >> http://lists.ofbiz.org/mailman/listinfo/dev >> > _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - Issue with RMI Registry
|
|
Tim, Yes, it would be nice to have that flexibility. Unfortunately the LocateRegistry class for the RMI Registry doesn't support this. I guess the alternative is to find and use a different JNDI name server or something... Here are the details for this class: http://java.sun.com/j2se/1.4.2/docs/api/java/rmi/registry/LocateRegistry.html -David Tim Ruppert wrote: > So, as expected changing the ports made it work and all is groovy. As I > said below in this thread, most (if no all) of the other containers > allow you to configure the host that the port is connecting to. It > would be a huge help if someone could let me know how configurability > could be exposed on this service. > > Cheers, > Tim > > Tim Ruppert wrote: >> I have not. I am sure that changing the ports will fix the issue - >> it's almost foolproof. What I'm trying to do is have that >> NamingServiceContainer aware of something other than localhost. I >> will try to pass in a host, but the call doesn't pass it it in the >> Java class, so there's little hope there - don't you agree? >> >> Wouldn't this cause a large issue in other, shared environments unless >> everyone just came up with their own ports? Is it possible to make >> this service more aware? >> >> Cheers, >> Tim >> >> -- >> Tim Ruppert >> HotWax Media >> http://www.hotwaxmedia.com >> >> o:801.649.6594 >> f:801.649.6595 >> >> >> >> David E Jones wrote: >>> Tim, >>> >>> Did you try changing the value in the ofbiz-containers.xml file? >>> >>> -David >>> >>> >>> Tim Ruppert wrote: >>> >>>> During our most recent ofbiz upgrade, we encountered a problem where >>>> I can only run one ofbiz instance on our development server. We am >>>> running multiple instances on one speedy box and ran into a conflict >>>> where the newly added NamingServiceContainer no longer respects the >>>> host configured in the configured file - where with CAROL we could >>>> start our containers on different RMI hosts. >>>> >>>> It appears that the call to LocateRegistry.createRegistry on line 62 >>>> in org.ofbiz.base.container.NamingServiceContainer is called with >>>> only a port. Does anyone know an easy way to configure this with a >>>> host as well? >>>> >>>> Cheers, >>>> Tim >>>> >>>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [hidden email] >>> http://lists.ofbiz.org/mailman/listinfo/dev >>> > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - Issue with RMI Registry
|
|
Thanks - this is where we were stumped as well :)
Changing the ports does work - so we're in a good shape to go forward. We were just trying to keep the patching at the domain level instead of the port level (I find it easier to understand). We'll look into a different way of handling this issue if someone else doesn't get there first. I definitely think this should be configurable. Thanks for looking into it David Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 David E. Jones wrote: > Tim, > > Yes, it would be nice to have that flexibility. Unfortunately the LocateRegistry class for the RMI Registry doesn't support this. I guess the alternative is to find and use a different JNDI name server or something... > > Here are the details for this class: > > http://java.sun.com/j2se/1.4.2/docs/api/java/rmi/registry/LocateRegistry.html > > -David > > > Tim Ruppert wrote: > >> So, as expected changing the ports made it work and all is groovy. As I >> said below in this thread, most (if no all) of the other containers >> allow you to configure the host that the port is connecting to. It >> would be a huge help if someone could let me know how configurability >> could be exposed on this service. >> >> Cheers, >> Tim >> >> Tim Ruppert wrote: >> >>> I have not. I am sure that changing the ports will fix the issue - >>> it's almost foolproof. What I'm trying to do is have that >>> NamingServiceContainer aware of something other than localhost. I >>> will try to pass in a host, but the call doesn't pass it it in the >>> Java class, so there's little hope there - don't you agree? >>> >>> Wouldn't this cause a large issue in other, shared environments unless >>> everyone just came up with their own ports? Is it possible to make >>> this service more aware? >>> >>> Cheers, >>> Tim >>> >>> -- >>> Tim Ruppert >>> HotWax Media >>> http://www.hotwaxmedia.com >>> >>> o:801.649.6594 >>> f:801.649.6595 >>> >>> >>> >>> David E Jones wrote: >>> >>>> Tim, >>>> >>>> Did you try changing the value in the ofbiz-containers.xml file? >>>> >>>> -David >>>> >>>> >>>> Tim Ruppert wrote: >>>> >>>> >>>>> During our most recent ofbiz upgrade, we encountered a problem where >>>>> I can only run one ofbiz instance on our development server. We am >>>>> running multiple instances on one speedy box and ran into a conflict >>>>> where the newly added NamingServiceContainer no longer respects the >>>>> host configured in the configured file - where with CAROL we could >>>>> start our containers on different RMI hosts. >>>>> >>>>> It appears that the call to LocateRegistry.createRegistry on line 62 >>>>> in org.ofbiz.base.container.NamingServiceContainer is called with >>>>> only a port. Does anyone know an easy way to configure this with a >>>>> host as well? >>>>> >>>>> Cheers, >>>>> Tim >>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [hidden email] >>>> http://lists.ofbiz.org/mailman/listinfo/dev >>>> >>>> >> >> _______________________________________________ >> Dev mailing list >> [hidden email] >> http://lists.ofbiz.org/mailman/listinfo/dev >> > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev > _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |