|
Asynchronous Beans messages |
|
ASYN0001E: Waiter not found in list.
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/.
ASYN0002I: Signature Exception
Explanation:
This is a problem generating a digital signature.
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/.
ASYN0003I: Invalid Key
Explanation:
This key which is used to make a digital signature is invalid.
User Response:
CSMG0002
ASYN0004I: No such JCE provider exists.
Explanation:
The JCE provider (Sun) needed is not installed.
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/.
ASYN0005I: No such JCE Algorithm (SHA1withDSA) exists.
Explanation:
The needed JCE algorithm SHA1withDSA is not available.
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/.
ASYN0006I: Context invalid exception, {1} was thrown while popping the service named {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/.
ASYN0007E: Cannot recover original context because unable to pop {0}.
Explanation:
There was a problem establishing a new context on the thread. We attempted to restore the original context and this has failed.
User Response:
This is a fatal error. Examine the logs and verify the installation. If the problem persists, contact IBM product support.
ASYN0008E: Names and intervals different lengths.
Explanation:
The two arrays passed to JMSHeartBeatPublisher have different lengths.
User Response:
This is an application problem. Fix the application so both arrays have equal lengths, and redeploy the application.
ASYN0009E: Exception {0} occurred when closing the publisher session in JMSHeartBeatPublisher.
Explanation:
There was an unexpected exception closing the JMS session.
User Response:
Check the JMS server logs to determine and correct the problem.
ASYN0010E: Cannot retreive alarm pool.
Explanation:
This primary alarm manager could not be created. This should not happen during normal operation.
User Response:
This should only happen if the installation was corrupted or the installation has been damaged. Reinstall the appserver.
ASYN0011E: AlarmImpl.init threw exception {0}.
Explanation:
The J2EE context could not be captured.
User Response:
This should only happen if the installation was corrupted or the installation has been damaged. Reinstall the appserver.
ASYN0012E: Alarm threw exception {0}.
Explanation:
If this is a WorkException then an AlarmListener threw an exception. AlarmListeners should not throw exceptions. Any other kind of exception indicates a possible bug.
User Response:
If it is a WorkException then a NOTIFICATION_EXCEPTION is fired on the associated AlarmManager. Correct the AlarmListener throwing the exception and restart the application.
ASYN0013E: Reset method threw exception {0}.
Explanation:
The alarm could not be reset.
User Response:
Report the problem with a test case, if possible, to IBM product support for examination.
ASYN0014E: Cancel method threw exception {0}.
Explanation:
The alarm could not be cancelled.
User Response:
Report the problem with a test case, if possible, to IBM product support for examination.
ASYN0015E: Cannot create Alarm Pool {0}.
Explanation:
This means an object pool for the alarm manager cannot be created.
User Response:
This indicates a corrupted or damaged installation. Reinstall the appserver. If the problem persists, then contact IBM product support.
ASYN0016E: Create getObject returned null.
Explanation:
An alarm cannot be allocated from an object pool.
User Response:
Indicates that a system class cannot be loaded and indicates a corrupt installation. Reinstall the appserver.
ASYN0017E: Create threw exception {0}.
Explanation:
An unexpected exception occurred when creating an alarm.
User Response:
Review the exception to determine and correct the problem.
ASYN0018E: ServiceContextInvalid during pop, service is {0}, exception was {1}.
Explanation:
There was a problem popping a service context. Examine the message to determine the problem.
User Response:
Examine the service and exception to determine the problem and correct it.
ASYN0019E: Attempt to push invalid service context named {0}, exception is {1}.
Explanation:
An attempt to push a captured service context has failed.
User Response:
Examine the service name and exception. This should only happen with WorkWithExecutionContexts which were serialized.
ASYN0020E: Cannot create WorkManager object pools.
Explanation:
Various object pools needed by the WorkManager could not be created.
User Response:
Verify that the installation is not damaged.
ASYN0027W: Encountered a failure in the fireAlarm method {0}.
Explanation:
An unexpected exception was encountered while processing an alarm fire event.
User Response:
Verify the installation. If the problem persists then make a test case which demonstrates the issue and contact IBM product support.
ASYN0030E: Cannot find meta data for j2eename {0}.
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.
User Response:
Inflate the object in a server that has the EAR containing the component.
ASYN0031E: The locateComponentMetaData method failed {0}.
Explanation:
An unexpected exception occurred locating the meta data for a J2EE component when inflating a WorkWithExecutionContext.
User Response:
This is a fatal error. Verify the installation is not damaged and try again.
ASYN0032E: Unexpected exception calling getXAResource.
Explanation:
An unexpected exception occurred getting the XAResource from an XASession.
User Response:
Verify the JMS installation is correct.
ASYN0033E: Unknown resource {0}.
Explanation:
A heart beat was received for an unknown resource.
User Response:
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 appserver.
ASYN0034E: JMS Exception processing heart beat {0}.
Explanation:
An unexpected exception occurred processing a heart beat message.
User Response:
Check with the JMS implementation documentation to diagnose the problem.
ASYN0035E: Exception during JMS listener subscription {0}.
Explanation:
An unexpected exception occurred registering a subscriber to the heart beat topic.
User Response:
Verify the topic exists and the JMS configuration is correct.
ASYN0036E: Failed to suspend current transaction. Exception was {0}.
Explanation:
An unexpected exception occurred suspending the transaction on the thread.
User Response:
Check the First Failure Data Capture (FFDC) and trace logs to determine the problem.
ASYN0037E: Failed to begin new transaction. Exception was {0}.
Explanation:
An unexpected exception occurred when starting a new transaction.
User Response:
Check the First Failure Data Capture (FFDC) and trace logs to determine the problem.
ASYN0038E: Failed to complete transaction. Exception was {0}.
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.
User Response:
Check the First Failure Data Capture (FFDC) and trace logs to determine the problem.
ASYN0039E: Failed to clean up local transaction. Exception was {0}.
Explanation:
An unexpected exception occurred when cleaning up the local transaction coordinator.
User Response:
Check the First Failure Data Capture (FFDC) and trace logs to determine the problem.
ASYN0040E: Failed to restore previous context. Exception was {0}.
Explanation:
The original transaction context could not be restored.
User Response:
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.
ASYN0042E: Cannot find the security service.
Explanation:
Indicates the security service could not be located.
User Response:
Indicates the server installation has been damaged. Reinstall.
ASYN0043E: IOException during JNDI operation.
Explanation:
An unexpected exception occurred binding an WorkManager/ObjectPoolManager in to JNDI.
User Response:
Indicates a damaged installation. Reinstall and try again.
ASYN0044E: Unknown action type in doPriv object. Unknown type was {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/.
ASYN0045E: JMS Resource header not found in JMS message.
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.
User Response:
Verify the topic is correct and that no other applications are mistakenly publishing messages on this topic.
ASYN0050E: Message key {0} was not found in any searched resource bundles.
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.
User Response:
Determine why the message catalog could not be found.
ASYN0051I: Listener {0} was not found for broadcaster {1}.
Explanation:
The listener has already been removed or was never added.
User Response:
Verify that the specified listener has been added and has not already been removed.
ASYN0052I: Work Manager service is disabled.
Explanation:
The Work Manager service has been disabled in the configuration, and is inaccessible on the server.
User Response:
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 appserver.
ASYN0053I: Work Manager service cannot be disabled.
Explanation:
The Work Manager service has been disabled in the configuration, but disabling this service would cause other services on the server to fail.
User Response:
Enable the Work Manager service again.
ASYN0054W: Work Manager service is disabled due to previous errors.
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.
User Response:
Try to resolve the previously logged errors. If unable to do so, contact IBM product support.
ASYN0055I: The Work Manager service started successfully.
Explanation:
The Work Manager service was started and is available to receive requests.
User Response:
No user action required.
ASYN0056I: The Work Manager service is stopping.
Explanation:
The Work Manager service is stopping and will be uanble to receive requests.
User Response:
No user action required.
ASYN0057E: Work Manager service could not resolve the {0} service.
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.
User Response:
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.
ASYN0058I: There was an error initializing Asynchronous Beans PMI .
Explanation:
The Asynchronous Beans PMI module could not be registered with the PMI service
User Response:
Verify that the product is installed correctly, and check the logs for further details. This error affects only performance data gathering.
ASYN0059I: Work Manager service initialized successfully.
Explanation:
The Work Manager service was successfuly initialized.
User Response:
No user action required.
ASYN1001I: Setting the initialState of the ABSample_PriceGenHB listener port to START.
Explanation:
NONE
User Response:
NONE
ASYN1102I: The ABSample_PriceGenHB listener port is already running.
Explanation:
NONE
User Response:
NONE
ASYN1103I: Starting the ABSample_PriceGenHB listener port
Explanation:
NONE
User Response:
NONE
ASYN1104I: The ABSample_PriceGenHB listner port is started.
Explanation:
NONE
User Response:
NONE
ASYN1105I: The appserver is running.
Explanation:
NONE
User Response:
NONE
ASYN1106I: Starting the appserver.
Explanation:
NONE
User Response:
NONE
ASYN1107I: Application server started.
Explanation:
NONE
User Response:
NONE
ASYN1108I: The JMS Server is running.
Explanation:
NONE
User Response:
NONE
ASYN1109I: Starting JMS Server.
Explanation:
NONE
User Response:
NONE
ASYN1110I: The JMS Server started.
Explanation:
NONE
User Response:
NONE
ASYN1111I: Setting the JMSServer initialState to START.
Explanation:
NONE
User Response:
NONE
ASYN1112I: Usage: wsadmin -f startSample.jacl -serverName
Explanation:
NONE
User Response:
NONE
ASYN1113I: Usage: wsadmin.sh -f startSample.jacl -serverName
Explanation:
NONE
User Response:
NONE
ASYN1114I: -serverName
Explanation:
NONE
User Response:
NONE
ASYN1115I: -nodeName
Explanation:
NONE
User Response:
NONE
ASYN1121I: Setting the JMSServer initialState to STOP.
Explanation:
NONE
User Response:
NONE
ASYN1122I: Stopping the JMS Server.
Explanation:
NONE
User Response:
NONE
ASYN1123I: JMS Server has stopped.
Explanation:
NONE
User Response:
NONE
ASYN1124I: Setting the initialState of the ABSample_PriceGenHB listener port to STOP.
Explanation:
NONE
User Response:
NONE
ASYN1125I: Stopping the ABSample_PriceGenHB listener port.
Explanation:
NONE
User Response:
NONE
ASYN1126I: The ABSample_PriceGenHB is stopped.
Explanation:
NONE
User Response:
NONE
ASYN1127I: Do you want to stop the JMS Server? Enter the number associated with the following options:
Explanation:
NONE
User Response:
NONE
ASYN1128I: [1] Stop the JMS Server.
Explanation:
NONE
User Response:
NONE
ASYN1129I: [2] Do not Stop the JMS Server.
Explanation:
NONE
User Response:
NONE
ASYN1130I: Usage: wsadmin -f stopSample.jacl -serverName
Explanation:
NONE
User Response:
NONE
ASYN1131I: Usage: wsadmin.sh -f stopSample.jacl -serverName
Explanation:
NONE
User Response:
NONE
ASYN1132I: -serverName
Explanation:
NONE
User Response:
NONE
ASYN1133I: -nodeName
Explanation:
NONE
User Response:
NONE
ASYN1140I: WebSphere Application Server Asynchronous Beans samples setup script.
Explanation:
NONE
User Response:
NONE
ASYN1141I: Connected to a managed environment.
Explanation:
NONE
User Response:
NONE
ASYN1142I: Connected to an unmanaged appserver.
Explanation:
NONE
User Response:
NONE
ASYN1143I: Saving the configuration.
Explanation:
NONE
User Response:
NONE
ASYN1144I: Server has shut down. Restart the server.
Explanation:
NONE
User Response:
NONE
ASYN1145I: Restart the server for these changes to take effect.
Explanation:
NONE
User Response:
NONE
ASYN1146I: Attempting to stop the server.
Explanation:
NONE
User Response:
NONE
ASYN1147I: Attempting to start the server.
Explanation:
NONE
User Response:
NONE
ASYN1148I: The appserver needs restarting. Do you want to stop the application server? Enter the number associated with the following options:
Explanation:
NONE
User Response:
NONE
ASYN1149I: [1] Stop the appserver.
Explanation:
NONE
User Response:
NONE
ASYN1150I: [2] Do not stop the appserver.
Explanation:
NONE
User Response:
NONE
ASYN1151I: No changes were made. The samples are ready to run.
Explanation:
NONE
User Response:
NONE
ASYN1160I: Automatic start up of the WebSphere Trader Price Generator Server is disabled.
Explanation:
NONE
User Response:
NONE
ASYN1161I: The WebSphere Trader Price Generator Server is starting.
Explanation:
NONE
User Response:
NONE
ASYN1162I: Automatic start up of the WebSphere Trader Ticker Streaming Server is disabled.
Explanation:
NONE
User Response:
NONE
ASYN1163I: The WebSphere Trader Ticker Streaming Server is starting.
Explanation:
NONE
User Response:
NONE
ASYN9999E: Unexpected Exception Occurred: {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/.
Last updated:
Library | Support | Trademarks | Feedback