[omniORB] 4.0.7: reference to servant becomming nil after some time

Duncan Grisby duncan at grisby.org
Fri Dec 21 10:26:56 GMT 2007


On Thursday 6 December, "Igor Lautar" wrote:

> Is it possible that an existing reference (_narrowed to valid ITF)
> becomes nil?

No. omniORB will definitely never change an object reference to be nil.

> Either by changing network configuration (IPs etc.) or something else.
> Is it at all possible that this occurs, excluding omniORB bugs (is such
> a bug in 4.0.7?)?
> 
> Our code is roughly the following (pseudo):
>  1) string_to_object
>  2) _narrow to itf
>  3) check nil
>  4) use
> 
> It once (only once) happened that after some time (observed after 2
> weeks of client uptime) of running, reference became nil. It couldn't be
> nil at the start as there is a check for it.
> 
> It could also be some memory corruption (writing where we shouldn't).

It is almost certainly either memory corruption, or that you have
released the object reference too many times so it is no longer valid.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --



More information about the omniORB-list mailing list