This exception is raised if the FactoryFinder or the CORBAservices Naming
Service encounter an internal error during the search, with the error being
written to the user log (ULOG).
The FactoryFinder or
CORBAservices Naming Service encountered an internal error during the search,
with the error being written to the user log (ULOG).
The Current interface defines methods that allow a client of the
Transaction Service to explicitly manage the association between threads
and transactions.
When the deactivate_object() method is invoked with this reason code,
the transaction is marked for rollback only.This reason code is used
only for objects that have the transaction activation policy.
This member function instructs the FactoryFinder to return one application
factory object reference whose id in the key matches the method's input
factory_id.
If the client is associated with a transaction, a Control object is returned that represents the
transaction context currently associated with the client thread.
If there is a transaction associated with the client thread, this method returns a printable string
describing the transaction (specifically the XID as specified by the Open
Group).
A request raises this exception to report that a heuristic decision was
made, the disposition of all relevant updates is not known, and for those
updates whose disposition is known, either all have been committed or all
have been rolled back.
A request raises this exception to report that a heuristic decision was
made and that some relevant updates have been committed and others have
been rolled back.
Allows the application to perform application-specific initialization
procedures, such as logging into a database, creating and registering
well-known object factories, initializing global variables, and so forth.
This exception is raised for the Current interface commit, rollback, and
rollback_only methods if there is no transaction associated with the
client thread.
Allows the application to perform any application-specific cleanup, such as logging off a database, unregistering
well-known factories, or deallocating resources.
Acquires CORBA object references for the FactoryFinder, SecurityCurrent,
TransactionCurrent, NotificationService, Tobj_SimpleEventsService,
and InterfaceRepository objects.
If the parameter is a valid object reference in the current execution environment, the client thread
becomes associated with that transaction (in place of any previous transaction).
The authentication failed, or the client was already authenticated and did not
invoke com.beasys.Tobj.PrincipalAuthenticator.logoff() or
com.beasys.Tobj_Bootstrap.destroy_current().
This method modifies a state variable associated with the target object
that affects the time-out period associated with transactions created by
subsequent invocations of the begin method.
This exception is raised for the Current interface begin method if the
client already has an associated transaction and the Transaction Service
implementation does not support nested transactions.
If in a proper context with a transaction not marked ROLLEDBACK, an object is
returned that represents the transaction context currently associated with
the client thread.
The TransactionCurrent interface supports all the methods of the Current interface in the
CosTransactions module, as described in the previous section.
The execution of the com.beasys.Tobj.TP.create_object_reference method
has failed because
an unknown interface ID is specified in the request for an object.