C++ TP Framework Messages

C++ TP Framework (TPFW) Messages 1-127

Note: When C++ TP Framework messages are listed in the user log (ULOG), the messages have the prefix LIBTPFW_CAT. For example, message 1 is listed as LIBTPFW_CAT:1.

Note: Messages in the range 1-99 are errors or warnings raised because of user processing. The messages generally indicate a problem in application processing that should be directed to the programmer.

Note: Messages in the range 100 and higher are errors or warnings raised because of system processing.

1	"ERROR: Exception in Server::initialize(): exception id. Reason = reason."
	Description	Either application code raised an exception in Server::initialize() or application code did not catch an exception raised during processing in Server::initialize(). The exception id is printed with a reason. If the application raised TobjS::InitializeFailed and included a reason string, it is printed here. The server startup processing is halted.
	Action	Notify the programmer.

2	"WARN: Exception in Server::release():exception id. Reason = reason."
	Description	Either application code raised an exception in Server::release() or application code did not catch an exception raised during processing in Server::release(). The exception id is printed with a reason. If the application raised TobjS::ReleaseFailed and included a reason string, it is printed here. Server shutdown processing continues.
	Action	Notify the programmer.

3	"INFO: Default Server::initialize() used."
	Description	The programmer either did not implement Server::initialize(), or called ServerInternal::initialize() explicitly. The default initialization tries to open the default XA resource manager.
	Action	None

4	"INFO: Default Server::release() used."
	Description	The programmer did not implement Server::release(), or called ServerInternal::release() explicitly. The default release tries to close the default XA resource manager.
	Action	None

5	"WARN: TP::deactivateEnable() called in illegal context. Called in Server::initialize() or Server::release()."
	Description	The application called TP::deactivateEnable outside the context of a CORBA method invocation. This is an illegal call. Processing continues.
	Action	Notify the programmer. Call to TP::deactivateEnable should be removed from Server::initialize and/or Server::release.

6	"WARN: TP::deactivateEnable() called illegally - object has transaction activation policy."
	Description	The application called TP::deactivateEnable inside a CORBA method invocation on an object with the transaction activation policy. This is an illegal call. Processing continues.
	Action	Notify the programmer.

7	"ERROR: Invoking request - interface not advertised: interfaceName."
	Description	The object reference invoked by a client is for an interface that is unknown to the system. Possible reasons are: No server is available that can service the interface. The server may not have been started yet, or may have been shut down or abnormally terminated. The factory that created the object reference specified an invalid interface name. The interface name specified in the call to TP::create_object_reference must correspond exactly to the interface name specified in the OMG IDL file for the CORBA object. This interface name is usually the OMG interface repository ID.
	Action	Check the status of the interface. It may be suspended. If you cannot find the interface in the system, notify the programmer.

8	"WARN: Application didn't catch TobjS exception. TP Framework throwing CORBA::BAD_OPERATION."
	Description	The system caught an exception defined in the TobjS idl module after invoking a method of a CORBA object. This warning indicates that either: The application raised an exception defined in TobjS idl within the method invocation, which is not allowed because the exceptions defined in this module are for use by servers only and should not be returned to clients. The application did not handle an exception defined in TobjS.idl that was thrown by a system call. In either case, the system converts the exception to CORBA::BAD_OPERATION before returning the exception to the client.
	Action	Notify the programmer.

9	"WARN: Application called TP::deactivateEnable() illegally and didn't catch TobjS exception."
	Description	The system caught a TobjS::IllegalOperation exception after a method invocation. The possible reasons are: The application raised a TobjS::IllegalOperation exception, which is not allowed because this exception is reserved for use by the WLE software. The application called TP::deactivateEnable() illegally (most likely in an object with transaction activation policy) and did not handle the exception.
	Action	Notify the programmer.

