[omniORB] stuck with python string size
John, Gareth (Poole)
gareth.john@siemens.com
Fri Jan 31 11:01:01 2003
Hi,
I may have been tracing a similar OmniORB/Visibroker problem but setting the
maximum GIOP version to1.0 seems to work ok. Does this mean there is a
problem with the implementation of V1.2 ?
The symptoms were (OmniORB 4 on Win2K)
OmniORB sends data using send(socket, buf, len, flags); and large data are
sent in multiples of 8k buffers. The Visibroker client works ok when
receiving one buffer but gets an exception on the second. Tracing the
OmniORB source shows the return value from the call to send() returns the
number of bytes sent, which is always correct. However, the correct
operation of the send() does not mean the data was delivered correctly, as
in our case.
-----Original Message-----
From: Duncan Grisby [mailto:duncan@grisby.org]
Sent: Thursday 30 January 2003 11:07 AM
To: Joost van Lawick
Cc: omniorb-list@omniorb-support.com
Subject: Re: [omniORB] stuck with python string size
On Tuesday 28 January, Joost van Lawick wrote:
> I use omniOrb and Python to connect to a Visibroker orb. I have
> compiled the latest omniOrb and omniOrbpy from CVS on a (suse) linux
> box. I have added --enable-threads and --disable-static to both
> configure scripts. I can connect send and receive python strings but
> only of size < 1024 chars.
>
> When I send a message (size >= 1024 chars) I get the following message:
>
> -----------------
> omniORB: Client opened connection to giop:tcp:192.100.100.243:51566
> omniORB: sendChunk: to giop:tcp:192.100.100.243:51566 112 bytes
> omniORB: sendCopyChunk: to giop:tcp:192.100.100.243:51566 10288 bytes
> omniORB: sendChunk: to giop:tcp:192.100.100.243:51566 43 bytes
> omniORB: throw giopStream::CommFailure from
giopStream.cc:816(0,MAYBE,COMM_FAILURE_WaitingForReply)
It looks like perhaps Visibroker doesn't support the fragmented
messages that omniORB is sending. If that is the case, it's broken.
To find out, you could try setting omniORB's maximum GIOP version to
1.0 with -ORBmaxGIOPVersion 1.0 .
If that doesn't help, is there any tracing you can turn on in
Visibroker?
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan@grisby.org --
-- http://www.grisby.org --
_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
Siemens Plc
Registered office: Siemens House, Oldbury, Bracknell, Berkshire, RG12 8FZ.
Registered no: 727817, England.
This communication contains information which is confidential and
may also be privileged. It is for the exclusive use of the addressee.
If you are not the addressee please note that any distribution,
reproduction, copying, publication or use of this communication
or the information in it is prohibited. If you have received this
communication in error, please contact us immediately and also
delete the communication from your computer.