[omniORB] JacORB/omniORB GIOP 1.2 protocol error

[Thomas Amsler]

Duncan,

I read in some news group messages that some GIOP 1.2 implementations 
allow to "turn off" fragmented messages.  Does omniORB allow this?

--(snip)---

Any ORB with GIOP 1.2 support must accept fragmented messages. (A compliant
GIOP 1.2 implementation can choose to never send fragments, but must be
able to accept them if they are used by the other end.)

---(snip)---

Thank you.

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

-- 
Thomas Amsler
amsler@cs.ucdavis.edu
http://davinci.cs.ucdavis.edu/thomas

"Imagination is more important than knowledge."
	--Albert Einstein