[omniORB] .Net Remoting and OmniOrb 4.1.7

[Olivier Thiboutot]

Hi,

We are using OmniOrb since a very long time (since 2.80) and we are facing a very strange problem in a very strange configuration.

Here it goes:


-          Context
On Windows Server 2008 R2 or Server 2012 SP1with 2 NICs, we have a service called TaskServer.
All CORBA dlls are built with MSVS 2012.
All wrapper for CORBA are coded with C++ MSVS 2012.
All other dlls are coded and built with C# MSVS 2012.
The service is coded with C# MSVS 2012.
The .Net Framework is version 4.
IPv4 only protocol. (but the same if we mix IPv4 and IPv6).
CORBA config has no fix name nor port.


-          Problematic
The service is using .Net Remoting technology to listen for orders (task).

When we demand a particular task, it loads dll. When the dll are using CORBA 4.1.7 for achieving their duty, it always shutdown the .Net Remoting socket as soon as CORBA load.
The exception in socket .Net remoting is silent. The service never received any message or exception into any .Net callback function


-          Test, conclusion  and Workaround
This never append in 2.8 and MS Visual Studio 6.0 (we tested it).
This never append if only one NIC is used.
We have no problem if we force the TaskServer to load CORBA 4.1.7 prior to lunch .Net remoting listener!

Can Anyone help me to go deeper into this since we receive noting from C++ driver using CORBA 4.1.7 or from CORBA itself.
We receive nothing at the TaskServer service in C#. Only the debugger write down a trace about the socket exception but we do not have the symbols or the code.

Best regards
Olivier Thiboutot
Voxco Inc.
Senior Programmer


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20150511/bee8206e/attachment.html>