Tuxedo
0

Administering a Tuxedo Application at Run Time

 Previous Next Contents View as PDF  

PortableServer::POAManager::deactivate

Synopsis

Changes the state of the POA manager to inactive.

C++ Binding

void deactivate (
CORBA::Boolean etherealize_objects,
CORBA::Boolean wait_for_completion);

Argument

etherealize_objects

For BEA WebLogic Enterprise 4.2 software and later software and BEA Tuxedo 8.0 and later software, this argument should always be set to FALSE.

wait_for_completion

If this argument is TRUE, the deactivate operation returns only after all requests in process have completed. If this argument is FALSE, the deactivate operation returns after changing the state of the associated POAs.

Exceptions

If issued while the POA manager is in the inactive state, the PortableServer::POAManager::AdapterInactive exception is raised.

Description

This operation changes the state of the POAManager to inactive. Entering the inactive state causes the associated POAs to reject requests that have not begun to be executed, as well as any new requests.

Note: This release of BEA Tuxedo does not support multithreading. Hence, wait_for_completion should not be TRUE if the call is made in the context of an object invocation. That is, the POAManager cannot be set to inactive state if it is currently executing.

Note: This function is supported only for a joint client/server.

Return Values

None.

 


POA Policy Member Objects

Interfaces derived from CORBA::Policy are used with the POA::create_POA operation to specify policies that apply to a POA. Policy objects are created using factory operations on any preexisting POA, such as the root POA. Policy objects are specified when a POA is created. Policies may not be changed on an existing POA. Policies are not inherited from the parent POA.

 

Back to Top Previous Next
Contact e-docsContact BEAwebmasterprivacy