[omniORB] wstring corruption, omniOrb -> Orbacus

[brk@jenkon.com]

Thanks, Ken, that helps. I'm also having a different problem now with
Visibroker for Java 4.5. I can connect fine, narrow to the correct
interface, but when I call a method (any method), I get something like the
stuff below. There must be something I'm doing wrong here, this many ORBs
can't all be screwy. Anyone?

omniORB: LocateRequest to remote:
key<0x00564201000000022f0020200000000b42616e6b
4d616e6167657220000001d9178c6e71>
omniORB: Python thread state scavenger start.
omniORB: AsyncInvoker: thread id = 2 has started. Total threads = 1
omniORB: Client opened connection to giop:tcp:209.210.37.31:4504
omniORB: sendChunk: to giop:tcp:209.210.37.31:4504 60 bytes
4749 4f50 0102 0103 3000 0000 0200 0000 GIOP....0.......
0000 6e64 2400 0000 0056 4201 0000 0002 ..nd$....VB.....
2f00 2020 0000 000b 4261 6e6b 4d61 6e61 /.  ....BankMana
6765 7220 0000 01d9 178c 6e71           ger ......nq
omniORB: inputMessage: from giop:tcp:209.210.37.31:4504 24 bytes
4749 4f50 0102 0104 0c00 0000 0200 0000 GIOP............
0100 0000 0000 0000                     ........
omniORB: Garbage left at the end of input message from
giop:tcp:209.210.37.31:45
04
omniORB: From endpoint: giop:tcp:209.210.37.31:4504. Detected GIOP 1.2
protocol
error in input message. Connection is closed.
omniORB: throw giopStream::CommFailure from
giopImpl12.cc:1208(0,YES,COMM_FAILUR
E_UnMarshalResults)
omniORB: Client connection refcount = 0
omniORB: Client close connection to giop:tcp:209.210.37.31:4504
Traceback (most recent call last):
  File "py_client.py", line 25, in ?
    print calc.news("hello there")
  File "Bank_idl.py", line 97, in news
    return _omnipy.invoke(self, "news", _0_Bank.AccountManager._d_news,
args)
omniORB.CORBA.COMM_FAILURE: Minor: COMM_FAILURE_UnMarshalResults,
COMPLETED_YES.
> -----Original Message-----
> From:	Ken Feuerman [SMTP:kfeuerma@adobe.com]
> Sent:	Thursday, March 14, 2002 3:31 PM
> To:	brk@jenkon.com
> Cc:	omniorb-list@uk.research.att.com
> Subject:	Re: [omniORB] wstring corruption, omniOrb -> Orbacus
> 
> As one data point, we have omniORB4 working with the JDK1.4 built-in ORB, 
> complete with wstring use.  Our system is just now coming together under 
> this configuration so we're still working out kinks, but at present none
> of 
> those kinks are wstring-related.
> 
> --Ken Feuerman.
> Adobe Systems, Inc.
> 
> 
> At 01:58 PM 3/14/2002 -0800, brk@jenkon.com wrote:
> >Working with the 12 Mar 2002 omniOrb4 snapshot and the latest Orbacus, if
> I
> >send a wstring from an omniOrb client to an orbacus server, by the time
> my
> >code receives the wstring on the server, it's been transformed to a
> string
> >of question marks. Here's a sample of the GIOP (same as for yesterday's
> >message about a similar problem with OpenOrb):
> >
> >omniORB: sendChunk: to giop:tcp:209.210.37.31:4121 116 bytes
> >4749 4f50 0102 0100 6800 0000 0600 0000 GIOP....h.......
> >0300 0000 0000 0000 2500 0000 abac ab31 ........%......1
> >3130 3136 3134 3232 3533 005f 526f 6f74 1016142253._Root
> >504f 4100 00ca feba be3c 9119 ae00 0000 POA......<......
> >0064 6c2e 0500 0000 6e65 7773 0000 0000 .dl.....news....
> >0000 0000 0c00 0000 1800 0000 fffe 4800 ..............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:4121 28 bytes
> >4749 4f50 0102 0001 0000 0010 0000 0006 GIOP............
> >0000 0000 0000 0000 4140 0000           ........A@..
> >
> >Does anyone know a solution? Is this just a configuration problem of some
> >kind? Is omniOrb known to work (with wstrings!!) with any Java ORB?
> >
> >Thanks,
> >
> >Bryn Keller
> >Senior Software Engineer
> >Jenkon
> >brk@jenkon.com