3.7.3.12.4 Exceptions

The following exceptions can be raised by the register_factory() method:

TobjS::CannotProceed

Indicates that the FactoryFinder encountered an internal error during the search, with the error being written to the user log (ULOG). Notify the operations staff immediately if this exception is raised. Depending on the severity of the internal error, the server running the FactoryFinder or the NameManager may have terminated. If a FactoryFinder service has terminated, start a new FactoryFinder service. If the NameManager has terminated, and there is another NameManager running, start a new one. If no NameManagers are running, restart the application.

TobjS::InvalidName

Indicates that the id string is empty. It is also raised if the field contains blank spaces or control characters.

TobjS::InvalidObject

Indicates that the factory value is nil.

TobjS::RegistrarNotAvailable

Indicates that the FactoryFinder object cannot locate the NameManager. Notify the operations staff immediately if this exception is raised. If no naming services servers are running, restart the application.

Note:

Another possible reason that this exception might occur is that the FactoryFinder cannot participate in a transaction. Therefore, you may need to suspend the current transaction before issuing the TP::register_factory() and TP::unregister_factory() calls. For information on suspending and resuming transactions, see Using CORBA Transactions in the online documentation.

TobjS::OverFlow

Indicates that the id string is longer than 128 bytes (currently the maximum allowable length).