Оценок - 0, средний балл: 0
(
)
)
|
К этому устройству также есть другие инструкции:
Компьютеры - HP Integrity NonStop H-Series (16.73 mb)
Компьютеры - HP Integrity NonStop H-Series (957.56 kb)
Компьютеры - HP Integrity NonStop H-Series (881.66 kb)
Компьютеры - HP Integrity NonStop H-Series (965.62 kb)
Компьютеры - HP Integrity NonStop H-Series (676.93 kb)
Компьютеры - HP Integrity NonStop H-Series (393.72 kb)
Компьютеры - HP Integrity NonStop H-Series (776.57 kb)
Фрагмент инструкции
required in order to process a request, but one is not available. This scenario occurs when the POA has the policies RETAIN and
USE_SERVANT_MANAGER and a request comes into this POA but there is no existing servant to handle it. In this case, a servant manager
is required; it must set up beforehand by a call to set_servant_manager( ).
603 - 1314062939 - MINOR_NO_SERVANT_LOCATOR
This minor code occurs in the context of an OBJ_ADAPTER system exception. This minor code is similar to the
MINOR_NO_SERVANT_ACTIVATOR minor code detailed above for NON_RETAIN POAs. An incoming request requires a servant locator in
order to find a servant but one has not been set. One difference is that this minor code will be generated for every request since, for a
NON_RETAIN POA with the USE_SERVANT_MANAGER policy, the servant locator is required to service any request.
604 - 1314062940 - MINOR_NOT_IN_AOM
This minor code occurs in the context of an OBJECT_NOT_EXIST system exception. It indicates that an incoming request could not find a
servant in the POA's active object map. This implies that the POA has policies of RETAIN and USE_ACTIVE_OBJECT_MAP_ONLY.
605 - 1314062941 - MINOR_NO_ADAPTER
This minor code occurs in the context of an OBJECT_NOT_EXIST system exception. It indicates that the POA named in the incoming
request could not be located. (POAs are also referred to more generically as object adapters). This code can also be generated in the
context of an OBJ_ADAPTER system exception. In this case, it indicates that a local request could not find its associated POA. This
happens when a reference to a servant is locally generated and the POA is subsequently destroyed (and can't be automatically re-
created).
606 - 1314062942 - MINOR_WRONG_STATE
This minor code occurs in the context of either a TRANSIENT or OBJ_ADAPTER system exception. In either case, the minor code indicates
that the POA manager is not in the correct state (it is not active) in order to process a request. A TRANSIENT exception is generated
when the 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 the client sending the request is a not a NonStop CORBA
ORB and the client is trying to invoke a method on a CORBA object that NonStop CORBA currently does not support. Turn POA tracing
on (environment variable NSDOM_CFG_TRACE_POA) to see the name of the operation that is having a problem
613 - 1314062949 - MINOR_POA_DESTROYED
This minor code occurs in the context of an OBJECT_NOT_EXIST system exception. If this occurs in response to any call on a POA, it
indicates that the POA upon which the call was made has been destroyed. The application should release the POA reference.
Subsequent operations on that POA are illegal; continuing operations are still possible within the application by re-creating a new POA
with the same properties as the one that was destroyed (that is, same name, same policies, same parent).
614 - 1314062950 - MINOR_BAD_VALUE
...Эта инструкция также подходит к моделям:
Компьютеры - HP Integrity NonStop J-Series (210.34 kb)