Bug 182 - servant_deactivation_condition and active object map
Summary: servant_deactivation_condition and active object map
Status: NEW
Alias: None
Product: TAO
Classification: Unclassified
Component: POA (show other bugs)
Version: 1.0
Hardware: All All
: P2 normal
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 1999-07-30 03:51 CDT by Irfan Pyarali
Modified: 2007-05-01 06:46 CDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Irfan Pyarali 1999-07-30 03:51:01 CDT 
<servant_deactivation_condition> is used for waiting for partially deactivated
servants to complete their deactivation before the POA is allowed to reactivate
them.  Currently, TAO_POA::is_servant_in_map() and TAO_POA::is_user_id_in_map()
use this condition variable. However, there are some other instances of partial
deactivation that we need to find and cover.
Comment 1 Irfan Pyarali 1999-07-30 04:10:59 CDT 
Yep, mine again.
Comment 2 Johnny Willemsen 2004-11-01 06:19:58 CST 
Does have anyone more info about this? I am currently refactoring the POA and 
am interested in any open issues here.
Comment 3 Irfan Pyarali 2004-11-01 12:04:04 CST 
The following methods are relevant:

create_reference_with_id_i() - A new entry maybe created in this
function, but the existence of a partially deactivated user id in the
AOM is not verfied.

servant_to_id_i() and servant_to_system_id_i() - A new entry maybe
created in these functions, but the existence of a partially
deactivated servant in the AOM is not verfied.
Comment 4 Johnny Willemsen 2007-05-01 06:46:11 CDT 
to pool