CORBA 2.6.1 Programmer's Reference

actual state is Discarding; otherwise, the OBJ_ADAPTER exception is raised, typically because the
state is Inactive. (If the state were Holding, an exception would not be raised; instead, the request
would be delayed (held) until the POA manager was requested to change to another state.
607 - 1314062943 - MINOR_WRONG_PROCESS
This minor code occurs in the context of an INV_OBJECT system exception. It indicates that a
request was delivered to a server, but the IOR indicates a different server. This can be caused by a
corrupt IOR. If generated in response to a local request (that is, where a client and server are in the
same process) this would indicate an internal error in the NonStop CORBA runtime software, and
details should be reported to your service provider.
608 - 1314062944 - MINOR_WRONG_POLICY
This minor code occurs in the context of either an OBJECT_NOT_EXIST or OBJ_ADAPTER
system exception. In the case of OBJECT_NOT_EXIST, it indicates a corrupt or stale IOR; a
client request indicates a POA, which does exist, however, the POA's current policy does not
match that given in the IOR. This is not legal. The OBJECT_NOT_EXIST exception is returned,
indicating the object previously referred to by the old IOR is gone. For an OBJ_ADAPTER,
exception this indicates that the POA was asked to create an object reference (for example, by
calling create_reference_with_id( ), and the POA has a PERSISTENT value for the
Lifespan policy, but no ORB profile was set for the server process. To remedy this, re-run the
server giving a correct -ORBprofile value command.
609 - 1314062945 - MINOR_NO_OBJECT_ID
This minor code occurs in the context of an OBJECT_NOT_EXIST system exception. This minor
code is generated when a local request is made using an uninitialized object. A proper object
reference will always have an object id and the MINOR_NO_OBJECT_ID code indicates that one
was not present. Make sure that your application obtained the object reference properly.
610 - 1314062946 - MINOR_NO_DEFAULT_SERVANT
This minor code occurs in the context of an OBJ_ADAPTER system exception. It indicates that a
request arrived which required a default servant to be present but no default servant was set. The
POA has the USE_DEFAULT_SERVANT value for the RequestProcessing policy and a
servant was not found for the request.
611 - 1314062947 - MINOR_NONE_GIVEN
This minor code occurs in the context of an OBJECT_NOT_EXIST system exception. This minor
code indicates that a servant manager was called but the manager returned NULL and no exception;
the locator did not return a servant. This may be considered an application error since the servant
manager is supposed to return an exception indicating the specific cause for not finding a servant.
612 - 1314062948 - MINOR_NO_SUCH_OPERATION
This minor code occurs in the context of a BAD_OPERATION system exception. It indicates that
during the process of servicing a request, the operation name present in the request was not among
those handled by the servant. This indicates, typically, that the type of the servant handling the
request does not match that of the client's target object. This is illegal. This might happen if an
application servant manager returned an incorrect servant for a request. This might also happen if