14.13.9.4 Description

This operation destroys the POA and all descendant POAs. The POA with its name may be recreated later in the same process. (This differs from the POAManager::deactivate operation, which does not allow a recreation of its associated POA in the same process.)

When a POA is destroyed, any requests that have started execution continue to completion. Any requests that have not started execution are processed as if they were newly arrived and there is no POA; that is, they are rejected and the OBJECT_NON_EXIST exception is raised.

If the wait_for_completion parameter is TRUE, the destroy operation returns only after all requests in process have completed and all invocations of etherealize have completed. Otherwise, the destroy operation returns after destroying the POAs.

Note:

This release of Oracle Tuxedo does not support multithreading. Hence, wait_for_completion must not be TRUE if the call is made in the context of an object invocation. That is, the POA cannot start destroying itself if it is currently executing.

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