11	"ERROR: Non-transactional invocation on CORBA object infected with a transaction."
	Description	An invocation was made without an active transaction on an object that is participating in a global transaction. This error can occur if a client sends a request to a CORBA object that is participating in a transaction started for another client. It can also occur if a call is made immediately after a transaction has been marked for rollback only. There is a small delay while the transaction-termination processing is completed by the transaction manager when the transaction is still active. This error is generally detected in a for loop that invokes the same object repeatedly for different transactions.
	Action	If many such messages are seen, notify the programmer. If loop processing is being done, sleep() for a short time between invocations.

12	"ERROR: Invalid gtrid when invoking {active|inactive}{transaction|method|process} - bound CORBA object infected with a transaction."
	Description	A client tried to invoke a CORBA object already infected by a transaction with a different transaction ID than the one it was originally processing. This error can occur if a client sends a request to a CORBA object that is participating in a transaction started for another client. It can also occur if a call is made immediately after a transaction has been marked for rollback only. There is a small delay while the transaction termination processing is completed by the transaction manager when the transaction is still active. This error is generally detected in a for loop that invokes the same object repeatedly for different transactions.
	Action	If many such messages are seen, notify the programmer. If loop processing is being done, sleep() for a short time between invocations.

21	"ERROR: Illegal recursive call on CORBA Object. Interface = interfaceName, OID = object ID."
	Description	A recursive call was made on a CORBA object. This error occurs if, for example, a client calls object A, which calls object B, which uses an object reference to object A to invoke a method of object A. The second call to object A causes this error message to be printed to the user log and a CORBA::OBJ_ADAPTER exception to be returned to the calling client (in this case, object B).
	Action	Notify the programmer.

22	"ERROR: Activating object - application raised TobjS::OutOfMemory. Interface = interfaceName, OID = object ID."
	Description	The system caught TobjS::OutOfMemory raised by either Server::create_servant or Tobj_ServantBase::activate_object. This error may have occurred because the application did not catch this exception when it was thrown either by a WLE system call or by application code.
	Action	This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

23	"ERROR: Activating object - application raised TobjS::CreateServantFailed. Reason = reason. Interface = interfaceName, OID = object ID."
	Description	The application raised TobjS:CreateServantFailed with the reason string supplied.
	Action	Application dependent. Notify your company's technical support or the application programmer.

24	"ERROR: Activating object - application raised TobjS::ActivateObjectFailed. Reason = servicename. Interface = interfaceName, OID = object ID."
	Description	The system caught TobjS::ActivateObjectFailed raised by either Server::create_servant or Tobj_ServantBase::activate_object. The application raised TobjS::ActivateObjectFailed with the reason string supplied.
	Action	Application dependent. Notify your company's technical support or the application programmer.

25	"ERROR: Activating object - CORBA Exception not handled by application. Exception ID = exception ID. Interface = InterfaceName, OID = object ID."
	Description	The system caught a CORBA exception raised by either Server::create_servant or Tobj_ServantBase::activate_object.
	Action	Application dependent. Notify your company's technical support or the application programmer.

26	"ERROR: Activating object - Unknown exception not handled by application Interface = InterfaceName, OID = object ID. "
	Description	The system caught an unknown exception raised by either Server::create_servant or Tobj_ServantBase::activate_object.
	Action	Application dependent. Notify your company's technical support or the application programmer.

27	"ERROR: De-activating object - application raised TobjS::DeactivateObjectFailed. Reason = reason Interface = interfaceName, OID = object ID."
	Description	The system caught a TobjS::DeactivateObjectFailed exception raised in Tobj_ServantBase::deactivate_object.
	Action	Application dependent. Notify your company's technical support or the application programmer.

28	"ERROR: De-activating object - CORBA Exception not handled by application. Exception ID = exception ID. Interface = InterfaceName, OID = object ID."
	Description	The system caught a CORBA exception raised in Tobj_ServantBase::deactivate_object.
	Action	Application dependent. Notify your company's technical support or the application programmer.

29	"ERROR: De-activating object - Unknown exception not handled by application Interface = InterfaceName, OID = object ID."
	Description	The system caught an unknown exception raised in Tobj_ServantBase::deactivate_object.
	Action	Application dependent. Notify your company's technical support or the application programmer.

100	"ERROR: Couldn't open XA resource manager in default Server::initialize(). tperrno = internalcode."
	Description	The default implementation of Server::initialize() failed to open the default XA resource manager for the server group. The tperrno function specifies the error returned.
	Action	Verify configuration of openinfo for the associated resource manager. Consult error codes described for tx_open(3).
	See Also	tx_open(3).

101	"ERROR: Couldn't close XA resource manager in default Server::release(). tperrno = internalcode."
	Description	The default implementation of Server::release() failed to close the default XA resource manager for the server group. The tperrno function specifies the error returned.
	Action	Consult error codes described for tx_close(3).
	See Also	tx_close(3).

102	"ERROR: TP::create_object_reference() couldn't create object reference for: Interface = servicename OID = servicename."
	Description	An internal exception was raised when an object reference for the specified interface and object ID was created.
	Action	Contact BEA Technical Support.

103	"ERROR: TP::[register | unregister]_factory() couldn't register factory. Registrar service not available. Check status of FactoryFinder server(s)."
	Description	The register or unregister factory operation failed because the FactoryFinder server or an associated server was not available.
	Action	Verify that the FactoryFinder and all associated servers are available.
	See Also	Administration Guide online document.

104	"ERROR: TP::servicename_factory() cannot proceed due to unexpected problem with Registrar. Check status of FactoryFinder server(s)."
	Description	An internal exception was raised when a factory was being registered or unregistered.
	Action	Verify that the FactoryFinder and all associated servers are available.
	See Also	Administration Guide online document.

106	"ERROR: Invoking request - couldn't get: resource."
	Description	An internal problem was encountered when the specified resource was being retrieved.
	Action	Contact BEA Technical Support.

107	"ERROR: Invoking request - no context."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

108	"ERROR: Invoking request - unexpected exception."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

109	"ERROR: After invoking request - couldn't get: resource. "
	Description	An internal problem was encountered when the specified resource was being retrieved.
	Action	Contact BEA Technical Support.

110	"ERROR: After invoking request - no context."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

111	"ERROR: After invoking request - interface not advertised: interfaceName."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

112	"ERROR: After invoking request - unexpected exception."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

113	"ERROR: Activating object - out of memory. Interface = interfaceName, OID = Object ID."
	Description	The system could not obtain sufficient memory to activate the specified object.
	Action	This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

116	"ERROR: Activating object - Internal map error. Interface = servicename, OID = servicename."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

118	"ERROR: No local gtrid or local gtrid doesn't match global gtrid."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

119	"ERROR: Invoking process-bound object - transaction table inconsistency."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

120	"ERROR: Invalid activation policy."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

121	"ERROR: Couldn't set tran sync."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

122	"ERROR: Couldn't set gtrid."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

123	"ERROR: Couldn't set deref."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

124	"ERROR: Couldn't set tran sync ..."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

125	"ERROR: Couldn't set gtrid ..."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

126	"ERROR: Couldn't set deref ..."
	Description	An internal problem was encountered.
	Action	Contact BEA Technical Support.

127	"ERROR: Context stack out of memory. System throws TobjS::OutOfMemory exception."
	Description	The system could not obtain sufficient memory to manage an internal stack.
	Action	This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

178	"WARN: TP::create_active_object_reference() called illegally - object does not have process activation policy."
	Description	TP::create_active_object_reference was called on an interface that does not have process activation policy.
	Action	Change the interface to have process activation policy.

179	"WARN: TP::deactivateEnable() called illegally - object does not have process activation policy."
	Description	TP::deactivateEnable was called on an object that does not have process activation policy.
	Action	Change the interface of the object to have process activation policy.

180	"ERROR: TP::create_object_reference() couldn't create object reference for: Interface = %s OID = %.256s"
	Description	An exception occurred while calling TP::create_object_reference. The object reference could not be created.
	Action	Check the user log for messages indicating the nature of the failure. Contact BEA Technical Support.