Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | This is a problem generating a digital signature. |
Action | 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/ . |
Explanation | This key which is used to make a digital signature is not valid. |
Action | CSMG0002 |
Explanation | The JCE provider (Sun) needed is not installed. |
Action | 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/ . |
Explanation | The needed JCE algorithm SHA1withDSA is not available. |
Action | 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/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | There was a problem establishing a new context on the thread. We attempted to restore the original context and this has failed. |
Action | This is an unrecoverable error. Examine the logs and verify the installation. If the problem persists, contact IBM product support. |
Explanation | This primary alarm manager could not be created. This should not happen during normal operation. |
Action | This should only happen if the installation was corrupted or the installation has been damaged. Reinstall the application server. |
Explanation | 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. |
Action | 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. |
Explanation | The alarm could not be reset. |
Action | Report the problem with a test case, if possible, to IBM product support for examination. |
Explanation | The alarm could not be canceled. |
Action | Report the problem with a test case, if possible, to IBM product support for examination. |
Explanation | An unexpected exception occurred when creating an alarm. |
Action | Review the exception to determine and correct the problem. |
Explanation | An attempt to push a captured service context has failed. |
Action | Examine the service name and exception. This should only happen with WorkWithExecutionContexts which were serialized. |
Explanation | Various object pools needed by the WorkManager could not be created. |
Action | Verify that the installation is not damaged. |
Explanation | 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. |
Action | Inflate the object in a server that has the EAR containing the component. |
Explanation | An unexpected exception occurred locating the meta data for a Java Platform, Enterprise Edition component when inflating a WorkWithExecutionContext. |
Action | This is an unrecoverable error. Verify the installation is not damaged and try again. |
Explanation | Indicates the security service could not be located. |
Action | Indicates the server installation has been damaged. Reinstall. |
Explanation | An unexpected exception occurred binding an WorkManager/ObjectPoolManager in to JNDI. |
Action | Indicates a damaged installation. Reinstall and try again. |
Explanation | 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. |
Action | Determine why the message catalog could not be found. |
Explanation | The listener has already been removed or was never added. |
Action | Verify that the specified listener has been added and has not already been removed. |
Explanation | The Work Manager service has been disabled in the configuration but will continue to run because of service dependencies. |
Action | Enable the Work Manager service in the configuration to avoid receiving this message in the future. |
Explanation | 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. |
Action | Try to resolve the previously logged errors. If unable to do so, contact IBM product support. |
Explanation | The Work Manager service was started and is available to receive requests. |
Action | No user action required. |
Explanation | 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. |
Action | 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. |
Explanation | The Asynchronous Beans PMI module could not be registered with the PMI service |
Action | Verify that the product is installed correctly, and check the logs for further details. This error affects only performance data gathering. |
Explanation | The Work Manager service was successfully initialized. |
Action | No user action required. |
Explanation | The value is not valid. |
Action | Provide a value in the valid range. |
Explanation | The value is not valid. |
Action | Provide a value in the valid range. |
Explanation | An AsynchBean, Work, WorkListener, or TimerListener cannot implement javax.ejb.EnterpriseBean. It must be either a remote or local interface to an EJB. |
Action | Do not make the AsynchBean, Work, WorkListener, or TimerListener implement javax.ejb.EnterpriseBean. Make it a remote or local interface to an EJB. |
Explanation | An TimerManager or AlarmManager is not in a working state. |
Action | 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. |
Explanation | The resource reference is not configured properly. Refer to the message for the permitted values. |
Action | Use the permitted values described in the message. |
Explanation | A configuration attribute is available for this setting and is preferred over the custom property. |
Action | Migrate all configuration utilities to use the configuration attribute and avoid using this custom property. |
Explanation | A method threw an Throwable and is caught by AsynchBeans component. |
Action | Make sure the method does not throw an Throwable. |
Explanation | The resource is being looked up without using resource reference. This is not a recommended way to lookup a resource. |
Action | Configure a resource reference for this resource, and use "java:comp/env/RESOURCE_JNDI_NAME" to lookup the resource. |
Explanation | All the objects in the work item collection should implement the appropriate WorkItem interface. |
Action | Make sure all the objects in the work item collection implement the appropriate WorkItem interface. |
Explanation | A TimerManager is being looked up without using resource reference. This is not a permitted way to look up a TimerManager. |
Action | Configure a resource reference for the TimerManager, and use "java:comp/env/TIMER_MANAGER_JNDI_NAME" to lookup the TimerManager. |
Explanation | The minimum number of work threads must be configured to a value less than or equal to the maximum number of work threads. |
Action | 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. |
Explanation | 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. |
Action | The service needs to be registered before asynchronous beans is used. Contact IBM product support. |
Explanation | The interval between submitting and starting the work item exceeded the lateWorkTime threshold. |
Action | Consider allocating more work threads to the work manager, reducing the load on the system, or increasing the lateWorkTime threshold. |
Explanation | The interval between the expected and actual start time exceeded the lateAlarmTime threshold. |
Action | Consider allocating more alarm threads to the work manager, reducing the load on the system, or increasing the lateAlarmTime threshold. |
Explanation | The interval between the expected and actual start time exceeded the lateTimerTime threshold. |
Action | Consider allocating more timer threads to the timer manager, reducing the load on the system, or increasing the lateTimerTime threshold. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |