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. |
Action | Determine why the message catalog could not be found. |
Explanation | An application was configured with either malformed or disallowed attributes. |
Action | 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. |
Explanation | An application was configured with either malformed or disallowed attributes. |
Action | 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. |
Explanation | An application was configured with attributes that could result in the application running in an unexpected mode. |
Action | 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. |
Explanation | An application was configured with attributes that could result in the application running in an unexpected mode. |
Action | 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. |
Explanation | Even if the application profiling service is configured to be disabled using the admin console, the application profiling service cannot actually be disabled. |
Action | Use the admin console tool to enable the application profiling service. |
Explanation | The application profiling service started successfully as part of the normal server startup process. |
Action | None. |
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. |
Action | Verify that the other is service is installed and enabled. |
Explanation | The server is shutting down and the application profiling service is stopping. |
Action | None. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | A bean that had been configured may have been removed from the module. |
Action | Remove the configuration element and reinstall. |
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. |
Action | Either reconfigure the application without application profiles if appropriate and reinstall, or uninstall from the base server and only install on Enterprise servers. |
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. |
Action | 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. |
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. |
Action | 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. |
Explanation | Problems were encountered while starting the application profiling service. |
Action | 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. |
Explanation | Read ahead hints are an optimization that cannot be applied to all container-managed relationships. |
Action | 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. |
Explanation | A method or entity has been configured to run with two different access intents, forcing the runtime to arbitrarily choose. |
Action | Reconfigure the application so that no method or entity is associated with more than one access intent policy, then reinstall the application. |
Explanation | A method or component has been configured to run as two different task names, forcing the runtime to arbitrarily choose. |
Action | Reconfigure the application so that no method or component is associated with more than one task, then reinstall the application. |
Explanation | A task reference has been configured to map to more than one task, forcing the runtime to arbitrarily choose. |
Action | Reconfigure the application so that each task reference is associated with exactly one task, then reinstall the application. |
Explanation | An entity has been configured with two different access intent policies associated with the same task, forcing the runtime to arbitrarily choose. |
Action | 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. |
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. |
Action | Do not use the console tool to administer your application profiling configuration. Try uninstalling and reinstalling the application to try and correct the problem. |
Explanation | Some configuration attributes in the application deployment descriptors are mandatory; the application may not run as desired without properly completing the configuration |
Action | Verify that all required attributes are properly specified. |
Explanation | If a task is configured on two application profiles, then the server runtime must guess which mapping to use. |
Action | Unconfigure the task from one of the application profiles. |
Explanation | The application server could not determine the correct access intent for the bean and loaded it instead with a default intent. |
Action | 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/. |
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. |
Action | 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. |
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. |
Action | 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. |
Explanation | Method-level access intent is configured within the specified application. Method-level access intent is deprecated. |
Action | Reconfigure the application using application profiling. |
Explanation | The specified application is configured to require the Application Profiling service, but the Application Profiling service is not enabled. |
Action | Enable the Application Profiling service before starting the specified application that is configured for application profiling. |
Explanation | The specified application will run in 5.x compatibility mode. The 5.x compatibility mode is deprecated. |
Action | Verify that all J2EE 1.3 applications on this server that use application profiling execute properly with Application Profiling 5.x Compatibility Mode disabled, then configure the Application Profiling service to not use 5.x Compatibility Mode. |
Explanation | The Application Profiling service has been disabled in the configuration, and it will be inaccessible on the server. |
Action | Disabling this service may cause other services on the server to fail. If you wish to enable the service, use the Administrative Console to configure services on this application server. |
Explanation | The specified application is configured to require the Application Profiling service, but it is installed and starting on a running server that enables Application Profiling 5.x Compatibility Mode. |
Action | Re-start the server. |
Explanation | The specified application is configured to require the Application Profiling service. The ibm-application-ext-pme.xmi file is created for this application. |
Action | None. |
Explanation | The specified application is not configured to require the Application Profiling service. The ibm-application-ext-pme.xmi file is not created for this application. |
Action | None. |
Explanation | The specified application is configured to require the Application Profiling service. The ibm-application-ext-pme.xmi file should be created for this application during installation. However, the file creation failed. It could be beccuse of Application profiling configuration problems in ejb modules. |
Action | Check Application profiling configuration in ejb modules of this application. |