[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.

I tried increasing the size to 4mb.  I still get the Comm failure =
message.

=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