[omniORB] Bug?

[youzhong liu]

Thanks all for all the replies. As most of the replies suggested, I
changed the default GIOP message size and solved the problem. 

Youzhong

On Fri, 23 Jul 1999, James Riden wrote:

> 
> Youzhong,
> 
> I think this is a default limit within omniORB. See section
> 4.5 (GIOP Message Size) in the omniORB2 manual on how to change
> it.
> 
> http://www.uk.research.att.com/omniORB/doc/omniORB2/node5.html#giopmsg
> 
> (anyone who is doing stuff other than performance testing, please
> note *why* the limit has been set )
> 
> hth.
> 
> cheers,
>  James
> 
> At 10:14 PM 7/22/99 -0400, youzhong liu wrote:
> >Hi, All,
> >
> >I am running performance testing on several ORB implementations. To
> >describe the problem, I am using a quite simple idl.
> >
> >typedef sequence<float>   float_seq;
> >
> >interface Echo{
> >     void floatSeq  (in float_seq x);
> >};
> >
> >When the size of the parameter is increased to be 2M Bytesi or above, an
> >exception is raised. I can't determine the exception type. I only know
> >it is not a CORBA::COMM_FAILURE or omniORB::fatalException.
> >
> >I am not sure whether it is a bug of omniORB, or omniORB's limitation,
> >or my fault. 
> >
> >If anyone has the similar experiences, please advice me how to get a
> >solution or draw a conclusion for this exception. 
> >
> >Thanks very much in advance for your reply!
> >
> >Sincerely,
> >Youzhong liu
> >Univ. of Florida
> >
> >
> 
> 
>