Hi Bruno, MICO 2.3.12 is really too old. Could you be so kind and test nearly latest HEAD source code? If possible, please download http://www.mico.org/snapshots/mico-head-2011-01-18.tar.bz2 and give it a try and let us know if it's working for you or not.
Thanks, Karel On 02/10/11 01:56 PM, Bruno MAGNE wrote: > Hi Everybody, > > I still use MiCO 2.3.12 with VS2500 under Windows. > > My application is made of several modules running on multiple PCs. Until now > nothing exceptional because CORBA and MiCO are made for that. > For a standalone version of my application, I am running all modules on a > single PC ; the MiCO communication processes are unchanged except we use only > “localhost” address. > > Under Linux, it works perfectly ; under Windows XP, the same way. The problem > of name resolution appears on Windows Vista/Seven. > > Description of the problem: > > - Even if I use only “localhost” between my modules, NSD and Mico libraries > uses the real name of the machine for the IP resolution and revert resolution > too. > - The consequence is that module registration seems to work on NSD but when > we would like to retrieve a module reference from NSD, it fails. > - I have found that, on Windows Vista/Seven, running NSD with “-ORBNoResolve” > option avoids changing “c:\windows\system32\drivers\etc\host” file. > - But it is not sufficient, I have cases (see enclosed NSD Debug info) where > it does not work. > > The first differences come at line 123 in “error.txt” where we saw the name > of the machine ; in the other case ( ok.txt” file), we see only the IP > address of the machine. > > It seems too that the behavior is different if we have one or multiple NIC > (physical or virtual) on the PC ; for example Ethernet, Wifi, VPN, VMWare > adapters. > > But why MiCO is changing “localhost” to the realname of the machine and/or > one of the IP address different from 127.0.0.1 > > Has somebody experience with such case ; any tips is welcome. Has Mico 2.3.13 > been improved in that way ? > > Thanks in advance for any answer. > > Best Regards > > Bruno Magne > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > > > > _______________________________________________ > Mico-devel mailing list > Mico-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mico-devel -- Karel Gardas kgar...@objectsecurity.com ObjectSecurity Ltd. http://www.objectsecurity.com ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Mico-devel mailing list Mico-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mico-devel
