| Summary: | Locking ORBInitializer Registry is done on multiple places with different locks | ||
|---|---|---|---|
| Product: | TAO | Reporter: | Johnny Willemsen <jwillemsen> |
| Component: | ORB | Assignee: | DOC Center Support List (internal) <tao-support> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | ||
| Priority: | P1 | ||
| Version: | 1.5.9 | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 2994 | ||
| Bug Blocks: | |||
invalid, not the registry is locked |
We can obtain the ORBInitializer registry throug the ORB or through PortableInterceptor::register_orb_initializer. When going through the ORB the orb lock is hold during the loading of the PI library, when going through the register_orb_initializer the static object lock is hold. This could lead to a double load, the ORB should also do a double checked locking on the static lock to my idea. Any other ideas? In the ORB: ACE_GUARD_RETURN (TAO_SYNCH_MUTEX, mon, this->lock_, 0); In PI: ACE_MT (ACE_GUARD (TAO_SYNCH_RECURSIVE_MUTEX, guard, *ACE_Static_Object_Lock::instance ()));