[omniORB] Py_ServantLocator Core Dump

[Gary Pennington]

Hi,

I am using Solaris 8, gcc 2.95.2, omniOrbpy1.1 as distributed from the
omniOrbpy website.

I have some code which implements the Evictor pattern using Servant
Locators (lifted from Henning/Vinoski and adapted to Python). The
application is multi-threaded and I am using multiple POA and
POAManagers to try and optimize throughput on SMP boxes.

When the system is under heavy load, i.e. load testing, I get a core
dump in the server process. The core indicates that the problem arises
in :-

-----------------  lwp# 12 / thread# 162  --------------------
 ff0afa5c
__0fRPy_ServantLocatorKpostinvokeRC65OPortableServerIObjectIdP65OPorta
bleServerDPOAPCcPvP65OPortableServerLServantBase (36a930, fe00fa3c,
33fbe0, fe00
fbe4, a087c, 4ba610) + 40
 fe757344
__0fKomniOrbPOAIdispatchR6SomniCallDescriptorP6RomniLocalIdentity (1,
32d470, fe00f90c, fe7c3df0, 36d188, 164d90) + 1ec
 fe74cf10 __0fRomniLocalIdentityIdispatchR6SomniCallDescriptor (36d188,
fe00f90c
, fe7c3df0, b, 0, ff0e5020) + 9c
 fe74b9a8 __0fKomniObjRefH_invokeR6SomniCallDescriptorUc (348a5c, 1, 1,
fe7c3df0
, fe00f90c, 0) + ac
 fe766500
__0f5OPortableServerW_objref_ServantLocatorKpostinvokeRC65OPortableSer
verIObjectIdP65OPortableServerDPOAPCcPvP65OPortableServerLServantBase
(348a48, f
e00fa3c, 33fbe0, fe00fbe4, a087c, 4ba610) + 70
 fe75ab88
__0fKomniOrbPOAPcall_postinvokeP65OPortableServerW_objref_ServantLocat
orR65OPortableServerIObjectIdPCcPvP65OPortableServerLServantBase
(33fbe0, 348a48
, fe00fa3c, fe00fbe4, a087c, 4ba610) + 40
 fe75aab0 __0fKomniOrbPOAOdispatch_to_slR6GGIOP_SPCUci (33fbe0, 5,
348a48, fe7ca
030, fe7c3df0, 4ba610) + 304
 fe77e800 __0fGGIOP_SNHandleRequestUc (fe00fb98, fe7cc284, c747f2b8,
ff0000, ff0
00000, ff00) + 6b4
 fe77dda8 __0fGGIOP_SKdispatcherP6GStrandT (4fa7f0, fe7c3df0, ff1e5a8c,
ff270400
, 10, 1ce2c1) + 174
 fe79e050 __0fPtcpSocketWorkerI_realRunPvT (4fa7f0, fe7c3df0, 4fa7f0,
fe7c3df0,
4bb248, 0) + 64
 ff0726ec omni_thread_wrapper (4bb248, 0, 0, 5, 1, fe400000) + c4
 ff25bc08 _thread_start (4bb248, 0, 0, 0, 0, 0) + 40

I am going to investigate this further, but I thought that it would be
wise to see if anyone else has seen a problem similiar to this or has
any insight as to what the problem might be.

Gary