WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


ASYN

ASYN0001E: Waiter not found in list.
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/.
ASYN0002I: Signature Exception
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/.
ASYN0003I: Invalid Key
Explanation This key which is used to make a digital signature is invalid.
Action CSMG0002
ASYN0004I: No such JCE provider exists.
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/.
ASYN0005I: No such JCE Algorithm (SHA1withDSA) exists.
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/.
ASYN0006I: Context invalid exception, {1} was thrown while popping the service named {0}.
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/.
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.
Action 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.
Action 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.
Action 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.
Action This should only happen if the installation was corrupted or the installation has been damaged. Reinstall the application server.
ASYN0011E: AlarmImpl.init threw exception {0}.
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.
ASYN0012E: Alarm/Timer threw exception {0}.
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.
ASYN0013E: Reset method threw exception {0}.
Explanation The alarm could not be reset.
Action 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.
Action 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.
Action This indicates a corrupted or damaged installation. Reinstall the application server. If the problem persists, then contact IBM product support.
ASYN0016E: Create getObject returned null.
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.
ASYN0017E: Create threw exception {0}.
Explanation An unexpected exception occurred when creating an alarm.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action Verify the JMS installation is correct.
ASYN0033E: Unknown resource {0}.
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.
ASYN0034E: JMS Exception processing heart beat {0}.
Explanation An unexpected exception occurred processing a heart beat message.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
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.
ASYN0042E: Cannot find the security service.
Explanation Indicates the security service could not be located.
Action 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.
Action 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.
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/.
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.
Action 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.
Action 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.
Action 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.
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.
ASYN0053I: Work Manager service cannot be disabled.
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.
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.
Action 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.
Action 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.
Action 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.
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.
ASYN0058I: There was an error initializing Asynchronous Beans PMI .
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.
ASYN0059I: Work Manager service initialized successfully.
Explanation The Work Manager service was successfuly initialized.
Action No user action required.
ASYN0060E: The value {0} is not valid for {1}. The valid values are: {2}.
Explanation The value is not valid.
Action Provide a value in the valid range.
ASYN0061E: The value {0} is not valid for {1}.
Explanation The value is not valid.
Action Provide a value in the valid range.
ASYN0062E: {0} cannot be an Enterprise Bean. It must be either a remote or local interface to an EJB.
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.
ASYN0063E: The {0} is in {1} state.
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.
ASYN0064E: The value {0} of the {1} resource reference element {2} is not right. Only the following values are allowed: {3}.
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.
ASYN0065W: The custom property {0} has been deprecated. Please use a cooresponding configuration attribute.
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.
ASYN0066E: The method {0} threw an Throwable: {1}.
Explanation A method threw an Throwable and is caught by AsynchBeans component.
Action Make sure the method does not throw an Throwable.
ASYN0067I: Resource {0} is being looked up without using resource reference.
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.
ASYN0068E: The object {0} in the work item collection is not a {1} object.
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.
ASYN0069E: TimerManager {0} is being looked up without using resource reference.
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.
ASYN0070E: The minimum number of work threads, {0}, cannot be configured higher than the maximum number of work threads, {1}.
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.
ASYN1001I: Setting the initialState of the ABSample_PriceGenHB listener port to START.
Explanation NONE
Action NONE
ASYN1102I: The ABSample_PriceGenHB listener port is already running.
Explanation NONE
Action NONE
ASYN1103I: Starting the ABSample_PriceGenHB listener port
Explanation NONE
Action NONE
ASYN1104I: The ABSample_PriceGenHB listner port is started.
Explanation NONE
Action NONE
ASYN1105I: The application server is running.
Explanation NONE
Action NONE
ASYN1106I: Starting the application server.
Explanation NONE
Action NONE
ASYN1107I: Application server started.
Explanation NONE
Action NONE
ASYN1108I: The JMS Server is running.
Explanation NONE
Action NONE
ASYN1109I: Starting JMS Server.
Explanation NONE
Action NONE
ASYN1110I: The JMS Server started.
Explanation NONE
Action NONE
ASYN1111I: Setting the JMSServer initialState to START.
Explanation NONE
Action NONE
ASYN1112I: Usage: wsadmin -f startSample.jacl -serverName <server name> -nodeName <node name>
Explanation NONE
Action NONE
ASYN1113I: Usage: wsadmin.sh -f startSample.jacl -serverName <server name> -nodeName <node name>.
Explanation NONE
Action NONE
ASYN1114I: -serverName <server name>, where server name is the name of the application server is running on.
Explanation NONE
Action NONE
ASYN1115I: -nodeName <node name>, where node name is the name of the node the application server is running on.
Explanation NONE
Action NONE
ASYN1121I: Setting the JMSServer initialState to STOP.
Explanation NONE
Action NONE
ASYN1122I: Stopping the JMS Server.
Explanation NONE
Action NONE
ASYN1123I: JMS Server has stopped.
Explanation NONE
Action NONE
ASYN1124I: Setting the initialState of the ABSample_PriceGenHB listener port to STOP.
Explanation NONE
Action NONE
ASYN1125I: Stopping the ABSample_PriceGenHB listener port.
Explanation NONE
Action NONE
ASYN1126I: The ABSample_PriceGenHB is stopped.
Explanation NONE
Action NONE
ASYN1127I: Do you want to stop the JMS Server? Enter the number associated with the following options:
Explanation NONE
Action NONE
ASYN1128I: [1] Stop the JMS Server.
Explanation NONE
Action NONE
ASYN1129I: [2] Do not Stop the JMS Server.
Explanation NONE
Action NONE
ASYN1130I: Usage: wsadmin -f stopSample.jacl -serverName <server name> -nodeName <node name>
Explanation NONE
Action NONE
ASYN1131I: Usage: wsadmin.sh -f stopSample.jacl -serverName <server name> -nodeName <node name>.
Explanation NONE
Action NONE
ASYN1132I: -serverName <server name> where server name is the name of the application server is running on.
Explanation NONE
Action NONE
ASYN1133I: -nodeName <node name> where node name is the name of the node the application server is running on.
Explanation NONE
Action NONE
ASYN1140I: WebSphere Application Server Asynchronous Beans samples setup script.
Explanation NONE
Action NONE
ASYN1141I: Connected to a managed environment.
Explanation NONE
Action NONE
ASYN1142I: Connected to an unmanaged application server.
Explanation NONE
Action NONE
ASYN1143I: Saving the configuration.
Explanation NONE
Action NONE
ASYN1144I: Server has shut down. Restart the server.
Explanation NONE
Action NONE
ASYN1145I: Restart the server for these changes to take effect.
Explanation NONE
Action NONE
ASYN1146I: Attempting to stop the server.
Explanation NONE
Action NONE
ASYN1147I: Attempting to start the server.
Explanation NONE
Action NONE
ASYN1148I: The application server needs restarting. Do you want to stop the application server? Enter the number associated with the following options:
Explanation NONE
Action NONE
ASYN1149I: [1] Stop the application server.
Explanation NONE
Action NONE
ASYN1150I: [2] Do not stop the application server.
Explanation NONE
Action NONE
ASYN1151I: No changes were made. The samples are ready to run.
Explanation NONE
Action NONE
ASYN1160I: Automatic start up of the WebSphere Trader Price Generator Server is disabled.
Explanation NONE
Action NONE
ASYN1161I: The WebSphere Trader Price Generator Server is starting.
Explanation NONE
Action NONE
ASYN1162I: Automatic start up of the WebSphere Trader Ticker Streaming Server is disabled.
Explanation NONE
Action NONE
ASYN1163I: The WebSphere Trader Ticker Streaming Server is starting.
Explanation NONE
Action NONE
ASYN9999E: Unexpected Exception Occurred: {0}.
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/.
Reference topic    

Terms of Use | Feedback

Last updated: May 3, 2010 12:35:57 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.asynchbeans.AsynchBeansMessages.html

© Copyright IBM Corporation 2006, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)