WebSphere Process Server messages     Operating Systems: All supported

EAAT

EAAT0001I: Validating the Enterprise configuration for {0}
Problem The assembly tool is beginning the process of validating the configuration for the application.
User response None
EAAT0002I: Validating the Application Profile configuration for {0}
Problem The assembly tool is beginning the process of validating the configuration for the Application Profile service.
User response None
EAAT0003I: Validating the Internationalization configuration for {0}
Problem The assembly tool is beginning the process of validating the configuration for the Internationalization service.
User response None
EAAT0004I: Validating the Extended Messaging configuration for {0}
Problem The assembly tool is beginning the process of validating the configuration for the Extended Messaging service.
User response None
EAAT0005I: Validating the ActivitySession configuration for {0}
Problem The assembly tool is beginning the process of validating the configuration for the ActivitySession service.
User response None
EAAT0006E: Invalid EJB Jar reference
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.
EAAT0007E: Invalid EJB Jar extension reference
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.
EAAT0008E: Invalid Web Application reference
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.
EAAT0009E: Invalid Web Application extension reference
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.
EAAT0010E: Invalid Application Client reference
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.
EAAT0011E: Invalid Application Client extension reference
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.
EAAT0012E: Application Profile without a name
Problem An Application Profile was not given a name.
User response Provide a unique name for the profile.
EAAT0013E: Duplicate Application Profile {0}
Problem Two different profiles with the same name were found in the application.
User response Ensure that profiles each have a unique name.
EAAT0014E: Task without a name
Problem A task was configured without a name.
User response Make sure each task has a name.
EAAT0015E: Duplicate task {0}
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.
EAAT0016E: Missing Access Intent policy name
Problem A custom Access Intent policy was configured without a name.
User response Provide a unique name for each Access Intent policy.
EAAT0017E: Duplicate Access Intent policy {0}
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.
EAAT0018E: Application Profile {0} not defined at the application scope
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.
EAAT0019E: Access Intent policy {0} is not defined in this module
Problem The referenced Access Intent policy does not exist.
User response Either define the Access Intent policy or remove the reference.
EAAT0020E: Illegal Access Intent policy {0} {1} {2}
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.
EAAT0021E: Policy {0} configured on unknown method {1}
Problem A referenced method cannot be found.
User response Remove the invalid method reference.
EAAT0022E: Method {0} is configured with both policies {1} and {2}
Problem A method is configured with different policies.
User response Remove extra policy configurations.
EAAT0023E: Bean {0} is configured with both policies {1} and {2}
Problem A bean is configured with different policies.
User response Remove extra policy configurations.
EAAT0024E: Servlet {0} is configured with both policies {1} and {2}
Problem A servlet is configured with different policies.
User response Remove extra policy configurations.
EAAT0025E: Task reference with no name
Problem A task reference was defined without a name.
User response Give each task reference a unique name.
EAAT0026E: Duplicate task reference {0}
Problem Two task references were defined with the same name.
User response Configure each task reference to have a unique name.
EAAT0027E: Unknown bean {0}
Problem An attribute was configured with a reference to a nonexistent bean.
User response Reassemble the application so that only valid components are referenced.
EAAT0028E: Invalid bean reference
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.
EAAT0029E: Invalid bean extension reference
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.
EAAT0030E: Unknown servlet {0}
Problem An attribute was configured with a reference to a nonexistent servlet.
User response Reassemble the application so that only valid components are referenced.
EAAT0031E: Invalid servlet reference
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.
EAAT0032E: Invalid servlet extension reference
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.
EAAT0033E: Invalid time zone: {0}, {1}
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.
EAAT0034E: Invalid locale: {0}, {1}
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.
EAAT0035E: Invalid run-as container attribute: {0}; see above errors.
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.
EAAT0036E: A policy is configured on method {0}, but the container is not configured to manage the policies for the service
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.
EAAT0037E: A policy is configured on servlet {0}, but the container is not configured to manage the policies for the service
Problem The servlet is not container-managed for the service's policies.
User response Verify that policies are configured only for container-managed servlets.
EAAT0038E: A required attribute is not defined within {0}
Problem The noted class is missing a required attribute.
User response Reassemble the application so that all required attributes are provided.
EAAT0039E: The value {0} is illegal.
Problem The noted value is illegal.
User response Reassemble the application so that the noted value is replaced with a valid value.
EAAT0040E: The read ahead hint {0} is invalid.
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.
EAAT0041E: The entity bean {0} is lifetime in cache enabled and may not be configured with update access type in access intent policy {1}.
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.
EAAT0042E: The entity bean {0} is lifetime in cache enabled and may not be configured with a pessimistic update access type in access intent policy {1}.
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.
EAAT0043I: Validating the Dynamic Query configuration for {0}
Problem The assembly tool is beginning the process of validating the configuration for the Dynamic Query service.
User response None
EAAT0044E: Validating the Dynamic Query configuration for {0}
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.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.websphere.validation.pme.extensions.pmeExtensionValidation.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)