WSVR0059I=WSVR0059I: EJB jar stopped: {0} The specified Enterprise JavaBean (EJB) JAR file has been stopped as part of application shutdown activities. No action is required. WSVR0167E=WSVR0167E: The name attribute value should be either component or service in the dependency element definition for the {0} component-id value for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0022W=WSVR0022W: The value, {0}, with Resource ID, {1}, located at {2} has an invalid variable A variable used in the resource is not defined or does not contain a valid value. Define the missing variable or provide a valid value for the missing variable. WSVR0058I=WSVR0058I: All EJBs will be initialized during application start The default option to defer Enterprise JavaBeans (EJB) initialization has been disabled. All Enterprise JavaBeans (EJBs) will be initialized during the application startup process. No action is required. WSVR0166E=WSVR0166E: The type attribute value should be either component or service in the dependency element definition for the {0} component type for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0021W=WSVR0021W: Native path entry, {0}, in Resource, {1}, located at {2} has an invalid variable A variable used in the native path definition of the resource is not defined or does not contain a valid value. Define the missing variable or provide a valid value for this variable. WSVR0057I=WSVR0057I: EJB jar started: {0} The specified Enterprise JavaBeans (EJB) JAR file has been started as part of normal application startup activities. No action is required. WSVR0165E=WSVR0165E: The type attribute value should be either component or service in the dependency element definition for the {0} class for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0020W=WSVR0020W: CustomService, {0}, failed to shutdown. {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0056W=WSVR0056W: Tie class of {0} can not be found. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0164E=WSVR0164E: The type attribute value should be either component or service in the dependency element definition for the {0} component-id value for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0055W=WSVR0055W: Unexpected objectToKey method callback for object {0}. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0228I=WSVR0228I: User initiated module stop operation request completed on Module, {1}, of application, {0} A managed bean (MBean) or an administrative console request to stop a module has successfully completed. No action is required. WSVR0119W=WSVR0119W: Unable to find MultibrokerDomain service, stateful session bean failover will not occur. The multibroker domain service might be disabled. Verify that the multibroker domain service is enabled. WSVR0163E=WSVR0163E: A type attribute is missing within the dependency element definition for the {0} component type for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0068=WSVR0068E: Attempt to start EnterpriseBean {0} failed with exception: {1} An error has occurred during the initialization and start of the specified Enterprise JavaBean (EJB). Take action recommended in the message associated with the specified exception. WSVR0067=WSVR0067E: EJB container caught {0} and is throwing {1}. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0066=WSVR0066W: Maximum threads for pool {0} was less than the minimum; changing from {1} to {2} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0065=WSVR0065W: Maximum threads for pool {0} was less than 1; changing from {1} to 1 This exception is unexpected. The cause is not immediately known. 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/ . WSVR0064=WSVR0064W: Minimum threads for pool {0} was less than 0; changing from {1} to 0 This exception is unexpected. The cause is not immediately known. 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/ . WSVR0062=WSVR0062E: Unable to start EJB, {0}: {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0227I=WSVR0227I: User initiated module stop operation requested on Module, {1}, of application, {0} A managed bean (MBean) or an administrative console request to stop a module is being processed. This request might have occurred because of an update to this application. No action is required. WSVR0162E=WSVR0162E: A type attribute is missing within the dependency element definition for the {0} component class for the {1} extension point in the {2} bundle.. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0052=WSVR0052W: Attempted to unregister URLProvider with null protocol The server has aborted its attempt to unregister a URL provider that is configured with a null protocol. Check the configuration of the URL provider. WSVR0226I=WSVR0226I: User initiated module start operation request completed on Module, {1}, of application, {0} A managed bean (MBean) or an administrative console request to start or update a module has successfully completed. No action is required. WSVR0117W=WSVR0117W: WebSphere RemoteObject cache size ({0}) not a valid integer. Using default value ({1}). A WebSphere RemoteObject cache size was specified using the system property com.ibm.websphere.RemoteObjectCacheSize. The value specified was not a valid integer. Change the value specified for the RemoteObject cache size system property to a valid integer. WSVR0161E=WSVR0161E: A type attribute is missing within the dependency element definition for the {0} component-id element value for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0009E=WSVR0009E: Error occurred during startup {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0047=WSVR0047E: Batch naming operation failed : {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0046=WSVR0046E: Unable to bind, {0}: {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0045=WSVR0045E: Unable to create sub-context {0}: {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0044=WSVR0044E: Unable to stop EJB jar, {0}: {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0043=WSVR0043E: Unbind failed for {0}: {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0042=WSVR0042E: Unable to stop {0}: {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0333W=WSVR0333W: Setting encodeResourceURLs to false has been deprecated. The default of encodeResourceURLs is now true, setting encodeResoureURLs to false is deprecated and can lead to resource not found problems at the application level. No action is required, but the user should be aware of the possibility of resourceNotFound errors, solveable by setting encodeResourceURLs to true WSVR0041=WSVR0041I: Stopping EJB jar: {0} The specified Enterprise JavaBeans (EJB) JAR file is being stopped as part of application shutdown activities. No action is required. WSVR0040=WSVR0040E: addEjbModule failed for {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0225I=WSVR0225I: User initiated module start operation requested on Module, {1}, of application, {0} An MBean or AdminConsole request to start or update a module is being processed. No action is required. WSVR0116W=WSVR0116W: WebSphere RemoteObject cache size ({0}) not in valid range. Using default value ({1}). A WebSphere RemoteObject cache size was specified using the system property com.ibm.websphere.RemoteObjectCacheSize. The value specified was not within the valid range. Change the value specified for the RemoteObject cache size system property to a valid value. WSVR0160E=WSVR0160E: The {0} startup-mode attribute value, which is specified for the {1} component type for the {2} extension point within the {3} bundle, is not valid. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0051W=WSVR0051W: Attempted to register a URL Provider, {0}, with a null protocol The server has aborted its attempt to unregister a URL provider that is configured with a null protocol. Check the configuration of the URL provider. WSVR0008E=WSVR0008E: Error encountered reading {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0039=WSVR0039E: Unable to start EJB jar, {0}: {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0038=WSVR0038I: No JNDI name found for {0}, binding home name as {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0037=WSVR0037I: Starting EJB jar: {0} The specified Enterprise JavaBeans (EJB) JAR file is being started as part of normal application start activities. No action is required. WSVR0036=WSVR0036E: Failure to obtain initial naming context: {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0035=WSVR0035E: Failure to initialized the container: {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0034=WSVR0034W: Invalid passivation directory specified: {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0033=WSVR0033E: Unable to load security collaborator, {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0032=WSVR0032E: Object Adapter created already This exception is unexpected. The cause is not immediately known. 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/ . WSVR0031=WSVR0031E: Unable to load container {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0030=WSVR0030E: ORB not initialized This exception is unexpected. The cause is not immediately known. 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/ . WSVR0224E=WSVR0224E: Module start operations not permitted on Module, {0}, of application, {1} Start operations are not allowed on this type of module. Perform the start operation on the application instead of on the module. WSVR0332I=WSVR0332I: Duplicate package definition detected for package {0}. The attempt to define the package resulted in an IllegalStateException, indicating that the package was already defined by this class loader or one of its ancestors. No action is required, but the user should be aware of the possibility that future class loads from this package may fail if the existing package definition was incorrect. WSVR0195E=WSVR0195E: Composition unit {0} in BLA {1} failed to stop. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0007E=WSVR0007E: Could not find the {0} object in {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0115I=WSVR0115I: WebSphere RemoteObject cache size set to {0}. The WebSphere RemoteObject cache size has been set based on the system property com.ibm.websphere.RemoteObjectCacheSize. No action is required. WSVR0223E=WSVR0223E: Module stop operations not permitted on Module, {0}, of application, {1} Stop operations are not allowed on this type of module. Perform the stop operation on the application instead of on the module. WSVR0331I=WSVR0331I: The {0} class loader plug-in has been loaded. 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. No action is required. WSVR0006I=WSVR0006I: Server recovery complete. Process stopping. The recovery process has successfully completed and the server is stopping. No action is required. WSVR0194E=WSVR0194E: Composition unit {0} in BLA {1} failed to start. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0114I=WSVR0114I: Message-driven Enterprise JavaBean (EJB) message listener is disabled. The message-driven Enterprise JavaBean (EJB) message listener has been disabled because either the messaging service is not installed or the messaging service is disabled. Message-driven Enterprise JavaBeans (EJBs) will not function properly. If a message-driven Enterprise JavaBean (EJB) is used on this node, a messaging service must be installed and enabled. WSVR0222E=WSVR0222E: Module stop operation not permitted on Module, {0}, of application, {1} The WAR file class loader scope does not allow you to perform stop operations on this module. Change the scope of the WAR file class loader to allow an isolated WAR file class loader. WSVR0113W=WSVR0113W: Configured number of threads value, {0}, for the EJB Timer Service is not allowed. Configured value must be in the range from {1} to {2}. The EJB Timer Service Number of timer threads property is not configured properly. Change the value specified for the EJB Timer Service Number of timer threads property to a supported value. WSVR0193I=WSVR0193I: Composition unit {0} in BLA {1} stopped. The specified composition unit in the specified Business Level Application (BLA) has been stopped. No action is required. WSVR0005I=WSVR0005I: Server {0} open for recovery. The server has started its recovery process. No action is required. WSVR0330E=WSVR0330E: An exception occurred while trying to retrieve the list of files in the directory {0}. There might be a problem with the permissions associated with the specified directory. Make sure that the specified directory has the correct permissions. WSVR0221I=WSVR0221I: Application started: {0} The specified application has started. No action is required. WSVR0112W=WSVR0112W: Configured poll interval value, {0}, for the EJB Timer Service is not allowed. Configured value must be in the range from {1} to {2}. The EJB Timer Service Poll interval property is not configured properly. Change the value specified for the EJB Timer Service Poll interval property to a supported value. WSVR0192I=WSVR0192I: Stopping composition unit {0} in BLA {1}. The specified composition unit in the specified Business Level Application (BLA) is being stopped. No action is required. WSVR0004E=WSVR0004E: The server name, {0}, is not a valid name. There is a mismatch between the name of the specified server and the server name specified in the corresponding server.xml file. Make sure that the same server name is specified in both the directory and in the corresponding server.xml. WSVR0220I=WSVR0220I: Application stopped: {0} The specified application is stopped. No action is required. WSVR0111W=WSVR0111W: EJB Timer Service could not be started, EJBs implementing the TimedObject interface will not function properly. The EJB Timer Service might not be configured properly. Verify the EJB Timer Service is configured properly. WSVR0191I=WSVR0191I: Composition unit {0} in BLA {1} started. The specified composition unit in the specified Business Level Application (BLA) has been started. No action is required. WSVR0003E=WSVR0003E: Server {0} failed to start {1} The server has failed to start. Check the server error logs for error messages that provide more information about the specific problems. WSVR0501E=WSVR0501E: Error creating component {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0190I=WSVR0190I: Starting composition unit {0} in BLA {1}. The specified composition unit in the specified Business Level Application (BLA) is being started. No action is required. WSVR0002I=WSVR0002I: Server {0} open for e-business, problems occurred during startup The server has started, but problems occurred during the server startup process. Check the server error logs for error messages that provide more information about the specific problems. WSVR0500E=WSVR0500E: Unable to parse {0} at line {1}, column {3} {4} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0110I=WSVR0110I: EJB Timer Service is disabled. The EJB Timer Service has been disabled because the Number of timer threads property is set to zero. Enterprise JavaBeans (EJBs) implementing the javax.ejb.TimedObject interface will not function properly when the Number of timer threads property is set to zero. If the EJB Timer Service is to be used on this node, set the Number of timer threads property to a valid value other than zero. This action will enable the EJB Timer Service. WSVR0644E=WSVR0644E: The Selectable Bundle Provider prefix "{0}" has been previously defined, selectable bundles for this provider will not be processed. Each selectable bundle provider must provide a unique provider prefix. 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/ .. WSVR0001I=WSVR0001I: Server {0} open for e-business The server has started successfully and is open for e-business. No action is required. WSVR0643I=WSVR0643I: No selectable bundle providers are defined. No WebSphere components have specified a selectable bundle provider extension point. 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/ .. WSVR0209E=WSVR0209E: Unable to start EJB jar {0}, enterprise bean {1} {2} An Enterprise JavaBean (EJB) JAR file has failed to start. Verify the Enterprise JavaBean (EJB) JAR file that contains the failed EJB has been deployed, and look for error messages that appear between this message and the preceding WSVR0037I message. WSVR0642E=WSVR0642E: Unexpected error occurred while attempting to access the "{0}" Eclipse extension point. Error data: {1} An error occurred while attempting to read Exclipse extension points. 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/ .. WSVR0208E=WSVR0208E: Unable to start EJB jar: {0} {1} An Enterprise JavaBean (EJB) JAR file has failed to start. Look for error messages that appear between this message and the preceeding WSVR0037I message. If you find one, it may be related to the cause of this message. If none of these messages are found, the description of the exception that appears as part of this message might help you determine why the EJB JAR file failed to start. WSVR0179I=WSVR0179I: The runtime provisioning feature is disabled. All components will be started. This message is for informational purposes only. Changes are not required for this user action. WSVR0641E=WSVR0641E: Unable to get Eclipse extension registry. Selectable bundle activation cannot be completed. 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/ .. WSVR0207W=WSVR0207W: Another application edition {0} is running. Please stop it first. Failed to start application edition {1}. Another edition of the application is running so the specified edition of the application cannot be started. Stop the edition of the application that is running and start the specified edition again. WSVR0178I=WSVR0178I: The runtime provisioning feature is enabled. Some components will be started as they are needed. This message is for informational purposes only. Changes are not required for this user action. WSVR0640E=WSVR0640E: Unable to get Eclipse extension point using the extension point identifier "{0}". Selectable bundle activation cannot be completed. 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/ .. WSVR0315E=WSVR0315E: The configuration data for the thread pool named {0} contains an invalid entry, this threadpool is not avaiable for use. The value specified for the Maximum size thread pool property cannot be zero, and must be greater than or equal to the value specified for the Minimum size property. Make sure that appropriate values are specified for the Maximum size and and Minimum size threadpool properties. WSVR0206E=WSVR0206E: Module, {0}, of application, {1}, failed to start This exception is unexpected. The cause is not immediately known. 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/ . WSVR0177E=WSVR0177E: The {0} component is disabled.. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0205E=WSVR0205E: Module, {0}, of application, {1}, failed to initialize This exception is unexpected. The cause is not immediately known. 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/ . WSVR0176E=WSVR0176E: The following exception has occurred in the configAnalyzer class: {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0313E=WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages. The message listener service might be disabled. Enable the message listener service if it is disabled. WSVR0204I=WSVR0204I: Application: {0} Application build level: Unknown The specified application does not have a specified application build level. No action is required. WSVR0175E=WSVR0175E: The Application Server cannot locate the {0} component, which is a mandatory dependency for the {1} component. The {1} component has been disabled. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0629I=WSVR0629I: The request buffer for thread pool "{0}" has reached its capacity. The queue of pending work requests on the specified thread pool has reached its limit, which could potentially lead to performance issues. No immediate action is required; however, to prevent the situation in the future, the thread pool's request buffer size may need to be increased. WSVR0174W=WSVR0174W: A duplicate component has been ignored. Ignore the {0} component for the {1} extension point within the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0203I=WSVR0203I: Application: {0} Application build level: {1} The application specified in the log message has the specified application build level. No action is required. WSVR0628W=WSVR0628W: The directory "{0}" is not empty and its contents might be overriding WebSphere classes. The specified directory is meant to be used for temporary patches. Classes contained in this directory will override WebSphere classes. Verify that the classes contained in the specified directory are compatible with the installed version of the product. WSVR0173W=WSVR0173W: A metadata error occurred for the {0} component for the {1} extension point within the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0202E=WSVR0202E: Application, {0}, failed to start {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0627W=WSVR0627W: A thread could not be acquired from the ORB thread pool after the maximum wait time of {0} milliseconds was exceeded. The ORB was unable to acquire a thread to process a request. 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. WSVR0201E=WSVR0201E: Application, {0}, failed to initialize {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0626W=WSVR0626W: The ThreadPool setting on the ObjectRequestBroker service is deprecated. The object request broker (ORB) service thread pool has been replaced by a thread pool manager service thread pool that has the same name. The thread pool settings on the ORB service are still supported in this release. However, this function will be removed in a future release. You might want to update the thread pool manager service thread pool configuration to match your object request broker service configuration and then select the Use the ORB.thread.pool settings associated with the Thread Pool Manager for the thread pool setting for the ORB service. WSVR0172E=WSVR0172E: In the {0} component for the {1} extension point within the {2} bundle, a child element value is not valid. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0019W=WSVR0019W: CustomService, {0}, failed to initialize. {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0200I=WSVR0200I: Starting application: {0} The specified application is starting. No action is required. WSVR0625W=WSVR0625W: Server {0} recovery complete, problems occurred during recovery. Server stopped. Server log files should contain failure information. The server encountered problems during recovery and has stopped. Examine the log files to see what failure messages were recorded there. WSVR0171E=WSVR0171E: In the services element definition for the {0} component for the {1} extension point within the {2} bundle, the only valid child element is the provide tag. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0018W=WSVR0018W: Unable to create CustomService, {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0170E=WSVR0170E: The interface attribute value is not specified in the service element definition for the {0} component for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0624I=WSVR0624I: Server {0} recovery complete. Server stopped. The server has completed recovery and has stopped. No action is required. WSVR0234E=WSVR0234E: Failed to stop the {0} module in the {1} application. An unexpected exception occurred while stopping the specified module. Review the SystemErr.log file to determine the cause of the failure. WSVR0407E=WSVR0407E: The {0} command is not supported on the {1} node since it has {2} version of the product. This command is only supported on a version equal to or greater than 7.0. Do not attempt to run this command on this node. WSVR0623W=WSVR0623W: Unexpected exception occurred: "{0}". The com.ibm.websphere.threadpool.clearThreadLocal property has been set and will be applied to the {0} thread pool. This option is deprecated. The com.ibm.websphere.threadpool.clearThreadLocal property is still used in this release, but will be removed in a future release. Remove the com.ibm.websphere.threadpool.clearThreadLocal property from the Java Virtual Machine (JVM) properties. WSVR0017E=WSVR0017E: Error encountered binding the J2EE resource, {0}, as {1} from {2} {3} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0233W=WSVR0233W: The configuration for the isolated shared library {0} was updated, but the changes will not be applied until the server is restarted. When the configuration of an isolated shared library is updated, the corresponding class loader is not updated if it is already in use. The server should be restarted for the changes to take effect. WSVR0016W=WSVR0016W: Classpath entry, {0}, in Resource, {1}, located at {2} has an invalid variable A variable that was included in the class path definition of the resource is not defined or does not contain a valid value. Define the missing variable or provide a valid value for this variable. WSVR0406I=WSVR0406I: Provisioning is disabled. This message is for informational purposes only. No action is required. WSVR0622W=WSVR0622W: The startup thread pool "{0}" could not be found. A default pool will be used. The thread pool associated with server startup could not be found in the configuration. Configure a thread pool with the name specified in this message. WSVR0124E=WSVR0124E: Failed to look up service {0}. Component {1} marked disabled This exception is unexpected. The cause is not immediately known. 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/ . WSVR0405I=WSVR0405I: Provisioning is enabled. This message is for informational purposes only. No action is required. WSVR0232E=WSVR0232E: Unable to resolve cross document link identified by the uri: {0}, and referenced by document {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0123W=WSVR0026W: The class paths for the isolated resource provider {0} were updated, but the changes will not be applied until the server is restarted. When the class paths of an isolated resource provider are updated, the corresponding class loader is not updated if it is already in use. The server should be restarted for the changes to take effect. WSVR0159E=WSVR0159E: The {0} startup-mode attribute value, which is specified for the {1} component class for the {2} extension point within the {3} bundle, is not valid. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0621E=WSVR0621E: CMP Bean "{0}" is configured to use a CMP Connection Factory JNDI name of "{1}" resource. This resource does not exist. This error indicates that a container-managed persistence (CMP) bean, that is configured to use a Connection Factory resource, is not available. The CMP bean cannot function because the resource is not defined by the administrator. Use the administrative console to select the specified data source for CMP use. WSVR0231E=WSVR0231E: Unrecognized resource type encountered during Application startup: {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0122W=WSVR0025W: The native paths specified for isolated resource provider {0} will be ignored. Native library loading is not supported for isolated resource providers. Remove the native library paths from the isolated resource provider. WSVR0404E=WSVR0404E: The {0} server on the {1} node does not exist. Either the server name or the node name was not specified correctly. Specify the correct node name and server name. WSVR0158E=WSVR0158E: A startup value, which is specified for the {0} component type and the {1} extension point within the {2} bundle, is not valid. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0230E=WSVR0230E: Invalid uri format encountered while processing cross document link: {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0403E=WSVR0403E: The {0} command name is not valid. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0049I=WSVR0049I: Binding {0} as {1} The resource manager is binding the specified resource to the specified JNDI name. No action is required. WSVR0402W=WSVR0402W: Invalid MBean name {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0121E=WSVR0121E: An exception occurred getting a socket for port {0} on hostname {1} with an IP address of {2}. {3} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0157E=WSVR0157E: A startup value, which is specified for the {0} component class and the {1} extension point within the {2} bundle, is not valid. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0048W=WSVR0048W: Binding {0} failed, no JNDI name found This exception is unexpected. The cause is not immediately known. 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/ . WSVR0401W=WSVR0401W: Unable to deregister the {0} MBean {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0120E=WSVR0120E: An error occurred processing {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0156E=WSVR0156E: Either the class or type attribute must be specified in the component definition for the {0} extension point in the {1} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0400W=WSVR0400W: Unable to register the {0} MBean {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0155E=WSVR0155E: Only component type elements must be defined for the {0} extension point in the {1} bundle.. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0010I=WSVR0010I: Server {0} open for recovery, problems occurred during startup. The server has started its recovery process, but problems occurred during the server startup process. Check the server error logs for error messages that provide more information about the specific problems. WSVR0219I=WSVR0219I: Application, {0}, is disabled The specified application is disabled and thus not started. No action is required. WSVR0154E=WSVR0154E: A components child element must be defined for the {0} extension point in the {1} bundle.. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0218W=WSVR0218W: No modules defined for application, {0}, on server, {1}, in cluster, {2} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0607W=WSVR0607W: Too many thread hangs have been falsely reported. The hang threshold is now being set to {0} seconds. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0651I=WSVR0651I: The {0} growable thread pool has grown to {1} times its initially-configured maximum of {2}. The specified thread pool has grown to the specified multiple of its predefined maximum size. A large number of threads might consume an undesired quantity of system resources. No action is required. WSVR0153E=WSVR0153E: A single components element must be defined for the {0} extension point in the {1} bundle.. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0109I=WSVR0109I: Component {0} not started since it is not specified for this platform in file {1} at line {2} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0217I=WSVR0217I: Stopping application: {0} The specified application is stopping. No action is required. WSVR0108W=WSVR0108W: Invalid attribute {0} in file {1} at line {2} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0606W=WSVR0606W: Thread "{0}" ({1}) was previously reported to be hung but has completed. It was active for approximately {2} milliseconds. There is/are {3} thread(s) in total in the server that still may be hung. A thread that was previously reported as hung is no longer active. This situation probably indicates that the work that was being processed on that thread has been completed. 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/ . WSVR0152E=WSVR0152E: The {0} component is a duplicate component ID. The duplicate component has been disabled. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0216W=WSVR0216W: Stopping application, {0}, failed. The application is not started. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0107W=WSVR0107W: Duplicate component, {0}, in file {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0605W=WSVR0605W: Thread "{0}" ({1}) has been active for {2} milliseconds and may be hung. There is/are {3} thread(s) in total in the server that may be hung.{4} A thread has been active for an extended period. This situation might indicate that the thread is in a deadlock or infinite loop situation. 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/ . WSVR0151E=WSVR0151E: The {0} component implements the {1} service, which is duplicated and ignored. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0215W=WSVR0215W: Starting application, {0}, failed. The application is not installed. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0150E=WSVR0150E: Missing entry for {0} in {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0214W=WSVR0214W: Application, {0}, already initialized. The specified application has already been initialized. This would occur if the application has already been started. Verify that the specified application has not already been started. WSVR0604I=WSVR0604I: Attempt to register EJBContainer MBean: caught exception {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0106E=WSVR0106E: Invalid startup value {0} at line {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0213W=WSVR0213W: Classpath entry, {0}, in library, {1}, located at {2} has an invalid variable This exception is unexpected. The cause is not immediately known. 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/ . WSVR0105E=WSVR0105E: Both type, {0}, or class, {1}, are defined in {2} at line {3} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0603E=WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0639E=WSVR0639E: An error occurred while processing asynchronous file operation request by the RuntimeSyncHandler. The exception is {0}. This exception is unexpected. The cause is not immediately known.. 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/ .. WSVR0602W=WSVR0602W: Attempt to access javaNameSpace from a ComponentMetaData that does not support a javaNameSpace. Only Web components and Enterprise JavaBean (EJB) components support access to the space that contains the Java class names (javaNameSpace). 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/ . WSVR0321I=WSVR0321I: The module deployment, {0}, contains a classloader. That classloader will be ignored. The configuration model allows a class loader to be contained by module deployments other than Web module deployments. Class loaders contained by module deployments other than Web module deployments are ignored. The configuration is usable. No configuration update is required. However, to stop receiving this message, remove the class loader that is contained in the noted module deployment. WSVR0212W=WSVR0212W: Library, {0}, defined in {1} does not exist This exception is unexpected. The cause is not immediately known. 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/ . WSVR0104E=WSVR0104E: No type or class defined in {0} at line {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0320W=WSVR0320W: The deployed object classloading mode, {0}, will override the deprecated module deployment classloading mode, {1}, of the web module deployment, {2}. When a Web module deployment contains a class loader, the class loading mode of that class loader takes precedence over the deprecated class loading mode of the Web module itself. The configuration is usable. However, to stop receiving this message, update the class loading mode of the Web module to match the class loading mode of the contained class loader. Keep in mind that the Web module deployment class loading mode is deprecated. WSVR0638E=WSVR0638E: An error occurred when the SelectableBundleSyncHandler attempted to dispatch a thread. The exception is {0}. An unrecoverable thread dispatch error occurred. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. WSVR0601W=WSVR0601W: javaURLContext object missing for J2EEName {0}, caught exception {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0211W=WSVR0211W: Duplicate library, {0}, defined in {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0103E=WSVR0103E: An error occurred destroying, {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0637E=WSVR0637E: An attempt to initialize the AsyncFileOperations service failed. The service is already initialized. The execution stack trace is {0}. An initialization operation failed. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. WSVR0600W=WSVR0600W: No thread context This exception is unexpected. The cause is not immediately known. 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/ . WSVR0073W=WSVR0073W: Unable to read required resource: {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0210W=WSVR0210W: No modules defined for application, {0}, on server, {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0102E=WSVR0102E: An error occurred stopping, {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0636E=WSVR0636E: Unexpected error occurred when attempting to switch selectable bundle implementations. Exception information: {0} Please examine previous log messages and ffdc logs for additional information. 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/ .. WSVR0246E=WSVR0246E: A recursive {0} product variable has been encountered in the {1} property of the {2} configuration object. A string that was being parsed contains a variable which directly or indirectly references itself. Check the specified string and remove the direct or indirect references. WSVR0101W=WSVR0101W: An error occurred starting, {0} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0072W=WSVR0072W: Ignoring undeclared override of interface, {0}, with implementation, {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0635E=WSVR0635E: Unable to locate Cluster Information in {0}. The document at the specified uri does not contain the required cluster information. This configuration document has been corrupted through some external means, delete and recreate the cluster. WSVR0245E=WSVR0245E: An unterminated product variable reference has been encountered when parsing the {0} value of the {1} property of the {2} configuration object. A closing parenthesis or closing brace is missing in the string definition for a product variable reference. Check the specified string and add the missing closing parenthesis or closing brace. WSVR0100W=WSVR0100W: An error occurred initializing, {0} {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0180E=WSVR0180E: Server {0} on node {1} was not found. The specified values for the server and node are not configured. Specify valid, configured values for these parameters. WSVR0071W=WSVR0071W: Nothing registered before for interface, {0}, override ignored for implementation, {1} This exception is unexpected. The cause is not immediately known. 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/ . WSVR0634E=WSVR0634E: Unable to locate ApplicationServer in {0}. The document at the specified uri does not contain an application server element. This configuration document has been corrupted through some external means, delete and recreate the application server. WSVR0244E=WSVR0244E: An undefined {0} product variable has been encountered in the {1} property of the {2} configuration object. An undefined product variable has been encountered when parsing a string property in a configuration object. Define the specified product variable. WSVR0633E=WSVR0633E: The OSGI server cache directory at {0} could not be created. Exception information: {1} The directory create operation could not be completed. Check directory permissions and other file system constraints that may prohibit the directory from being created. WSVR0243E=WSVR0243E: Recursive WebSphere variable reference "{0}" encountered. A string that was being parsed contains a variable which directly or indirectly references itself. Check the specified string and remove the direct or indirect references. WSVR0632E=WSVR0632E: The OSGI server cache directory at {0} could not be deleted. Exception information: {1} The directory delete operation could not be completed. Check directory permissions and other file system constraints that may prohibit the directory from being deleted. WSVR0242E=WSVR0242E: Unterminated WebSphere variable reference encountered while parsing string "{0}". A closing parenthesis is missing in the string definition for a WebSphere variable reference. Check the specified string and add the missing closing parenthesis. WSVR0169E=WSVR0169E: The name attribute value should be either component or service in the dependency element definition for the {0} component type for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ . WSVR0631E=WSVR0631E: The Selectable Bundle {0} could not be installed into the OSGI server cache at {1}. Exception information: {2} The file copy operation could not be completed. Check directory permissions and other file system constraints that may prohibit the file from being copied. WSVR0241I=WSVR0241I: Undefined WebSphere variable "{0}" encountered while parsing string "{1}". An undefined WebSphere variable was encountered while parsing a string. This variable might be optional. Define the WebSphere variable if your system requires it to be set. If the variable substitution is not needed, specify $$ as the escape sequence. If the variable substitution is needed, use the correct syntax, which should be similar to ${VAR_NAME}. WSVR0024I=WSVR0024I: Server {0} stopped The server is stopped. No action is required. WSVR0630I=WSVR0630I: Growable thread pool "{0}" has been expanded beyond its initially-defined maximum capacity. The pool size is currently "{1}". The specified thread pool has reached its predefined maximum size and will be expanded. No immediate action is required; however, the pool will continue to grow as long as work requests outpace the current number of available threads. WSVR0168E=WSVR0168E: The name attribute value should be either component or service in the dependency element definition for the {0} class value for the {1} extension point in the {2} bundle. This exception is unexpected. The cause is not immediately known. 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/ .