Re: ORBit errors when reconnecting.

[Michael Meeks <michael ximian com>]

Hi Craig,

On Wed, 2003-02-19 at 07:33, Craig Wright wrote:
> I'm using orbit-0.5.15 for connecting two processes written in
> C++.

	I would upgrade to ORBit2 - and use the 'orbitcpp' C++ bindings in CVS
- personally :-)

> On the server:
> 
> ORBit-CRITICAL **: file orbit_object.c: line 530 (ORBit_marshal_object): 
> assertion `ORBIT_ROOT_OBJECT(obj)->refs > 0' failed.

	That means that you have (somehow) CORBA_Object_released' the object
you're trying to marshal - which is really bad news. Are you sure you
own the reference to that ? Either that - or you're not passing (or
returning) a valid object reference into a method - but something else.
You sure you're not trying to return a servant as an object ?

	What does compiling with -Wall tell you about your code ?

> On the client:
> 
> ORBit-Message: demarshal_profile(): IIOP major is 0
> ORBit-Message: demarshal_profile(): IIOP major is 0
> ORBit-Message: demarshal_profile(): IIOP major is 0
> ORBit-Message: demarshal_profile(): IIOP major is 0
> ORBit-Message: demarshal_profile(): IIOP major is 0
> ORBit-Message: demarshal_profile(): IIOP major is 0
> Segmentation fault

	That's bad in and of itself; but not that interesting - it got corrupt
data. A crash in ORBit2 would be serious since it's designed to handle
corrupt data; ORBit1 is emphatically not ;-)

	HTH,

		Michael.

-- 
 mmeeks@gnu.org  <><, Pseudo Engineer, itinerant idiot