Visibroker and wstrings (was: RE: [omniORB] wstring corruption, omniOrb -> Orbacus )

[Duncan Grisby]

On Friday 15 March, brk@jenkon.com wrote:

> Thanks Duncan, that does indeed help! The next thing is to actually call the
> method, which goes like this:
> 
> omniORB:  send codeset service context: ( ISO-8859-1,UTF-16)
> omniORB: sendChunk: to giop:tcp:209.210.37.31:4504 132 bytes
> 4749 4f50 0102 0100 7800 0000 0400 0000 GIOP....x.......
> 0300 0000 0000 0000 2400 0000 0056 4201 ........$....VB.
> 0000 0002 2f00 2020 0000 000b 4261 6e6b ..../.  ....Bank
> 4d61 6e61 6765 7220 0000 01d9 178c 6e71 Manager ......nq
> 0500 0000 6e65 7773 005f 6964 0100 0000 ....news._id....
> 0100 0000 0c00 0000 0100 0000 0100 0100 ................
> 0901 0100 0301 0c01 1800 0000 fffe 6800 ..............h.
> 6500 6c00 6c00 6f00 2000 7400 6800 6500 e.l.l.o. .t.h.e.
> 7200 6500                               r.e.
> omniORB: inputMessage: from giop:tcp:209.210.37.31:4504 68 bytes
> 4749 4f50 0102 0101 3800 0000 0400 0000 GIOP....8.......
> 0200 0000 0000 0000 1e00 0000 4944 4c3a ............IDL:
> 6f6d 672e 6f72 672f 434f 5242 412f 4d41 omg.org/CORBA/MA
> 5253 4841 4c3a 312e 3000 01d9 0000 0000 RSHAL:1.0.......
> 0100 0000                               ....
> omniORB: throw MARSHAL from GIOP_C.cc:241 (NO,0x00000000)

That shows that the MARSHAL exception came from Visibroker. Is it
possible to turn any tracing on on Visibroker to see why it was
unhappy?

Try to get a trace of Visibroker talking to itself. If Visibroker
doesn't have an option like -ORBtraceLevel 40 in omniORB, try using
Ethereal (www.ethereal.com) to snoop the packets.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --