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.
| 
 300  | 
 ERROR: Value of 'property' is not a String as expected  | |
| 
 
  | 
 Description  | 
 The value of the indicated environment property was not a String.  | 
| 
 Action  | 
 Make sure that the indicated property is set to a String value in the application.  | |
| 
 301  | 
 ERROR: Value of 'property' is not "TRUE" or "FALSE" as expected  | |
| 
 
  | 
 Description  | 
 The value of the indicated environment property was not a Boolean string.  | 
| 
 Action  | 
 Make sure that the indicated property is set to a correct boolean String value in the application.  | |
| 
 302  | 
 ERROR: Internal error - unable to create root context factory  | |
| 
 
  | 
 Description  | 
 An unexpected exception occurred when attempting to instantiate the   | 
| 
 Action  | 
 Check the system ULOG for further diagnostic messages. Make sure the server classpath is properly configured.  | |
| 
 303  | 
 ERROR: Internal error - problem creating 'wle.ejb' sub-context: rootException  | |
| 
 
  | 
 Description  | 
 An internal unexpected error occurred when attempting to create a subcontext in the local JNDI namespace. The rootException indicates the underlying exception for the failure.  | 
| 
 Action  | 
 Contact BEA Customer Support.  | |
| 
 304  | 
 ERROR: Limit reached while following link references, possible link cycle  | |
| 
 
  | 
 Description  | 
 An attempt was made to resolve a chain of   | 
| 
 Action  | 
 
Check the   | |
| 
 305  | 
 ERROR: Exception occurred while invoking object factory  | |
| 
 
  | 
 Description  | 
 An unexpected exception occurred while attempting to resolve an object binding to a target instance.  | 
| 
 Action  | 
 Check the root exception for more information. For reference bindings, the object factory may not have been able to create the target instance.  | |
| 
 306  | 
 ERROR: Can't remove object of type class1 from an aggregate of type class2  | |
| 
 
  | 
 Description  | 
 An attempt was made to unbind an object of class1 from an   | 
| 
 Action  | 
 
Application dependent.  The application should only unbind   | |
| 
 307  | 
 ERROR: Context does not support subcontexts  | |
| 
 
  | 
 Description  | 
 An attempt was made by the application to create a subcontext in a context that only supports a flat namespace.  | 
| 
 Action  | 
 
Application dependent.  The application must not create subcontexts in a context associated with a   | |
| 
 308  | 
 ERROR: name is not an instance of class as expected  | |
| 
 
  | 
 Description  | 
 A subcontext naming operation failed. The indicated name is not bound to a subcontext instance of class as expected.  | 
| 
 Action  | 
 Application dependent. Notify the programmer.  | |
| 
 309  | 
 ERROR: Could not resolve bound object reference to an object instance  | |
| 
 
  | 
 Description  | 
 An unexpected exception occurred when attempting to create a target object instance from a bound object reference.  | 
| 
 Action  | 
 Check the root exception for more information. Make sure that the required object factory classes are in the server classpath.  | |
| 
 310  | 
 ERROR: method called with empty name  | |
| 
 
  | 
 Description  | 
 A naming operation with an empty name was attempted by the application.  | 
| 
 Action  | 
 Application dependent. Notify the programmer.  | |
| 
 311  | 
 ERROR: Internal error - unable to set parent for naming store  | |
| 
 
  | 
 Description  | 
 An attempt to set the parent for the current naming store failed.  | 
| 
 Action  | 
 Contact BEA Customer Support.  | |
| 
 312  | 
 ERROR: Internal error - name is empty or has multiple composite components  | |
| 
 
  | 
 Description  | 
 An attempt to parse a local name failed. The name is either empty or has naming components outside the local namespace.  | 
| 
 Action  | 
 Contact BEA Customer Support.  | |
| 
 313  | 
 ERROR: Internal error - failed to create NormalName  | |
| 
 
  | 
 Description  | 
 An attempt to create an internal object instance   | 
| 
 Action  | 
 Contact BEA Customer Support.  | |
| 
 314  | 
 ERROR: Internal error - name is empty or has multiple composite components  | |
| 
 
  | 
 Description  | 
 An attempt to parse a local name failed. The name is either empty or has naming components outside the local namespace.  | 
| 
 Action  | 
 Contact BEA Customer Support.  | |
| 
 315  | 
 ERROR: Internal error - invalid name: "val"  | |
| 
 
  | 
 Description  | 
 An internal attempt to parse a composite name failed. The invalid name is indicated by val.  | 
| 
 Action  | 
 Contact BEA Customer Support.  | |
| 
 316  | 
 ERROR: Internal error - problem creating 'wle.factories' sub-context: rootException  | |
| 
 
  | 
 Description  | 
 An internal unexpected error occurred when attempting to create a subcontext in the local JNDI namespace. The rootException indicates the underlying exception for the failure.  | 
| 
 Action  | 
 Contact BEA Customer Support.  | |