[omniORB] JacORB/omniORB GIOP 1.2 protocol error

[Thomas Amsler]

Duncan,

I am in touch with the JacORB developers now. You were right that they
don't support the GIOP 1.2 fragmented messages.  Because my application
depends on "wstring" support, I am forced to use GIOP 1.2.  I have to
check now with the JacORB developers on this issue, in order to have
this feature supported.
Thank you for all your help.


 On Mon, 10 Jun 2002, Duncan Grisby wrote:

> On Friday 7 June, Thomas Amsler wrote:
>
> > I am running a server using omniORB4 and a client using JacORB1.4GA.  I
> > am getting errors while calling this method:
>
> [...]
> > On the server side, omniORB, I am getting this error:
> > omniORB: From endpoint: giop:tcp:192.168.1.10:37384. Detected GIOP 1.2
> > protocol error in input message. Connection is closed.
> >
> > On the client side, JacORB, I am getting this error:
> > [ Connected to 192.168.1.10:37374 ]
> > [ WARNING: Received a Fragment message ]
> > [ WARNING: Received a Fragment message ]
> > java.lang.Error: Messages of type 7 don't have request ids
>
> It looks like JacORB does not support GIOP 1.2 fragmented messages.
> That's a shame, since omniORB always uses fragments with GIOP 1.2.
> Fragmentation allows the marshalling code to go much faster, since it
> doesn't have to figure out how big the message will be before it
> starts sending it.
>
> If that is the problem, the only work-around is to force omniORB to
> use GIOP 1.0. That will work as long as you aren't using wstring,
> which requires 1.2. To force omniORB to only use GIOP 1.0, use the
> command line (or config, env) -ORBmaxGIOPVersion 1.0
>
> Cheers,
>
> Duncan.
>
> --
>  -- Duncan Grisby         --
>   -- duncan@grisby.org     --
>    -- http://www.grisby.org --
>

-- Thomas Amsler
amsler@cs.ucdavis.edu