[omniORB] omniORB 3.0.5 crash with ZCF

[Christian Reis]

On Fri, Jun 28, 2002 at 03:56:45PM -0300, Christian Reis wrote:
> 
> Hello there,
> 
> I'm testing out omniORB 3.0.5 and omniORBpy 1.5 on a local, custom-built
> glibc2.1 box with python2.1.1. At the moment, I'm trying to look at ZCF,
> a set of class wrappers for the ZEO server from Zope, John Heintz's
> creation available from
> http://www.zope.org/Members/jheintz/ZODB_CORBA_Connection/ZCF-0_6.zip/view
> 
> I've got a strange issue. When I run the server and try to contact it
> through the client, it crashes with a SEGV. I've pulled a stack track
> and it isn't very suggestive, but I can attach it if it seems needed.
> 
> Has anybody had crashes with these versions when homebuilt? It might be
> something know, which is why i'm not posting traces and debugging yet.

Hmmm. Okay, this is the case:

omniORB: Assertion failed.  This indicates a bug in the application
using omniORB, or maybe in omniORB itself. e.g. using the ORB after it
has been shut down.
 file: omni30/pyServant.cc
 line: 1321
 info: 0

Which reads:

static
omniPy::Py_omniServant*
newSpecialServant(PyObject* pyservant, PyObject* opdict, char* repoId)
{
  if (!strcmp(repoId, PortableServer::ServantActivator::_PD_repoId))
    return new Py_ServantActivator(pyservant, opdict, repoId);

  if (!strcmp(repoId, PortableServer::ServantLocator::_PD_repoId))
    return new Py_ServantLocator(pyservant, opdict, repoId);

  if (!strcmp(repoId, PortableServer::AdapterActivator::_PD_repoId))
    return new Py_AdapterActivator(pyservant, opdict, repoId);

  OMNIORB_ASSERT(0);
  return 0;
}

Any idea why the repository id isn't matching the expected ones? John?

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL