PMI_INIT_ERROR=ASYN0058I: There was an error initializing Asynchronous Beans PMI . The Asynchronous Beans PMI module could not be registered with the PMI service Verify that the product is installed correctly, and check the logs for further details. This error affects only performance data gathering. INVALID_TIMERMANAGER_STATE=ASYN0063E: The {0} is in {1} state. An TimerManager or AlarmManager is not in a working state. If the TimerManager or AlarmManager is in Stop or Stopping state, get a new AlarmManager or TimerManager. If the TimerManager is in Suspended or Suspending state, resume the TimerManager before scheduling a Timer. ASYN0093.operation.not.supported=ASYN0093E: The operation {0} is not supported. The specified operation is not supported. Update the application such that it no longer attempts to perform the unsupported operation. NO_RESREF_INFO=ASYN0067I: Resource {0} is being looked up without using resource reference. The resource is being looked up without using resource reference. This is not a recommended way to lookup a resource. Configure a resource reference for this resource, and use "java:comp/env/RESOURCE_JNDI_NAME" to lookup the resource. RESREF_ERROR=ASYN0064E: The value {0} of the {1} resource reference element {2} is not right. Only the following values are allowed: {3}. The resource reference is not configured properly. Refer to the message for the permitted values. Use the permitted values described in the message. MSG_KEY_46=ASYN0020E: Cannot create WorkManager object pools. Various object pools needed by the WorkManager could not be created. Verify that the installation is not damaged. MSG_KEY_45=ASYN0019E: Attempt to push invalid service context named {0}, exception is {1}. An attempt to push a captured service context has failed. Examine the service name and exception. This should only happen with WorkWithExecutionContexts which were serialized. MSG_KEY_43=ASYN0017E: Create threw exception {0}. An unexpected exception occurred when creating an alarm. Review the exception to determine and correct the problem. MSG_KEY_40=ASYN0014E: Cancel method threw exception {0}. The alarm could not be canceled. Report the problem with a test case, if possible, to IBM product support for examination. MSG_KEY_UNEX_EXCEPT=ASYN9999E: Unexpected Exception Occurred: {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ASYN0090_LATE_WORK=ASYN0090I: Work manager {0} is running work item {1} later than expected. The work item was submitted at {2} and is starting to run at {3}. The interval between submitting and starting the work item exceeded the lateWorkTime threshold. Consider allocating more work threads to the work manager, reducing the load on the system, or increasing the lateWorkTime threshold. MIN_MAX_ERROR=ASYN0070E: The minimum number of work threads, {0}, cannot be configured higher than the maximum number of work threads, {1}. The minimum number of work threads must be configured to a value less than or equal to the maximum number of work threads. Reconfigure the minimum number of work threads, the maximum number of work threads, or both, such that the minimum number of work threads is less than or equal to the maximum number of work threads. ERR_MISSING_KEY=ASYN0050E: Message key {0} was not found in any searched resource bundles. A key was passed into the Messages 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. Determine why the message catalog could not be found. ASYN0091_LATE_ALARM=ASYN0091I: Work manager {0} is running alarm {1} later than expected. The scheduled time at which the alarm was expected to run is {2}, but instead the alarm is running at {3}. The interval between the expected and actual start time exceeded the lateAlarmTime threshold. Consider allocating more alarm threads to the work manager, reducing the load on the system, or increasing the lateAlarmTime threshold. INVALID_VALUE_2=ASYN0061E: The value {0} is not valid for {1}. The value is not valid. Provide a value in the valid range. MSG_KEY_39=ASYN0013E: Reset method threw exception {0}. The alarm could not be reset. Report the problem with a test case, if possible, to IBM product support for examination. NO_RESREF_ERROR=ASYN0069E: TimerManager {0} is being looked up without using resource reference. A TimerManager is being looked up without using resource reference. This is not a permitted way to look up a TimerManager. Configure a resource reference for the TimerManager, and use "java:comp/env/TIMER_MANAGER_JNDI_NAME" to lookup the TimerManager. MSG_KEY_38=ASYN0012E: Alarm/Timer threw exception {0}. If this is a WorkException then an AlarmListener/TimerListener threw an exception. AlarmListeners or TimerListeners should not throw exceptions. Any other kind of exception indicates a possible bug. If it is a WorkException then a NOTIFICATION_EXCEPTION is fired on the associated AlarmManager or TimerManager. Correct the AlarmListener or TimerListener throwing the exception and restart the application. MSG_KEY_36=ASYN0010E: Cannot retreive alarm pool. This primary alarm manager could not be created. This should not happen during normal operation. This should only happen if the installation was corrupted or the installation has been damaged. Reinstall the application server. WORKMANAGER_STARTED=ASYN0055I: The Work Manager service started successfully. The Work Manager service was started and is available to receive requests. No user action required. WORKMANAGER_DISABLED=ASYN0054W: Work Manager service is disabled due to previous errors. The Work Manager service experienced an error during initialization. The service will be inaccessible on the given server. The root error should have been logged previously. Try to resolve the previously logged errors. If unable to do so, contact IBM product support. MSG_KEY_28=ASYN0007E: Cannot recover original context because unable to pop {0}. There was a problem establishing a new context on the thread. We attempted to restore the original context and this has failed. This is an unrecoverable error. Examine the logs and verify the installation. If the problem persists, contact IBM product support. MSG_KEY_26=ASYN0006I: Context invalid exception, {1} was thrown while popping the service named {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ASYN0059I=ASYN0059I: Work Manager service initialized successfully. The Work Manager service was successfully initialized. No user action required. WORKMANAGER_CANNOT_BE_DISABLED=ASYN0053I: Work Manager service cannot be disabled. The Work Manager service has been disabled in the configuration but will continue to run because of service dependencies. Enable the Work Manager service in the configuration to avoid receiving this message in the future. INVALID_VALUE=ASYN0060E: The value {0} is not valid for {1}. The valid values are: {2}. The value is not valid. Provide a value in the valid range. INVALID_ITEM_IN_COLLECTION=ASYN0068E: The object {0} in the work item collection is not a {1} object. All the objects in the work item collection should implement the appropriate WorkItem interface. Make sure all the objects in the work item collection implement the appropriate WorkItem interface. ASYN0092_LATE_TIMER=ASYN0092I: Timer manager {0} is running timer {1} later than expected. The scheduled time at which the timer was expected to run is {2}, but instead the timer is running at {3}. The interval between the expected and actual start time exceeded the lateTimerTime threshold. Consider allocating more timer threads to the timer manager, reducing the load on the system, or increasing the lateTimerTime threshold. MSG_KEY_19=ASYN0005I: No such JCE Algorithm (SHA1withDSA) exists. The needed JCE algorithm SHA1withDSA is not available. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . MSG_KEY_18=ASYN0004I: No such JCE provider exists. The JCE provider (Sun) needed is not installed. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . MSG_KEY_17=ASYN0003I: Invalid Key This key which is used to make a digital signature is not valid. CSMG0002 MSG_KEY_16=ASYN0002I: Signature Exception This is a problem generating a digital signature. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . MSG_INFO_LISTENER_NOT_FOUND=ASYN0051I: Listener {0} was not found for broadcaster {1}. The listener has already been removed or was never added. Verify that the specified listener has been added and has not already been removed. ERR_NO_SERVICE=ASYN0057E: Work Manager service could not resolve the {0} service. The Work Manager service could not resolve the specified service, which is required for the Work Manager service. Look through the log to determine the specified service started successfully. If you wish to use the Work Manager service, correct the problem with the specified service. If you are unable to correct the problem, contact IBM product support. MSG_KEY_08=ASYN0001E: Waiter not found in list. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SERVICE_REGISTERED_TOO_LATE=ASYN0080W: Registration of the {0} service might not be honored because the service was registered after asynchronous beans was used. When asynchronous beans is used, it processes the list of registered services. If a service is registered after this point, the registration might not be honored. The service needs to be registered before asynchronous beans is used. Contact IBM product support. MSG_KEY_60=ASYN0043E: IOException during JNDI operation. An unexpected exception occurred binding an WorkManager/ObjectPoolManager in to JNDI. Indicates a damaged installation. Reinstall and try again. CUSTOM_PROPERTY_WARNING=ASYN0065W: The custom property {0} has been deprecated. Please use a cooresponding configuration attribute. A configuration attribute is available for this setting and is preferred over the custom property. Migrate all configuration utilities to use the configuration attribute and avoid using this custom property. METHOD_THROW_THROWABLE=ASYN0066E: The method {0} threw an Throwable: {1}. A method threw an Throwable and is caught by AsynchBeans component. Make sure the method does not throw an Throwable. MSG_KEY_59=ASYN0042E: Cannot find the security service. Indicates the security service could not be located. Indicates the server installation has been damaged. Reinstall. MSG_KEY_57=ASYN0031E: The locateComponentMetaData method failed {0}. An unexpected exception occurred locating the meta data for a Java Platform, Enterprise Edition component when inflating a WorkWithExecutionContext. This is an unrecoverable error. Verify the installation is not damaged and try again. MSG_KEY_56=ASYN0030E: Cannot find meta data for j2eename {0}. A WorkWithExecutionContext was created using the named Java Platform, Enterprise Edition component. An attempt was made to serialize and then inflate this in an EAR which the component does not exist. Inflate the object in a server that has the EAR containing the component. ASYNCHBEAN_CANNOT_BE_ENTERPRISEBEAN=ASYN0062E: {0} cannot be an Enterprise Bean. It must be either a remote or local interface to an EJB. An AsynchBean, Work, WorkListener, or TimerListener cannot implement javax.ejb.EnterpriseBean. It must be either a remote or local interface to an EJB. Do not make the AsynchBean, Work, WorkListener, or TimerListener implement javax.ejb.EnterpriseBean. Make it a remote or local interface to an EJB.