Messages
Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
1 |
ERROR: Missing ORB argument to Tobj_Bootstrap | |
|
Description |
An attempt to create the |
Action |
Make sure that the | |
2 |
ERROR: Cannot find class val | |
|
Description |
An attempt to create the |
Action |
Make sure that the corresponding WLE Java | |
3 |
ERROR: Cannot instantiate delegate bootstrap | |
|
Description |
An attempt to create the |
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. | |
8 |
ERROR: Underlying ORB unable to resolve a reference to FactoryFinder | |
|
Description |
An attempt to call |
Action |
Contact BEA Customer Support. | |
9 |
ERROR: Underlying ORB unable to resolve a reference to InterfaceRepository | |
|
Description |
An attempt to call |
Action |
Contact BEA Customer Support. | |
11 |
ERROR: Underlying ORB unable to resolve a reference to Tobj_SimpleEventsService | |
|
Description |
This is an internal error. |
Action |
Contact BEA Customer Support. | |
12 |
ERROR: Underlying ORB unable to resolve a reference to NotificationService | |
|
Description |
This is an internal error. |
Action |
Contact BEA Customer Support. | |
25 |
INFO: Loading val | |
|
Description |
This is an informational message indicating that the Java Virtual Machine is now loading the |
Action |
None. | |
26 |
ERROR: Invalid M3 file val : missing val1 | |
|
Description |
An attempt was made to boot the server process with an invalid file specified in val. The val1value 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 val | |
|
Description |
An attempt was made to boot the server process with no M3-server entry existing in the file specified in val. |
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. | |
31 |
ERROR: ServerMain.release received exception:val | |
|
Description |
An attempt to shut down the server process failed due to an internal error in the ORB. The val value provides details of the exception returned. |
Action |
Contact BEA Customer Support. | |
36 |
ERROR: Could not open XA resource manager in default Server.initialize(). error = val | |
|
Description |
An attempt to open the XA resource manager in the default |
Action |
Take corrective action based on the error value returned. | |
37 |
ERROR: Could not close XA resource manager in default Server.release(). error = val | |
|
Description |
An attempt to close the XA resource manager in the default |
Action |
Take corrective action based on the error value returned. | |
38 |
ERROR: TP.create_object_reference() could not create object reference for: Interface = val OID = val1 | |
|
Description |
An internal exception was raised when an object reference for the specified interface and object ID was created. The val and val1 values provide details about the interface and the OID, respectively. |
Action |
Contact BEA Customer Support. | |
40 |
ERROR: TP.val_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 val value provides details about whether the call to register or unregister
the factory was made. Another possible reason for this message is that
the FactoryFinder cannot participate in a transaction. Therefore, you may
need to suspend the current transaction before issuing the calls
|
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 |
Action |
Notify the programmer. The call to | |
42 |
WARN: TP.deactivateEnable() called illegally - object has transaction activation policy. | |
|
Description |
The application called |
Action |
Notify the programmer. | |
44 |
ERROR: Could not find root POA, exception returned:val | |
|
Description |
An attempt to initialize the ORB during server boot time failed because the root Portable Object Adapter (POA) could not be found. The val value provides details of the exception returned. |
Action |
Contact BEA Customer Support. | |
45 |
ERROR: Could not create child POA, exception returned:val | |
|
Description |
An attempt to initialize the ORB during server boot time failed because the child Portable Object Adapter (POA) could not be created. The val value provides details of the exception returned. |
Action |
Contact BEA Customer Support. | |
46 |
ERROR: Cannot set default servant, exception returned:val | |
|
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 val value provides details of the exception returned. |
Action |
Contact BEA Customer Support. | |
47 |
ERROR: Exception in Server.initialize(): val. Reason = val1 | |
|
Description |
During server boot time, an exception was thrown in |
Action |
Take corrective action based on the exception returned. | |
48 |
ERROR: Exception in Server.initialize(): val. Reason = unknown | |
|
Description |
During server boot time, an exception was thrown in |
Action |
Take corrective action based on the exception returned. Otherwise, contact BEA Customer Support. | |
49 |
WARN: Exception in Server.release(): val. Reason = val1 | |
|
Description |
During server shutdown, an exception was thrown in |
Action |
Take corrective action based on the exception returned. | |
50 |
WARN: Exception in Server.release(): val. Reason = unknown | |
|
Description |
During server shutdown, an exception was thrown in |
Action |
Take corrective action based on the exception returned. | |
51 |
INFO: Default Server.initialize() used. | |
|
Description |
The programmer either did not implement |
Action |
None. | |
52 |
INFO: Default Server.release() used. | |
|
Description |
The programmer either did not implement |
Action |
None. | |
53 |
ERROR: Illegal recursive call on CORBA Object. Interface = val OID = val1 | |
|
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 |
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, | |
57 |
ERROR: Activating object - application raised TobjS.CreateServantFailed. Reason = val Interface = val1 OID = val2 | |
|
Description |
The application raised |
Action |
Application dependent. Notify the programmer. | |
58 |
ERROR: Activating object - Exception not handled by application. Interface = val OID = val1 | |
|
Description |
The system caught an exception while activating the object that was not handled by the application. The val and val1 values provide details of the interface and the OID, respectively. |
Action |
Application dependent. Notify the programmer. | |
59 |
ERROR: Activating object - application raised TobjS.OutOfMemory. Interface = val OID = val1 | |
|
Description |
The system caught |
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 = val OID = val1 Reason = val2 | |
|
Description |
The system caught |
Action |
Application dependent. Notify the programmer. | |
61 |
ERROR: Activating object - exception not handled by application. Interface = val OID = val1 | |
|
Description |
The system caught an exception while activating the object that was not handled by the application. The val and val1 values provide details of the interface and the OID, respectively. |
Action |
Application dependent. Notify the programmer. | |
62 |
ERROR: De-activating object - application raised TobjS.DeactivateObjectFailed. Interface = val OID = val1 Reason = val2 | |
|
Description |
The system caught a |
Action |
Application dependent. Notify the programmer. | |
63 |
ERROR: De-activating object - Exception not handled by application. Interface = val OID = val1 | |
|
Description |
The system caught an exception while deactivating the object that was not handled by the application. The val and val1 values provide details of the interface and OID, respectively. |
Action |
Application dependent. Notify the programmer. | |
68 |
ERROR: Orb initialization failed | |
|
Description |
An internal problem was encountered in the ORB during initialization of the JavaServer. |
Action |
Contact BEA Customer Support. | |
69 |
ERROR: CorbaMain.sever_init received INTERNAL exception: val | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. The val value contains details of the exception returned to the Java Virtual Machine. |
Action |
Contact BEA Customer Support. | |
70 |
ERROR: CorbaMain.sever_init received exception: val | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. The val value contains details of the exception returned to the Java Virtual Machine. |
Action |
Contact BEA Customer Support. | |
71 |
ERROR: CorbaDeployment.deploy received INTERNAL exception: val | |
|
Description |
An internal problem was encountered during initialization of the Java server application. The val value contains details of the exception returned to the Java Virtual Machine. |
Action |
Contact BEA Customer Support. | |
72 |
ERROR: CorbaDeployment.deploy received exception: val | |
|
Description |
An internal problem was encountered during initialization of the Java server application. The val value contains details of the exception returned to the Java Virtual Machine. |
Action |
Contact BEA Customer Support. | |
73 |
WARN: TP.create_active_object_reference() called illegally - interface is unknown in this server: Interface = val OID = val1 | |
|
Description |
|
Action |
Notify the programmer. The interface name that is specified in the call to
| |
74 |
WARN: TP.create_active_object_reference() called illegally - object does not have process activation policy: Interface = val OID = val1 | |
|
Description |
|
Action |
Notify the programmer. The interface that is specified in the call to
| |
75 |
ERROR: TP.create_active_object_reference() could not create object reference for: Interface = val OID = val | |
|
Description |
An exception occurred. The object reference could not be created. The val and val1 values provide details of the interface and the OID, respectively. |
Action |
Contact BEA Customer Support. | |
76 |
ERROR: initialize received exception: val | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. The val value contains details of the exception returned to the Java Virtual Machine. |
Action |
Contact BEA Customer Support. | |
77 |
ERROR: TP.val_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 val 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. | |
78 |
ERROR: Cannot proceed with TP.register_factory or TP.unregister_factory 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 val 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. | |
79 |
ERROR: Cannot decode jar file property | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. |
Action |
Contact BEA Customer Support. | |
80 |
ERROR: Cannot decode argument property | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. |
Action |
Contact BEA Customer Support. | |
81 |
ERROR: Cannot instantiate framework with "val": val1 | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. The val value gives additional information about which framework was being instantiated. The val1 value contains details of the exception returned to the Java Virtual Machine. |
Action |
Contact BEA Customer Support. | |
82 |
ERROR: Cannot get skeleton information for class val | |
|
Description |
An internal problem was encountered during initialization of the Java server application. The val value contains the name of the class that was being processed. |
Action |
Contact BEA Customer Support. | |
83 |
ERROR: Cannot create ApplicationServer! | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. |
Action |
Contact BEA Customer Support. | |
85 |
ERROR: Cannot invoke server_init, caught exception: val | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. The val value contains details of the exception returned to the Java Virtual Machine. |
Action |
Contact BEA Customer Support. | |
86 |
ERROR: Cannot invoke server_init, caught exception: val | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. The val value contains details of the exception returned to the Java Virtual Machine. |
Action |
Contact BEA Customer Support. | |
87 |
ERROR: Could not resolve initial reference for POACurrent during initialization | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. |
Action |
Contact BEA Customer Support. | |
88 |
ERROR: Could not narrow POACurrent during initialization | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. |
Action |
Contact BEA Customer Support. | |
89 |
ERROR: Object is not a ServantInfo | |
|
Description |
The ORB expects the object to be an instance of the ServantInfo class. |
Action |
Contact BEA Customer Support. | |
90 |
ERROR: Caught unexpected TpfwException | |
|
Description |
An unexpected exception occurred during object activation. |
Action |
Contact BEA Customer Support. | |
91 |
ERROR: Caught unexpected DeactivateObjectFailed | |
|
Description |
An unexpected exception occurred during object deactivation. |
Action |
Contact BEA Customer Support. | |
92 |
ERROR: Caught unexpected TpfwException from call to postInvoke | |
|
Description |
An unexpected exception occurred during object deactivation. |
Action |
Contact BEA Customer Support. | |
93 |
ERROR: Caught unexpected Throwable exception | |
|
Description |
An unexpected exception occurred during object deactivation. |
Action |
Contact BEA Customer Support. | |
94 |
ERROR: Caught unexpected Throwable exception from call to postInvoke | |
|
Description |
An unexpected exception occurred. |
Action |
Contact BEA Customer Support. | |
95 |
ERROR: Caught Throwable, throw OBJECT_NOT_EXIST | |
|
Description |
An unexpected exception occurred during object activation. |
Action |
Contact BEA Customer Support. | |
96 |
ERROR: TP.create_active_object_reference() could not activate object for: Interface = val OID = val | |
|
Description |
An exception occurred. The object could not be activated. The val and val1 values provide details of the interface and the OID, respectively. |
Action |
Contact BEA Customer Support. | |
97 |
ERROR: Tobj_Bootstrap initialization failed | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. |
Action |
Contact BEA Customer Support. | |
99 |
ERROR: Cannot create JNDI 'wle.factories' subcontext. | |
|
Description |
An internal problem was encountered during initialization of the JavaServer. |
Action |
Contact BEA Customer Support. |