Internationalization service errors

The following conditions can occur while your internationalized application is running. These conditions might cause the internationalization service not to start, to throw instances of IllegalStateException, or to exercise default behaviors:

If you encounter unexpected or exceptional behavior, the problem is likely related to one of these conditions. You need to examine the trace log to investigate these conditions, which requires that you configure the diagnostic trace service to generate messages about internationalization service function. To do this, see the topic Troubleshooting the internationalization service.

The service is disabled

The internationalization service does not initialize and start when the service's startup setting is cleared. The service generates a message indicating whether it is enabled or disabled. Applications cannot access the internationalization API when the service is disabled. If an application attempts a JNDI lookup to obtain the UserInternationationlization reference, the lookup fails with a NamingException indicating the reference could not be found. In addition, the service does not scope (propagate) internationalization context on incoming (outgoing) business method invocations.

The service is not started

The internationalization service is operational whenever it is in the STARTED state. For example, if an application attempts to access internationalization context and the service is not started, the API throws an IllegalStateException. In addition, the service does not provide runtime support for servlets and enterprise beans.

As an application server progresses through its lifecycle, it initializes, starts, stops, and terminates (destroys) the internationalization service. If an anomaly occurs during initialization, the service does not start. Once the service has been started, its state can change to BLOCKED in the event that a serious error occurs. The service generates a message for every state change.

If a trace message indicates that the service is not STARTED, examine previous messages to determine the problem. For instance, the internationalization service does not start if the activity service is unavailable and a message is displayed to that effect during initialization of the internationalization service.

During startup, the following messages indicate potential configuration or run-time problems:

No ORB support
The service could not obtain an instance of the ORB. This is a fatal error. Examine the logs for information.
No TCM support
The service could not obtain an instance of its thread context manager. This is a fatal error. Examine the logs for information.
No IIOP (Activity service) support
The service could not register with the Activity service. This is a fatal error. The internationalization service cannot propagate or receive context on IIOP requests without Activity service support. Review the logs for error conditions related to the Activity service.
No AsynchBeans support
The service could not register into the AsynchBeans environment. This warning indicates that the AsynchBeans environment cannot support internationalization context. If the application server should have AsynchBeans support, verify that the asynchbeans.jar and asynchbeansimpl.jar files exist in the classpath and review the trace log for any AsynchBeans error conditions.
No EJB container support
The service could not register with the EJB container. This is a warning that the internationalization service cannot support enterprise beans. Without EJB container support, internationalization, contexts do not scope properly to EJB business methods. Review the trace log for any EJB container-related error conditions.
No Web container support
The service could not register with the Web container. This is a warning that the internationalization service cannot support servlets and Java Server Pages (JSPs). Without Web container support, internationalization contexts do not scope properly to servlet service methods. Review the trace log for any Web container-related error conditions.
No Meta-data support
The service could not register with the meta-data service. This is a warning that the internationalization service cannot process the internationalization policies within application deployment descriptors. Without meta-data support, the service associates the default internationalization context management policy, [CMI, RunAsCaller], to every servlet lifecycle method and enterprise bean business method invocation. Review the trace log for any meta-data service-related error conditions.
No JNDI (Name service) support
The service could not bind the UserInternationalization object into the namespace. This is a fatal error. Application components are unable to access internationalization context API references, and are therefore unable to access internationalization context elements. Review the trace log for any Naming (JNDI) service-related error conditions.
No API support
The service could not obtain an instance of an internationalization context API object. This is a fatal error. Application components are unable to access internationalization context API references, and are therefore unable to access internationalization context elements.

Invalid context element

The service detected an invalid internationalization context element. For example, the internationalization service does not support TimeZone instances of a type other than java.util.SimpleTimeZone. If the service encounters an invalid element, it logs a message and substitutes the corresponding default element of the JVM.

Missing context element

The service detected a missing internationalization context element. Incoming requests, for example from application servers not supporting the internationalization service will lack internationalization context. When the service attempts to access a caller internationalization context element, which does not exist in this case, it logs a message and substitutes the corresponding default element of the JVM.

Whenever possible, the internationalization service should be enabled within all clients and hosting application servers comprising a WebSphere enterprise application. For more information see the topic Managing the internationalization service.

Invalid policy

The internationalization service detected a malformed internationalization policy in the application deployment descriptor. At execution, the service replaces the malformed attribute with the appropriate default. For instance, if the internationalization type for an entity bean is set to Application during the execution of a servlet or EJB business method invocation, the service logs the inconsistency and enforces the Container setting instead.

Also, AMI application components do have an implicit container internationalization attribute. By default they run as server. The service silently enforces the implicit policy, [AMI, RunAsServer], and logs messages to this effect.

Invalid container internationalization attributes are likely to occur when specifying the Locales and Time zone ID fields. When encountering invalid Locales and Time zone ID within attributes, the service replaces each with the corresponding default element of the JVM. Be sure to follow the guidelines provided in the topic Assembling internationalized applications.

Missing policy

The service detected a missing internationalization policy. At execution, the service replaces the missing policy with the appropriate default. For instance, if the internationalization type is missing for a servlet or enterprise bean, the service sets the attribute to Container.

Container internationalization attributes are not mandatory for CMI application components. In the event that a CMI servlet or EJB business method lacks a container internationalization attribute, the service silently enforces the implicit policy [CMI, RunAsCaller].

When an application lacks internationalization policies in its deployment descriptor, or meta-data support is unavailable, the service logs a message and applies the policy [CMI, RunAsCaller] on every servlet service method and EJB business method invocation.

For more information, see the following topics:


Related tasks
Troubleshooting the internationalization service
Related reference
Internationalization service exceptions



Searchable topic ID:   rin_troubleshoot
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/i18n/ref/rin_troubleshoot.html

Library | Support | Terms of Use | Feedback