|
WebSphere Access Intent messages |
|
ACIN0001E: Message key {0} was not found in any searched catalog.
Explanation:
A key was passed into the AccessIntentMessages class to resolve to a string, but a properties file for the locale could not be found and the appropriate message could not be retrieved.
User Response:
Determine why the message catalog could not be found.
ACIN0002E: An access intent configuration for application {0} is invalid: {1}
Explanation:
An application was configured with either malformed or disallowed attributes.
User Response:
Use the provided key to determine in what way the application was misconfigured. The key is defined in the user documentation. Reassemble the application with appropriate access intent attributes.
ACIN0003E: An access intent configuration for application {0} is invalid because: {1}
Explanation:
An application was configured with either malformed or disallowed attributes.
User Response:
Use the provided reason to determine in what way the application was misconfigured. Reassemble the application with appropriate access intent attributes and reinstall the application.
ACIN0004E: An access intent configuration for application {0} may be invalid: {1}
Explanation:
An application was configured with attributes that could result in the application running in an unexpected mode.
User Response:
Use the provided key to determine in what way the application may have been misconfigured. The key is defined in the user documentation. Reassemble the application with appropriate access intent attributes if necessary.
ACIN0005E: An access intent configuration for application {0} may be invalid because: {1}
Explanation:
An application was configured with attributes that could result in the application running in an unexpected mode.
User Response:
Use the provided reason to determine in what way the application may have been misconfigured. Reassemble the application with appropriate access intent attributes and reinstall the application if necessary.
ACIN0006I: The application profiling service cannot be disabled.
Explanation:
Even if the application profiling service is configured to be disabled using the admin console, the application profiling service cannot actually be disabled.
User Response:
Use the admin console tool to enable the application profiling service.
ACIN0007I: The application profiling service started successfully.
Explanation:
The application profiling service started successfully as part of the normal server startup process.
User Response:
None.
ACIN0008E: The access intent or application profiling service could not resolve the following service: {0}.
Explanation:
The access intent and application profiling services require coordination with other services to function correctly. Without those services, the access intent and application profiling service may not work correctly.
User Response:
Verify that the other is service is installed and enabled.
ACIN0009I: The application profiling service is stopping.
Explanation:
The server is shutting down and the application profiling service is stopping.
User Response:
None.
ACIN0010E: The access intent or application profiling service encountered an unexpected exception during the following: {0}.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ACIN0011W: The configuration element {0} is associated with a non-existent ejb.
Explanation:
A bean that had been configured may have been removed from the module.
User Response:
Remove the configuration element and reinstall.
ACIN0012W: Application profiling configuration can only used on an Enterprise server; some access intent policies may not be applied.
Explanation:
Application profiles are used to configure access intent policies for particular units of work. However, the application profiling configuration can only be processed on an Enterprise server; the execution of this application may not behave as desired otherwise.
User Response:
Either reconfigure the application without application profiles if appropriate and reinstall, or uninstall from the base server and only install on Enterprise servers.
ACIN0013E: The access intent interface will be unavailable to BMP entities.
Explanation:
BMP entities that programatically use the access intent service will not be able to look up the interface in naming due to previous errors.
User Response:
Determine from previous messages the problems encountered during startup. Verify that all necessary classes and packages are in the correct locations and that all prerequisit services are enabled and started.
ACIN0014I: The default access intent policy named {0} and assigned to the entity {1} was originally configured only for dynamic query.
Explanation:
An access intent policy was created in a previous version of WebSphere to act as the the default intent for dynamic queries. This configuration will be treated as the default access intent for all requests upon this entity, including dynamic query.
User Response:
Using the version of the assembly tool which was used to originally create the access intent policy for dynamic query, rename the policy to DEFAULT, then reinstall the application.
ACIN0015I: The application profiling service started; problems occurred during startup.
Explanation:
Problems were encountered while starting the application profiling service.
User Response:
Determine from previous messages the problems encountered during startup. Verify that all necessary classes and packages are in the correct locations and that all prerequisite services are enabled and started.
ACIN0016I: Some read ahead hints in the module cannot be applied.
Explanation:
Read ahead hints are an optimization that cannot be applied to all container-managed relationships.
User Response:
Determine which read ahead hints cannot be applied and remove them from the application configuration, then reinstall the application. Note that the application will run correctly without removing unapplied read ahead hints; this message may be safely ignored.
ACIN0017W: The ejb element {0} has been configured with both the access intent {1} and {2}; {2} will be used.
Explanation:
A method or entity has been configured to run with two different access intents, forcing the runtime to arbitrarily choose.
User Response:
Reconfigure the application so that no method or entity is associated with more than one access intent policy, then reinstall the application.
ACIN0018W: The j2ee element {0} has been configured with both the task name {1} and {2}; {2} will be used.
Explanation:
A method or component has been configured to run as two different task names, forcing the runtime to arbitrarily choose.
User Response:
Reconfigure the application so that no method or component is associated with more than one task, then reinstall the application.
ACIN0019W: The j2ee component {0} has configured the logical task reference {1} to both the task named {1} and the task named {2}; {2} will be used.
Explanation:
A task reference has been configured to map to more than one task, forcing the runtime to arbitrarily choose.
User Response:
Reconfigure the application so that each task reference is associated with exactly one task, then reinstall the application.
ACIN0020W: The entity {0} has been configured for the task {1} with both the access intent policies {2} and {3}; {3} will be used.
Explanation:
An entity has been configured with two different access intent policies associated with the same task, forcing the runtime to arbitrarily choose.
User Response:
Reconfigure the application so that each task is associated with at most one application profile and every entity is configured at most once with an access intent within any application profile, then reinstall the application.
ACIN0021W: Application profiles in this application will not support administration from the console.
Explanation:
The console-administered configuration settings for application profiling could not be processed. The application will execute instead according to the application's original deployment descriptors. Changes to the configuration can only be made by reassembling and resintalling the application.
User Response:
Do not use the console tool to administer your application profiling configuration. Try uninstalling and reinstalling the application to try and correct the problem.
ACIN0022E: The following application profile attribute cannot be null: {0}
Explanation:
Some configuration attributes in the application deployment descriptors are mandatory; the application may not run as desired without properly completing the configuration
User Response:
Verify that all required attributes are properly specified.
ACIN0023W: The task {0} has been configured with both the application profile {1} and {2}; {2} will be used.
Explanation:
If a task is configured on two application profiles, then the server runtime must guess which mapping to use.
User Response:
Unconfigure the task from one of the application profiles.
ACIN0024E: Could not determine the desired access intent for {0} and defaulted to {1}.
Explanation:
The appserver could not determine the correct access intent for the bean and loaded it instead with a default intent.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ACIN0025I: Some finders in the module do not support exclusive locks and will not successfully execute under some pessimistic access intent policies.
Explanation:
Some user-defined queries do not support exclusive locking of the retrieved records. Execution of those queries under access intent policies that require exclusive locks will result in an exception.
User Response:
Refer to the documentation to determine which queries do not support access intent policies that require exclusive locks. Either configure the application such that those queries will not execute with access intent policies that require exclusive locks, or rewrite the query and redeploy and reinstall the application.
ACIN0026E: An unknown access intent policy {0} is specified that cannot be resolved; {1} will be used instead.
Explanation:
The definition of a referenced access intent policy cannot be found. If the policy was defined as an Enterprise defined access intent policy and the application is run on a non-Enterprise server, the defined policy will not be available.
User Response:
Verify that the referenced access intent policy is properly defined for the version of WebSphere on which the application is executing. Remove the configured access intent policy and reconfigure the access intent using WebSphere assembly tools, then reinstall the application.
Last updated:
Library | Support | Trademarks | Feedback