Explanation | The internationalization service API and propagation mechanisms provide default values for internationalization context elements that are either unavailable or not valid. |
Action | The service provides local process default elements for any caller context elements that are missing from an incoming request. For invocation context elements, specify the invocation locales and time zones through the internationalization context API before issuing outgoing requests. |
Explanation | The specified internationalization context element was unavailable during a particular action, such as handling an incoming request or completing an internationalization context API method invocation. |
Action | A context element can be missing from an incoming request (for instance, a request from a client that is not using the internationalization service). For caller context, enable the internationalization service on the client, if possible. For missing invocation context elements, specify them through the internationalization context API. |
Explanation | The specified type of context element is malformed. See the product documentation for details about well-formed locale and time zone elements. |
Action | When using the [CMI, Run-As-Specified] internationalization context management policy, reassemble the application component and correct the problematic context element. For application-managed internationalization, correct the problematic context element within the application source. |
Explanation | The format of an internationalization context element detected on an incoming request is not supported by this release of the internationalization service. |
Action | No action is required. By default, the service uses the format of the local process. |
Explanation | The internationalization service applies the default context management policy [CMI, Run-As-Caller] for internationalization context management deployment descriptors that are either unavailable or not valid. |
Action | No action is required. If you prefer a context management policy other than the default, reassemble the application and assign internationalization context management policies to all components. |
Explanation | The internationalization context element for the application component was unavailable during a particular action, such as handling an outgoing request or completing an internationalization context API method invocation. |
Action | Reassemble the application and assign an internationalization context management policy to the component indicated. Otherwise, the service uses the default policy. |
Explanation | The content of an internationalization context management policy is not valid. |
Action | Reassemble the application and ensure that the specified internationalization context management policy is supported. |
Explanation | No internationalization context management information was detected for the specified application component. |
Action | Reassemble the application and assign an internationalization context management policy to the specified component. Otherwise, the service uses the default policy. |
Explanation | Specifies the current state, configuration, or quality of the internationalization service. |
Action | No action is required. |
Explanation | Indicates a re-attempted action on the internationalization service. |
Action | No action is required. |
Explanation | The specified action on the internationalization service has not occurred. |
Action | No action is required. |
Explanation | Indicates a change in the quality of the internationalization service. If a serious problem occurs, service might be suspended. |
Action | Review the trace log for error conditions that might result in suspension of service. |
Explanation | The message key supplied to retrieve a message is not valid. |
Action | None. |
Explanation | The service encountered an unexpected condition. |
Action | Enable tracing for the internationalization service and examine the trace log for statements that indicate both the actual problem and the resulting quality of service. |
Explanation | A minor code indicates a particular system error. |
Action | None. Minor codes are not implemented in this release of the internationalization service. |
Explanation | The Java security framework is prohibiting access to the default Java Virtual Machine locale or time zone. |
Action | Modify the Java security framework permissions to allow access to the default locale or time zone. |
Explanation | The internationalization context API throws an IllegalStateException exception whenever an application component attempts to set its invocation locale while running under a container-managed internationalization context policy (for example, [CMI, Run-As-Caller]). |
Action | Reassemble the application and associate the application-managed internationalization context management policy to the specified application component. |
Explanation | A serious error has occurred: The internationalization service cannot handle IIOP requests with an object request broker (ORB). |
Action | Review the trace log for related error conditions. |
Explanation | A serious error has occurred: The internationalization service cannot scope context elements without the thread context manager. |
Action | Review the trace log for related error conditions. |
Explanation | A serious error has occurred: Without the activity service, internationalization context cannot be propagated over IIOP requests. |
Action | Review the trace log for activity service error conditions. |
Explanation | The internationalization context is not supported in the specified asynchronous beans runtime environment, if it is running. |
Action | If the application server must support asynchronous beans, verify that asynchbeans.jar resides in the class path and review the trace log for error conditions related to asynchronous beans. |
Explanation | A serious error has occurred: Without Enterprise JavaBeans (EJB) container support, internationalization context cannot be scoped properly to EJB methods. |
Action | Review the trace log for EJB container-related error conditions. |
Explanation | A serious error has occurred: Without Web container support, internationalization context cannot be scoped properly to servlets and JavaServer Pages components. |
Action | Review the trace log for any Web container-related error conditions. |
Explanation | A serious error has occurred: Without SOAP handling support, internationalization context cannot be scoped properly to Web services. |
Action | Review the trace log for any Web service-related error conditions. |
Explanation | A serious error has occurred: Without the metadata service, internationalization context management policies default to [CMI, Run-As-Caller]. |
Action | Review the trace log for error conditions related to the metadata service. |
Explanation | A serious error has occurred: Without API support, application components cannot access internationalization context elements. |
Action | None. |
Explanation | A serious error has occurred: Without naming service (JNDI) support, application components cannot obtain internationalization context API references. |
Action | Review the trace log for error conditions related to the naming service. |