Explanation | The assembly tool is beginning the process of validating the configuration for the application. |
Action | None |
Explanation | The assembly tool is beginning the process of validating the configuration for the Application Profile service. |
Action | None |
Explanation | The assembly tool is beginning the process of validating the configuration for the Internationalization service. |
Action | None |
Explanation | The assembly tool is beginning the process of validating the configuration for the Extended Messaging service. |
Action | None |
Explanation | The assembly tool is beginning the process of validating the configuration for the ActivitySession service. |
Action | None |
Explanation | An enterprise component is missing its reference to the ejb module or the reference is not valid. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | An enterprise component is missing its reference to the ejb module extension or the reference is not valid. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | An enterprise component is missing its reference to the web module or the reference is not valid. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | An enterprise component is missing its reference to the web module extension or the reference is not valid. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | An enterprise component is missing its reference to the client module or the reference is not valid. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | An enterprise component is missing its reference to the client module extension or the reference is not valid. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | An Application Profile was not given a name. |
Action | Provide a unique name for the profile. |
Explanation | Two different profiles with the same name were found in the application. |
Action | Ensure that profiles each have a unique name. |
Explanation | A task was configured without a name. |
Action | Make sure each task has a name. |
Explanation | A task was configured on multiple Application Profile or used multiple times in a list of task references. |
Action | Remove the duplicate task or tasks. |
Explanation | A custom Access Intent policy was configured without a name. |
Action | Provide a unique name for each Access Intent policy. |
Explanation | More than one Access Intent policy has the same name. |
Action | Ensure that each instance of an Access Intent policy has a unique name. |
Explanation | Each Application Profile in an ejb module must be defined at the application scope. |
Action | Configure the Application Profile at the application scope. |
Explanation | The referenced Access Intent policy does not exist. |
Action | Either define the Access Intent policy or remove the reference. |
Explanation | The Access Intent policy is not valid. |
Action | Review the Application Profile and Access Intent documentation and ensure that all Access Intent policies adhere to the specification. |
Explanation | A referenced method cannot be found. |
Action | Remove the method reference which is not valid. |
Explanation | A method is configured with different policies. |
Action | Remove extra policy configurations. |
Explanation | A bean is configured with different policies. |
Action | Remove extra policy configurations. |
Explanation | A servlet is configured with different policies. |
Action | Remove extra policy configurations. |
Explanation | A task reference was defined without a name. |
Action | Give each task reference a unique name. |
Explanation | Two task references were defined with the same name. |
Action | Configure each task reference to have a unique name. |
Explanation | An attribute was configured with a reference to a nonexistent bean. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | A bean-scoped attribute was configured without a reference to a bean. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | A bean-scoped attribute was configured without a reference to a bean extension. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | An attribute was configured with a reference to a nonexistent servlet. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | A servlet-scoped attribute was configured without a reference to a servlet. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | A servlet-scoped attribute was configured without a reference to a servlet extension. |
Action | Reassemble the application so that only valid components are referenced. |
Explanation | A specified time zone ID is not valid. If the configuration is not corrected, then the runtime will use the default time zone of the process. Refer to the Internationalization service's documentation. |
Action | A valid time zone ID identifies any time zone supported by SDK class java.util.TimeZone. Time zone ID may be a custom ID having format GMT[+|-]hh[[:]mm], or any ID returned by method java.util.TimeZone.getAvailableIDs(). Modify the time zone ID according to the Internationalization service's documentation. |
Explanation | A specified locale is not valid. If the configuration is not corrected, then the runtime will use the default locale of the process. Refer to the Internationalization service's documentation. |
Action | A valid locale contains at least a Language code or a Country code, where a Language code is preferrably a valid ISO 639 language code, and a Country code is preferrably a valid ISO 3166 country code. Modify the locale configuration according to the Internationalization service's documentation. |
Explanation | A Run as attribute is not valid. If the configuration is not corrected, then the runtime will use the default locale of the process. Refer to the Internationalization service's documentation. |
Action | A valid Run as attribute, when set to Specified, specifies at least one valid locale and a valid time zone ID. Modify the Run as configuration according to the Internationalization service's documentation. |
Explanation | The bean is not container-managed for the service's policies. |
Action | Verify that policies are configured only for methods from container-managed beans. |
Explanation | The servlet is not container-managed for the service's policies. |
Action | Verify that policies are configured only for container-managed servlets. |
Explanation | The noted class is missing a required attribute. |
Action | Reassemble the application so that all required attributes are provided. |
Explanation | The noted value is illegal. |
Action | Reassemble the application so that the noted value is replaced with a valid value. |
Explanation | Read ahead hints must be comprised of declared CMR field names that define paths which can be navigated from the source bean. |
Action | Reassemble the application with valid read ahead hint values. |
Explanation | Beans that are configured for lifetime in cache may not be configured for update. |
Action | Reassemble the application so either lifetime in cache is disabled or access intent is read-only. |
Explanation | Beans that are configured for lifetime in cache may not be configured for pessimistic update. |
Action | Reassemble the application so either lifetime in cache is disabled or access intent is read-only or optimistic update. |
Explanation | The assembly tool is beginning the process of validating the configuration for the Dynamic Query service. |
Action | None |
Explanation | Dynamic Query must use one of WebSphere's predefined access intent policies. |
Action | Reassemble the application so that dynamic query uses one of WebSphere's predefined access intent policies. |