Explanation | The server has started successfully and is open for e-business. |
Action | This is an informational message. No action is required. |
Explanation | The server has started, but problems occurred during server start. |
Action | Check server logs for any errors or problems. |
Explanation | The server has failed to started. |
Action | Check server logs for any errors or problems. |
Explanation | There is a mismatch between the name of the server speicified and the server name in the corresponding server.xml. |
Action | Make sure that the server name specified matches both the directory name for the server and the server name in the corresponding server.xml. |
Explanation | The server has started recovery. |
Action | This is an informational message. No action is required. |
Explanation | The server has recovered and is stopping. |
Action | This is an informational message. No action is required. |
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 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 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 server has started recovery. Problems occurred during startup. |
Action | Check server logs for any errors or problems. |
Explanation | A variable used in the classpath definition of the resource is not defined or does not contain a valid value. |
Action | Define the missing variable or provide a valid value for the missing variable. |
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 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 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 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 | A variable used in the native path definition of the resource is not defined or does not contain a valid value. |
Action | Define the missing variable or provide a valid value for the missing variable. |
Explanation | A variable used in the resource is not defined or does not contain a valid value. |
Action | Define the missing variable or provide a valid value for the missing variable. |
Explanation | The server is stopped. |
Action | This is an informational message. No action is required. |
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 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 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 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 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 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 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 specified EJB jar is being started as part of normal application start activities. |
Action | None. |
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 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 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 specified EJB jar is being stopped as part of application shutdown activities. |
Action | None. |
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 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 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 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 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 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 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 | Binding resource, {0}, with JNDI name, {1}. |
Action | This is an informational message. No action is required. |
Explanation | The server has aborted the attempt of registering a URL Provider with null protocol. |
Action | Please check the configuration of the URL Provider. |
Explanation | The server has aborted the attempt of unregistering a URL Provider with null protocol. |
Action | Please check the configuration of the URL Provider. |
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 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 specified EJB jar has been started as part of normal application start activities. |
Action | None. |
Explanation | The default option to defer EJB initialization has been disabled, therefore all EJBs will be initialized during application start. |
Action | None. |
Explanation | The specified EJB jar has been stopped as part of application shutdown activities. |
Action | None. |
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 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 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 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 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 | An error has occurred during the initialization and start of an EnterpriseBean {0}. |
Action | Take action recommended in the message associated with exception {1}. |
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 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 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 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 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 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 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 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 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 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 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 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 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 EJB Timer Service has been disabled by configuring the number of threads to zero, EJBs implementing the javax.ejb.TimedObject interface will not function properly. |
Action | If the EJB Timer Service is to be used on this node it must be enabled by setting the number of threads greater than zero. |
Explanation | The EJB Timer Service may not be configured properly. |
Action | Verify the EJB Timer Service is configured properly. |
Explanation | Configured poll interval for the EJB Timer Service is not set properly. |
Action | Change the configured poll interval for the EJB Timer Service to a supported value. |
Explanation | Configured number of threads for the EJB Timer Service is not set properly. |
Action | Change the configured number of threads for the EJB Timer Service to a supported value. |
Explanation | The MessageDrivenBean Message Listener has been disabled by either not installing or disabling the Messaging Service, EJBs implementing the javax.ejb.MessageDrivenBean interface will not function properly. |
Action | If MessageDrivenBeans are to be used on this node a Messaging Service must be installed and enabled. |
Explanation | The WebSphere RemoteObject cache size has been set based on the system property "com.ibm.websphere.RemoteObjectCacheSize". |
Action | No action required. |
Explanation | A WebSphere RemoteObject cache size was specified using the system property "com.ibm.websphere.RemoteObjectCacheSize", but the value specified was not within the valid range. |
Action | Change the RemoteObject cache size system property to a valid value. |
Explanation | A WebSphere RemoteObject cache size was specified using the system property "com.ibm.websphere.RemoteObjectCacheSize", but the value specified was not a valid integer. |
Action | Change the RemoteObject cache size system property to a valid integer. |
Explanation | The multibroker domain service may be disabled. |
Action | Verify the multibroker domain service is enabled. |
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 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 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 | Starting application, {0}. |
Action | This is an informational message. No action is required. |
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 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 application {0} has the specified application build level {1}. |
Action | This is an informational message. No action is required. |
Explanation | The application {0} does not have a specified application build level. |
Action | This is an informational message. No action is required. |
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 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 | Another edition of the application is running so the specified edition of the application cannot be started. |
Action | Stop the edition of the application that is running and start the specified edition again. |
Explanation | An EJB jar has failed to start. |
Action | Look for error messages that appear between this message and the preeceeding WSVR0037I message. If you find one, it may be related to the cause of this message. If none is found, use the exception that appears as part of this message as a possible cause of this message. |
Explanation | An EJB has failed to start. |
Action | Verify the EJB jar that contains the failed EJB {1} has been deployed and look for error messages that appear between this message and the preeceeding WSVR0037I message. |
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 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 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 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 application {0} has already been initialized. This would occur if the application has already been started. |
Action | Verify the application {0} has not already been started. |
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 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 | Application, {0}, is stopping |
Action | This is an informational message. No action is required. |
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 | Application, {0}, is disabled and thus not started. |
Action | This is an informational message. No action is required. |
Explanation | Application, {0}, is stopped. |
Action | This is an informational message. No action is required. |
Explanation | Application, {0}, is started. |
Action | This is an informational message. No action is required. |
Explanation | The WAR classloader scope prohibits module stop operations. |
Action | The WAR classloader scope must be set such as to provide a isolated WAR classloader. |
Explanation | Stop operations are not allowed on modules of this type. |
Action | Perform the stop operation on the appplication instead. |
Explanation | Start operations are not allowed on modules of this type. |
Action | Perform the start operation on the appplication instead. |
Explanation | An MBean or AdminConsole request to start or update a module is being processed. |
Action | This is an informational message. No action is required. |
Explanation | An MBean or AdminConsole request to start or update a module has successfully been processed. |
Action | This is an informational message. No action is required. |
Explanation | An MBean or AdminConsole request to stop a module is being processed, this may be occuring as the result of application update. |
Action | This is an informational message. No action is required. |
Explanation | An MBean or AdminConsole request to stop a module has successfully been processed. |
Action | This is an informational message. No action is required. |
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 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 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 | An undefined WebSphere variable was encountered while parsing a string. This variable may be optional. |
Action | Define the WebSphere variable if it is not optional. If variable substitution is not intended, then $$ should be used as escape sequence. Otherwise, use the correct syntax like ${VAR_NAME}. |
Explanation | An unterminated WebSphere variable reference was encountered while parsing a string, meaning a closing parenthesis is missing in the string definition. |
Action | Verify the string definition for any unterminated WebSphere variable reference with missing parenthesis. |
Explanation | A recursive WebSphere variable reference was encountered while parsing a string, meaning a variable is referenced recursively in a variable definition. |
Action | Check for any recursive WebSphere variable references in the WebSphere variable configuration. |
Explanation | The message listener service may be disabled. |
Action | Verify the message listener service is enabled. |
Explanation | The maximum size must be greater tha zero, and also greater than or equal to the minimum size. |
Action | Verify (via the admin console) the maximum and minimum size of the threadpool are specified correctly. |
Explanation | When a web module deployment contains a classloader, the classloading mode of that classloader takes precedence over the deprecated classloading mode of the web module itself. |
Action | The configuration is usable. However, to stop receiving this message, update the classloading mode of the web module to match the classloading mode of the contained classloader. Also, be aware of the deprecation of the web module deployment classloading mode. |
Explanation | The configuration model allows a classloader to be contained by module deployments other than web module deployments. Classloaders contained by module deployments other than web module deployments have no effect. |
Action | The configuration is usable. No configuration update is required. However, to stop receiving this message, remove the classloader that is contained by the noted module deployment. |
Explanation | There may be a problem with the permissions associated with this directory. |
Action | Verify the permissions on this directory. |
Explanation | The com.ibm.websphere.classloader.plugin system property has been set. The class that is specified by this system property is capable of modifying the bytecodes of application classes. This message is for informational purposes only. |
Action | No action is required. |
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 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 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 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 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 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 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 | Only Web-Components and EJB-Components support access to the javaNameSpace. |
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 | 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 | A thread has been active for an extended period. This may indicate that the thread is hung, including deadlock and infinite loop situations. |
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 | A thread that was previously reported as hung has now completed. |
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 | This error indicates that a CMP which is configured to use a Connection Factory resource is not available. The CMP bean will not function because the resource is not defined by the administrator. |
Action | Create this Connection Factory by ensuring this data source is selected for CMP use in the administrative console. |
Explanation | The thread pool associated with server startup could not be found in the configuration. |
Action | Configure a thread pool with the name given in the warning message. |
Explanation | The com.ibm.websphere.threadpool.clearThreadLocal property is still used in this release, but will be removed in a future release. |
Action | Remove the com.ibm.websphere.threadpool.clearThreadLocal property from the Java Virtual Machine (JVM) properties. |
Explanation | The server has completed recovery and has stopped. |
Action | This is an informational message. No action is required. |
Explanation | The server had problems during recovery and has stopped. |
Action | Examine the log files to see what failure messages were recorded there. |
Explanation | The ObjectRequestBroker service ThreadPool has been replaced by a ThreadPoolManager service ThreadPool with the same name. |
Action | This value is still used in this release, but will be removed in a future release. You may update the ThreadPoolManager service ThreadPool configuration to match the ObjectRequestBroker service configuration and remove the ObjectRequestBroker service configuration. |
Explanation | The ORB was unable to acquire a thread to process a request. |
Action | Reduce traffic to the server, increase the ORB thread pool size, or increase the value of the com.ibm.websphere.orb.threadPoolTimeout ORB custom property. |
Explanation | The directory is meant to be used for temporary patches. Classes contained in this directory will override WebSphere classes. |
Action | Verify that the classes contained in the directory are compatible with the version of WebSphere installed. |