[omniORB] Communications Failure on server after executes method

[David Morgenlender]

Sai-Lai,

>> I'm currently using omniORB 2.5.  I have a couple of methods running =
on
>> the server (under ETS-Kernel).  The client is running on a different
>> system (Win95). One method is working ok.  The other method seems to =
be=20
>> working ok, except a  "Communication failure" message is generated =
after=20
>> the method exits.  The message is generated in TFactory.cc in=20
>> tcpSocketWorker::_realRun().  It catches  a COMM_FAILURE exception,
>> checks for a trace level >=3D3D 5, then generates the  message.
>
>> The only significant difference between the calls to the 2
>> methods, is  the problematic method has an unbounded sequence as an
>> output parameter;  it consists of 500,000 ULong values;  the sequence=20
>> seems to be returned properly.
>>=20
>> Do you have any idea what could be causing the problem & whether it's
>> anything to be concerned about?
>
>500,000 ULong =3D 2Mbytes. Your reply definitely exceeds the default =
limit on
>the GIOP message size imposed by the ORB. Just increase the limit using
>omniORB::MaxMessageSize(size_t newvalue) on *both* the client and the
>server. See the user guide for details.

Thanks for the suggestion.  But, I don't think that's the problem.  I =
just
looked at the omniORB code;  the default value for max_giop_message_size;=
  it's
2048 * 1024, i.e. 2,097,152, 2mb.  The sequence size I used is 500000 * =
4, i.e.
2,000,000, less than 2mb ... or is there more than 97,152 bytes of =
overhead?

Also, the sequence was transferred properly.

At one point, I had the sequence size as much larger than 2mb =
(approximately
4mb, as I recall).  The symptoms were different than the Comm failure;  =
an
exception was generated.

I guess it couldn't hurt to increase the maximum message size though!  =
I'll let
you know what I discover.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Dave Morgenlender
e-mail: dmorgen@alum.mit.edu
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D