[omniORB] stuck with message size in Python

[Joost van Lawick]

Hello,

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)
omniORB: Client connection refcount = 0
omniORB: Client close connection to giop:tcp:192.100.100.243:51566
omniORB: throw COMM_FAILURE from omniObjRef.cc:751 (MAYBE,COMM_FAILURE_WaitingForReply)
Traceback (most recent call last):
  File "producer.py", line 28, in ?
    p.post(msg)
  File "producer.py", line 13, in post
    msgId = self.cmf.xmit("PRODUCER_JOOST", "CMF_BASE", smsg, 43, 5, len(smsg), "ERRORS")
  File "cmf_idl.py", line 234, in xmit
    return _omnipy.invoke(self, "xmit", _0_CMF.Dispatcher._d_xmit, args)
omniORB.CORBA.COMM_FAILURE: Minor: COMM_FAILURE_WaitingForReply, COMPLETED_MAYBE.
omniORB: omniRemoteIdentity deleted.
omniORB: ObjRef(IDL:CMF/Dispatcher:1.0) -- deleted.

-----------------

I have tried all sorts of things, even raised chunk size in giopStream.cc, which
is ok but that does not realy solve the problem.

Cheers,


Joost van Lawick

-- 
When I was a boy I was told that anybody could become President.  Now
I'm beginning to believe it.
		-- Clarence Darrow

--
Joost van Lawick van Pabst
E: joost@lawick.nl
W: http://www.lawick.nl/