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 | This is a problem generating a digital signature. |
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 | This key which is used to make a digital signature is invalid. |
Action | CSMG0002 |
Explanation | The JCE provider (Sun) needed is not installed. |
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 | The needed JCE algorithm SHA1withDSA is not available. |
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 | 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 | 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 a fatal error. Examine the logs and verify the installation. If the problem persists, contact IBM product support. |
Explanation | The two arrays passed to JMSHeartBeatPublisher have different lengths. |
Action | This is an application problem. Fix the application so both arrays have equal lengths, and redeploy the application. |
Explanation | There was an unexpected exception closing the JMS session. |
Action | Check the JMS server logs to determine and correct the problem. |
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 | The J2EE context could not be captured. |
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 cancelled. |
Action | Report the problem with a test case, if possible, to IBM product support for examination. |
Explanation | This means an object pool for the alarm manager cannot be created. |
Action | This indicates a corrupted or damaged installation. Reinstall the application server. If the problem persists, then contact IBM product support. |
Explanation | An alarm cannot be allocated from an object pool. |
Action | Indicates that a system class cannot be loaded and indicates a corrupt installation. Reinstall the application server. |
Explanation | An unexpected exception occurred when creating an alarm. |
Action | Review the exception to determine and correct the problem. |
Explanation | There was a problem popping a service context. Examine the message to determine the problem. |
Action | Examine the service and exception to determine the problem and correct it. |
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 | An unexpected exception was encountered while processing an alarm fire event. |
Action | Verify the installation. If the problem persists then make a test case which demonstrates the issue and contact IBM product support. |
Explanation | A WorkWithExecutionContext was created using the named J2EE 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 J2EE component when inflating a WorkWithExecutionContext. |
Action | This is a fatal error. Verify the installation is not damaged and try again. |
Explanation | An unexpected exception occurred getting the XAResource from an XASession. |
Action | Verify the JMS installation is correct. |
Explanation | A heart beat was received for an unknown resource. |
Action | This may not be a problem. It just means a resource is publishing heart beat messages and there is no corresponding subsystem monitor on this application server. |
Explanation | An unexpected exception occurred processing a heart beat message. |
Action | Check with the JMS implementation documentation to diagnose the problem. |
Explanation | An unexpected exception occurred registering a subscriber to the heart beat topic. |
Action | Verify the topic exists and the JMS configuration is correct. |
Explanation | An unexpected exception occurred suspending the transaction on the thread. |
Action | Check the First Failure Data Capture (FFDC) and trace logs to determine the problem. |
Explanation | An unexpected exception occurred when starting a new transaction. |
Action | Check the First Failure Data Capture (FFDC) and trace logs to determine the problem. |
Explanation | A global transaction was present that had not been committed or rolled back by the application. An unexpected exception occurred when the runtime tried to roll back this exception. |
Action | Check the First Failure Data Capture (FFDC) and trace logs to determine the problem. |
Explanation | An unexpected exception occurred when cleaning up the local transaction coordinator. |
Action | Check the First Failure Data Capture (FFDC) and trace logs to determine the problem. |
Explanation | The original transaction context could not be restored. |
Action | A very long lived doWork could cause a transaction timeout on the transaction which is active when doWork was called. When doWork finally returns, the original transaction may have timed out. |
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 | 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 | The JMS header resource was not present in the message. The wrong topic is being used or another application is publishing messages on this topic. |
Action | Verify the topic is correct and that no other applications are mistakenly publishing messages on this topic. |
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, and is 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 Work Manager service has been disabled in the configuration but will continue to run because 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 is stopping and will be uanble 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, please 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 successfuly 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 right. Please 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 utlities 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 | 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/. |