Java TP Framework Messages

Java TP Framework Messages 1-66

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

1	"ERROR: Missing ORB argument to Tobj_Bootstrap"
	Description	An attempt to create the Tobj_Bootstrap object failed because the orb argument passed to the Tobj_Bootstrap constructor was empty.
	Action	Make sure that the orb argument that was passed to the Tobj_Bootstrap constructor is not empty.

2	"ERROR: Cannot find class {0}"
	Description	An attempt to create the Tobj_Bootstrap object failed because the class name in {0} could not be found.
	Action	Make sure that the corresponding WLE Java .jar file is included in the class path.

3	"ERROR: Cannot instantiate delegate bootstrap"
	Description	An attempt to create the Tobj_Bootstrap object failed while attempting to invoke its constructor.
	Action	Contact BEA Customer Support.

4	"ERROR: Cannot execute delegate bootstrap constructor"
	Description	An attempt to create the Tobj_Bootstrap object failed while attempting to execute its constructor.
	Action	Contact BEA Customer Support.

5	"ERROR: Cannot access delegate bootstrap constructor"
	Description	An attempt to create the Tobj_Bootstrap object failed while attempting to access its constructor.
	Action	Contact BEA Customer Support.

6	"ERROR: No cached reference to FactoryFinder found"
	Description	An attempt to call resolve_initial_references("FactoryFinder") failed because the Bootstrap object could not locate any cached references to the FactoryFinder object.
	Action	Contact BEA Customer Support.

7	"ERROR: No cached reference to InterfaceRepository found"
	Description	An attempt to call resolve_initial_references("InterfaceRepository") failed because the Bootstrap object could not locate any cached references to the InterfaceRepository object.
	Action	Contact BEA Customer Support.

8	"ERROR: Underlying ORB unable to resolve a reference to FactoryFinder "
	Description	An attempt to call resolve_initial_references("FactoryFinder") failed because the underlying ORB was unable to internally resolve a reference to the FactoryFinder object.
	Action	Contact BEA Customer Support.

9	"ERROR: Underlying ORB unable to resolve a reference to InterfaceRepository "
	Description	An attempt to call resolve_initial_references("InterfaceRepository") failed because the underlying ORB was unable to internally resolve a reference to the InterfaceRepository object.
	Action	Contact BEA Customer Support.

10	"ERROR: Invalid data exchange between application and infrastructure threads"
	Description	The underlying ORB was unable to exchange data between the application and the infrastructure threads while attempting to boot or process incoming requests.
	Action	Contact BEA Customer Support.

13	"ERROR: Calling infrastructure from other thread in single-threaded mode"
	Description	In a single-threaded environment, an attempt was made to call the infrastructure thread from a separate thread.
	Action	Contact BEA Customer Support.

15	"ERROR: Cannot call infrastructure when no call is active"
	Description	An attempt was made to call the infrastructure thread, when the infrastructure thread was not in a state expecting any incoming calls.
	Action	Contact BEA Customer Support.

16	"INFO: Threading level is Single-Threaded (level 0)"
	Description	This is an informational message to the user indicating that the threading level in the booted server process is single-threaded.
	Action	None.

17	"INFO: Threading level is Multi-Threaded/Serialized outgoing requests (level 1)"
	Description	This is an informational message to the user indicating that the threading level in the booted server process is multithreaded/serialized outgoing requests.
	Action	None.

18	"WARN: Invalid threading level {0}. Defaulting to level 0"
	Description	This is a warning to the user that an attempt was made to boot the server process with a threading level indicated in {0}. However, the system overrides this threading level so that the server process boots in a single-thread environment.
	Action	None.

19	"ERROR: Cannot load libij, exception:{0}"
	Description	An attempt to load the library libij by the Java Virtual Machine failed. The {0} value contains details of the exception returned to the Java Virtual Machine.
	Action	Try to resolve the problem based on the exception returned to the Java Virtual Machine. Otherwise, contact BEA Customer Support.

20	"ERROR: Invalid empty argument list"
	Description	An attempt was made to boot the server process with an invalid empty argument list.
	Action	Make sure that the UBBCONFIG file has the appropriate arguments corresponding to the server process entry.

21	"ERROR: Missing argument after -M option"
	Description	An attempt was made to boot the server process with an empty argument after the -M option.
	Action	Make sure that the UBBCONFIG file has the appropriate arguments corresponding to the server process entry.

22	"ERROR: Invalid option:{0}"
	Description	An attempt was made to boot the server process with an invalid option specified in {0}.
	Action	Make sure that the UBBCONFIG file has the appropriate arguments corresponding to the server process entry.

23	"ERROR: Missing .jar file"
	Description	An attempt was made to boot the server process with a missing .jar file in the argument list.
	Action	Make sure that the UBBCONFIG file has the appropriate arguments corresponding to the server process entry.

24	"ERROR: Invalid thread level:{0}"
	Description	An attempt was made to boot the server process with an invalid value corresponding to the thread level argument.
	Action	Make sure that the UBBCONFIG file has the appropriate arguments corresponding to the server process entry.

25	"INFO: Loading {0}"
	Description	This is an informational message indicating that the Java Virtual Machine is now loading the .jar file specified in {0}.
	Action	None.

26	"ERROR: Invalid M3 file {0} : missing {1}"
	Description	An attempt was made to boot the server process with an invalid file specified in {0}. The {1}value indicates the file that was missing that prevented a successful boot.
	Action	Make sure that the corresponding XML file for the server process has the appropriate values.

27	"ERROR: No M3-Server entry in {0}"
	Description	An attempt was made to boot the server process with no M3-server entry existing in the file specified in {0}.
	Action	Make sure that the corresponding XML file for the server process has the appropriate values.

28	"ERROR: server_init failed"
	Description	An attempt to boot the server process failed due to an internal error in the ORB.
	Action	Contact BEA Customer Support.

29	"ERROR: ServerMain.init received exception:{0}"
	Description	An attempt to boot the server process failed due to an internal error in the ORB. The {0} value provides details of the exception returned.
	Action	Contact BEA Customer Support.

30	"ERROR: ServerMain.service received exception:{0}"
	Description	An attempt to process an incoming request failed due to an internal error in the ORB. The {0} value provides details of the exception returned.
	Action	Contact BEA Customer Support.

31	"ERROR: ServerMain.release received exception:{0}"
	Description	An attempt to shut down the server process failed due to an internal error in the ORB. The {0} value provides details of the exception returned.
	Action	Contact BEA Customer Support.

32	"ERROR: Out of memory"
	Description	An attempt to allocate space for internal data structures failed because the server process ran out of memory.
	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.

34	"INFO: Total application factory shutdown assumed."
	Description	A server application is attempting to unregister an application factory during Server.release(). The server detects a problem with the unregister operation at this time. Upon further investigation, the server discovers that the entire application is shutting down. As a result, the unregister attempt silently fails because the NameManagers also shut down.
	Action	None.

35	"WARN: Posting failed; Slave NameManagers may become out of sync."
	Description	The master NameManager failed to post an update message to the SystemEventBroker, brought about by either a register_factory or an unregister_factory method. Therefore, the SystemEventBroker cannot notify any slave NameManagers. As a result, the slave's factory name mapping may lose synchronization with the master.
	Action	First check to ensure that the SystemEventBroker is running. Second, ensure that there is a communications path between the SystemEventBroker and the master NameManager. Lastly, shut down and restart the slave NameManagers. On reboot, the slave NameManagers obtain a new copy of the factory name mapping from the master NameManager.

36	"ERROR: Could not open XA resource manager in default Server.initialize(). error = {0}"
	Description	An attempt to open the XA resource manager in the default Server.initialize() failed. The {0} value provides details of the error value returned.
	Action	Take corrective action based on the error value returned.

37	"ERROR: Could not close XA resource manager in default Server.release(). error = {0}"
	Description	An attempt to close the XA resource manager in the default Server.release() failed. The {0} value provides details of the error value returned.
	Action	Take corrective action based on the error value returned.

38	"ERROR: TP.create_object_reference() could not create object reference for: Interface = {0} OID = {1}"
	Description	An internal exception was raised when an object reference for the specified interface and object ID was created. The {0} and {1} values provide details about the interface and the OID, respectively.
	Action	Contact BEA Customer Support.

39	"ERROR: TP.{0}_factory() could not register factory. Registrar service not available. Check status of FactoryFinder server(s)."
	Description	The register_factory() or unregister_factory() method failed because the FactoryFinder server or an associated server was not available. The {0} value provides details about whether the call to register or unregister the factory was made.
	Action	Verify that the FactoryFinder and all associated servers are available.

40	"ERROR: TP.{0}_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. The {0} value provides details about whether the call to register or unregister the factory was made.
	Action	Verify that the FactoryFinder and all associated servers are available.

41	"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. The call to TP.deactivateEnable should be removed from Server.initialize() and/or Server.release().

42	"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 activation policy set to transaction. This is an illegal call. Processing continues.
	Action	Notify the programmer.

43	"ERROR: ORB init failed, exception returned:{0}"
	Description	An attempt to initialize the ORB during server boot time failed. The {0} value provides details of the exception returned.
	Action	Contact BEA Customer Support.

44	"ERROR: Could not find root POA, exception returned:{0}"
	Description	An attempt to initialize the ORB during server boot time failed because the root Portable Object Adapter (POA) could not be found. The {0} value provides details of the exception returned.
	Action	Contact BEA Customer Support.

