[omniORB] linux, windows communication problem + new problems

Karl Schulze k.schulze at synedra.com
Tue Oct 10 11:50:28 BST 2006


Hello everybody

About 4 month ago I posted a strange problem while using omniORB naming 
service
and servers under Linux and clients under windows. After sending some 
trace-output
nothing new about that topic was posted here.

I have now redone all my tests with omniORB 4.1.0-rc1 to test if this 
topic was maybe
fixed within this new release. But the problem still remains the same.

The setup I use is the following: omniNames and the eg3_impl are running 
on a Linux
box with some parameters set, that are
scanGranularity = 1
inConScanPeriod = 1
threadPerConnectionPolicy = 0
maxServerThreadPoolSize = 5

For the client I use a slightly modified version of eg3_clt. Where the 
main reads like
int
main (int argc, char **argv)
{
 try {
   CORBA::ORB_var orb = CORBA::ORB_init(argc, argv);
   for (CORBA::ULong count=0; count < 1000; count++)
   {
       cerr << count << "/1000" << endl;
       CORBA::Object_var obj = getObjectReference(orb);
       Echo_var echoref = Echo::_narrow(obj);
       hello(echoref);
       Sleep(2000); // sleep(2); for Linux
   }

   orb->destroy();
 } ...
with the corresponding include for the sleep (#include <Windows.h> for 
win or
#include <unistd.h> for Linux)

Usually the client get a CORBA::COMM_FAILURE for count is around 200.

While performing this tests I have tried some different setups too.
Namely I have used the above egl_clt in parallel from 2 different Linux 
boxes
(different from the one where the server and omniNames is running).
The server and omniNames are using the same parameters stated above.
The strange thing is, after a while (count is around 50-200) all 4 involved
communication partners seems to be stalled. Any new connection attempt
also stall directly. When using just one client I was not able to 
produce this
problem.

If it is useful I can provide the trace-output for all communication 
partners,
but they are rather long :)

Is this behavior a known behavior with the parameters I use?
Am I doing something wrong (out of specifications)?

Thanks
Karl




More information about the omniORB-list mailing list