Problem | The assembly tool is beginning the process of validating the configuration for the application. |
User response | None |
Problem | The assembly tool is beginning the process of validating the configuration for the Application Profile service. |
User response | None |
Problem | The assembly tool is beginning the process of validating the configuration for the Internationalization service. |
User response | None |
Problem | The assembly tool is beginning the process of validating the configuration for the Extended Messaging service. |
User response | None |
Problem | The assembly tool is beginning the process of validating the configuration for the ActivitySession service. |
User response | None |
Problem | An enterprise component is missing its reference to the ejb module or the reference is invalid. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | An enterprise component is missing its reference to the ejb module extension or the reference is invalid. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | An enterprise component is missing its reference to the web module or the reference is invalid. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | An enterprise component is missing its reference to the web module extension or the reference is invalid. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | An enterprise component is missing its reference to the client module or the reference is invalid. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | An enterprise component is missing its reference to the client module extension or the reference is invalid. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | An Application Profile was not given a name. |
User response | Provide a unique name for the profile. |
Problem | Two different profiles with the same name were found in the application. |
User response | Ensure that profiles each have a unique name. |
Problem | A task was configured without a name. |
User response | Make sure each task has a name. |
Problem | A task was configured on multiple Application Profile or used multiple times in a list of task references. |
User response | Remove the duplicate task or tasks. |
Problem | A custom Access Intent policy was configured without a name. |
User response | Provide a unique name for each Access Intent policy. |
Problem | More than one Access Intent policy has the same name. |
User response | Ensure that each instance of an Access Intent policy has a unique name. |
Problem | Each Application Profile in an ejb module must be defined at the application scope. |
User response | Configure the Application Profile at the application scope. |
Problem | The referenced Access Intent policy does not exist. |
User response | Either define the Access Intent policy or remove the reference. |
Problem | The Access Intent policy is invalid. |
User response | Review the Application Profile and Access Intent documentation and ensure that all Access Intent policies adhere to the specification. |
Problem | A referenced method cannot be found. |
User response | Remove the invalid method reference. |
Problem | A method is configured with different policies. |
User response | Remove extra policy configurations. |
Problem | A bean is configured with different policies. |
User response | Remove extra policy configurations. |
Problem | A servlet is configured with different policies. |
User response | Remove extra policy configurations. |
Problem | A task reference was defined without a name. |
User response | Give each task reference a unique name. |
Problem | Two task references were defined with the same name. |
User response | Configure each task reference to have a unique name. |
Problem | An attribute was configured with a reference to a nonexistent bean. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | A bean-scoped attribute was configured without a reference to a bean. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | A bean-scoped attribute was configured without a reference to a bean extension. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | An attribute was configured with a reference to a nonexistent servlet. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | A servlet-scoped attribute was configured without a reference to a servlet. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | A servlet-scoped attribute was configured without a reference to a servlet extension. |
User response | Reassemble the application so that only valid components are referenced. |
Problem | A specified time zone ID is invalid. 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. |
User response | 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. |
Problem | A specified locale is invalid. If the configuration is not corrected, then the runtime will use the default locale of the process. Refer to the Internationalization service's documentation. |
User response | 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. |
Problem | A Run as attribute is invalid. If the configuration is not corrected, then the runtime will use the default locale of the process. Refer to the Internationalization service's documentation. |
User response | 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. |
Problem | The bean is not container-managed for the service's policies. |
User response | Verify that policies are configured only for methods from container-managed beans. |
Problem | The servlet is not container-managed for the service's policies. |
User response | Verify that policies are configured only for container-managed servlets. |
Problem | The noted class is missing a required attribute. |
User response | Reassemble the application so that all required attributes are provided. |
Problem | The noted value is illegal. |
User response | Reassemble the application so that the noted value is replaced with a valid value. |
Problem | Read ahead hints must be comprised of declared CMR field names that define paths which can be navigated from the source bean. |
User response | Reassemble the application with valid read ahead hint values. |
Problem | Beans that are configured for lifetime in cache may not be configured for update. |
User response | Reassemble the application so either lifetime in cache is disabled or access intent is read-only. |
Problem | Beans that are configured for lifetime in cache may not be configured for pessimistic update. |
User response | Reassemble the application so either lifetime in cache is disabled or access intent is read-only or optimistic update. |
Problem | The assembly tool is beginning the process of validating the configuration for the Dynamic Query service. |
User response | None |
Problem | Dynamic Query must use one of WebSphere's predefined access intent policies. |
User response | Reassemble the application so that dynamic query uses one of WebSphere's predefined access intent policies. |