Re: [Orbit-python-list] Do activate_object_with_id and -ORBIPv4Port really work?
Status: Inactive
Brought to you by:
tack
From: <ml...@kn...> - 2002-01-31 21:25:15
|
On Thu, Jan 31, 2002 at 06:30:15PM -0200, Christian Robottom Reis wrote: > On Thu, 31 Jan 2002, ml wrote: > > > > I hacked 0.3.1 to fix this, but it could be that the parameter is not > > > being passed along. I'm not sure if that's your problem. What happens if > > > you don't pass those in? > > > > The first two arguments do have the expected effect, the > > third not. > > It could be an orbit bug; can you try and bring it up with them? > > We may not be passing in the parameter, but I find that very hard to > believe if the others do and we don't manipulate them. Changing order does > nothing, I assume? It seems to be either a problem with (C-)Orbit or with my understanding of it. I compiled the echo-server.c from the orbit-0.5.13 test suite and ran it as follows: ./echo-server -ORBIPv4Port=7777 -ORBIIOPIPv4=1 -ORBIIOPUSock=0 Neither is the object id "myEchoString" as it should, because PortableServer_POA_activate_object_with_id() has been called nor is the open port 7777, but 1166 or so. The ior-decode utility and a check using netstat -an shows this clearly. IP and not UNIX sockets is used, at least. Cheers! |