[omniORB] MARSHAL Exception with Visibroker/Java and Any

[Gary D. Duzan]

   Did this not make it into 2.7.1? I'm running into the same thing
with longs now and I don't see any entry in the offset table which is
close. (The offset to the long is also misaligned, but there is nothing
with 20 bytes or so, at least.) I'll probably go ahead and try hacking
something into typecode.cc for our own use, but if you have a patch
for it I'll take it. :-)
   Thanks.

					Gary Duzan
					GTE Laboratories



In Message <Pine.LNX.4.04.9903121205420.19547-100000@pitanga> ,
   David Riddoch <djr@uk.research.att.com> wrote:

=>
=>Gary,
=>
=>
=>Looks like an omniORB problem. I've had a look at the code, and we fail if
=>another ORB passes us a TypeCode which contains an indirection to a
=>primitive type.
=>
=>The reason it didn't work in previous versions of omniORB, is that we
=>didn't support indirections at all.
=>
=>I'm sorting it out now, and will release omniORB 2.7.1 when it've
=>finished!
=>
=>
=>Cheers,
=>David
=>
=>
=>
=>On Thu, 11 Mar 1999, Gary D. Duzan wrote:
=>
=>> 
=>>    I'm seeing a problem when trying to have a Visibroker/Java process
=>> send an Any-encoded struct to an OmniORB process. Running it through
=>> the debugger I'm seeing that it is dying while trying to unmarshall the
=>> typecode. I believe I have all the appropriate patches applied. The
=>> CORBA::MARSHAL exception is being raised in
=>> 
=>> Typecode_marshaller::unmarshall(MemBufferedStream&,
=>> 				TypeCode_offsetTable*).
=>> 
=>> Some local variable values are tck=0xffffffff, currpos=96, and
=>> offset=-25. It was called by
=>> 
=>> TypeCode_struct::NP_unmarshallComplexParams(MemBufferedStream&,
=>> 					    TypeCode_offsetTable*).
=>> 
=>> The encoded type is a struct with 9 fields, and it seems to be choking
=>> on the 2nd one. The first two fields are both strings. The name and
=>> typecode for the first seem to be unmarshalled fine, getting a
=>> plt_Simple and CORBA::tk_string in the respective switch blocks, and
=>> while the name of the second is unmarshalled fine, the typecode comes
=>> out as plt_None and 0xffffffff.
=>>    Has anyone else seem anything like this? It could certainly be a
=>> Visibroker/Java problem, but with all the new Any code in 2.7.0, I tend
=>> to suspect OmniORB. We're trying 2.5.0 to see if we can get that to
=>> work, but we haven't finished recompiling yet. Any help getting this to
=>> work would be appreciated.
=>> 
=>> 					Gary Duzan
=>> 					GTE Laboratories
=>> 
=>> 
=>> 
=>> 
=>
=>