[omniORB] omniORB assertion failure in omniOrbPoa::lastInvocationHasCompleted

[Duncan Grisby]

On Monday 14 July, Chris Newbold wrote:

> During a recent stress test of our application, we hit the following
> assertion in omniORB (version 4.0.1):

[...]
> Is there anyway this could be caused by an application-level error?
> Presumably the only thing that might provoke this is attempting to
> deactivate a bogus object, but I would have expected that to be caught
> sooner...

Was it during POA destruction, or normal running?  I recently fixed a
bug in destruction that might have caused that assertion to fail.

If it's during normal running, the most likely cause is memory
corruption, either by omniORB or your application. If possible, try
running under Purify or Valgrind or similar.

Either way, please update to the current CVS contents before trying to
track it down, in case changed things affect the behaviour.

Cheers,

Duncan.

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