45	"ERROR: Could not create child POA, exception returned:{0}"
	Description	An attempt to initialize the ORB during server boot time failed because the child Portable Object Adapter (POA) could not be created. The {0} value provides details of the exception returned.
	Action	Contact BEA Customer Support.

46	"ERROR: Cannot set default servant, exception returned:{0}"
	Description	An attempt to initialize the ORB during server boot time failed because the default servant could not be set for the Portable Object Adapter (POA). The {0} value provides details of the exception returned.
	Action	Contact BEA Customer Support.

47	"ERROR: Exception in Server.initialize(): {0}. Reason = {1}"
	Description	During server boot time, an exception was thrown in Server.initialize(). The {0} and {1} values provide details of the exception returned.
	Action	Take corrective action based on the exception returned.

48	"ERROR: Exception in Server.initialize(): {0}. Reason = unknown"
	Description	During server boot time, an exception was thrown in Server.initialize(). The {0} value provides details of the exception returned.
	Action	Take corrective action based on the exception returned. Otherwise, contact BEA Customer Support.

49	"WARN: Exception in Server.release(): {0}. Reason = {1}"
	Description	During server shutdown, an exception was thrown in Server.release(). The {0} and {1} values provide details of the exception returned. Processing continues.
	Action	Take corrective action based on the exception returned.

50	"WARN: Exception in Server.release(): {0}. Reason = unknown"
	Description	During server shutdown, an exception was thrown in Server.release(). The {0} value provides details of the exception returned. Processing continues.
	Action	Take corrective action based on the exception returned.

51	"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.

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

53	"ERROR: Illegal recursive call on CORBA Object. Interface = {0} OID = {1}"
	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). The {0} and {1} values provide details of the interface and OID, respectively.
	Action	Notify the programmer.

54	"ERROR: Cannot find activation policy of interface"
	Description	The TP Framework was not able to find the activation policy of an interface on which an incoming request was made.
	Action	Contact BEA Customer Support.

55	"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.

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

57	"ERROR: Activating object - application raised TobjS.CreateServantFailed. Reason = {0} Interface = {1} OID = {2}"
	Description	The application raised TobjS.CreateServantFailed with the reason string supplied. The {0}, {1}, and {2} values provide details of the reason code, the interface, and the OID, respectively.
	Action	Application dependent.

58	"ERROR: Activating object - Exception not handled by application. Interface = {0} OID = {1}"
	Description	The system caught an exception while activating the object that was not handled by the application. The {0} and {1} values provide details of the interface and the OID, respectively.
	Action	Application dependent. Notify the user.

59	"ERROR: Activating object - application raised TobjS.OutOfMemory. Interface = {0} OID = {1}"
	Description	The system caught TobjS.OutOfMemory while activating the 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. The {0} and {1} values provide details of the interface and the OID, respectively.
	Action	This error may indicate that all available memory for the process has been exhausted. Ensure that the 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.

60	"ERROR: Activating object - application raised TobjS.ActivateObjectFailed. Interface = {0} OID = {1}"
	Description	The system caught TobjS.ActivateObjectFailed exception raised while activating the object. The {0} and {1} values provide details of the interface and the OID, respectively.
	Action	Application dependent.

61	"ERROR: Activating object - exception not handled by application. Interface = {0} OID = {1}"
	Description	The system caught an exception while activating the object that was not handled by the application. The {0} and {1} values provide details of the interface and the OID, respectively.
	Action	Application dependent. Notify the user.

62	"ERROR: De-activating object - application raised TobjS.DeactivateObjectFailed. Interface = {0} OID = {1} Reason = {2}"
	Description	The system caught a TobjS.DeactivateObjectFailed exception raised while deactivating the object. The {0} and {1} values provide details of the interface and OID, and reason code, respectively.
	Action	Application dependent. Notify the user.

63	"ERROR: De-activating object - Exception not handled by application. Interface = {0} OID = {1}"
	Description	The system caught an exception while deactivating the object that was not handled by the application. The {0} and {1} values provide details of the interface and OID, respectively.
	Action	Application dependent. Notify the user.

64	"ERROR: Invoking request - could not get: InterfaceID"
	Description	An internal problem occurred in the ORB while trying to access the interface.
	Action	Contact BEA Customer Support.

65	"ERROR: Invoking request - could not get: OID"
	Description	An internal problem occurred in the ORB while trying to access the OID.
	Action	Contact BEA Customer Support.

66	"ERROR: Activating object - Internal map error. Interface = {0}, OID = {1}"
	Description	An internal problem was encountered in the ORB while activating the object. The {0} and {1} values provide details of the interface and the OID, respectively.
	Action	Contact BEA Customer Support.