Naming Resolution problem on Windows Vista/Seven

[Bruno MAGNE]

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

[Karel Gardas]

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

Post by Bruno MAGNE
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.
- 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
------------------------------------------------------------------------------
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
https://lists.sourceforge.net/lists/listinfo/mico-devel

[Bruno MAGNE]

Hi Karel,

We have already downloaded version 2.3.13 and compiled successfully with VS2005 SP1. Currently no tests have been done with that version.

I have downloaded too the snapshot "mico-head-2011-01-18.tar.bz2" but I have some compilation problems.

1) In iop.cc with the line "_orbids[MICOMT::Thread::self()] = map;"

2) In orb.cc with the line " _invokes[MICOMT::Thread::self()] = map;"

I guess, it is the same error.


3) In watm.cc with the error

watm.cc(283) : error C2259: 'WATM::WATMProfile' : unable to instantiate an abstract class due to the following members:
'void CORBA::IORProfile::objectkey_nc(CORBA::Octet *,CORBA::Long)' : is abstract
E:\Mico.Win32\mico-head-2011-01-18\include\mico/ior.h(143) : see declaration of 'CORBA::IORProfile::objectkey_nc'


Can you help me ?

Best Regards

Bruno Magne

-----Message d'origine-----
De : Karel Gardas [mailto:***@objectsecurity.com]
Envoyé : vendredi 11 février 2011 18:29
À : Bruno MAGNE
Cc : 'mico-***@lists.sourceforge.net'
Objet : Re: [mico-devel] Naming Resolution problem on Windows Vista/Seven


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

Post by Bruno MAGNE
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.
- 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
------------------------------------------------------------------------------
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
https://lists.sourceforge.net/lists/listinfo/mico-devel

[Karel Gardas]

Hi Bruno,

indeed, when I tried compiling latest HEAD with VC++ 2005 I've got those
errors too. I've fixed that already (or attempted to do) but then I get
strange issue (block on mutex) in ORB_init which is quite surprising
since I'm using recursive mutex on that place. I'll try to have a look
at it again sometimes next week.

Cheers,
Karel

Post by Bruno MAGNE
Hi Karel,
We have already downloaded version 2.3.13 and compiled successfully with VS2005 SP1. Currently no tests have been done with that version.
I have downloaded too the snapshot "mico-head-2011-01-18.tar.bz2" but I have some compilation problems.
1) In iop.cc with the line "_orbids[MICOMT::Thread::self()] = map;"
2) In orb.cc with the line " _invokes[MICOMT::Thread::self()] = map;"
I guess, it is the same error.
3) In watm.cc with the error
'void CORBA::IORProfile::objectkey_nc(CORBA::Octet *,CORBA::Long)' : is abstract
E:\Mico.Win32\mico-head-2011-01-18\include\mico/ior.h(143) : see declaration of 'CORBA::IORProfile::objectkey_nc'
Can you help me ?
Best Regards
Bruno Magne
-----Message d'origine-----
Envoyé : vendredi 11 février 2011 18:29
À : Bruno MAGNE
Objet : Re: [mico-devel] Naming Resolution problem on Windows Vista/Seven
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

Post by Bruno MAGNE
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.
- 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
------------------------------------------------------------------------------
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
https://lists.sourceforge.net/lists/listinfo/mico-devel