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


WSVR

WSVR0001I: Server {0} open for e-business
Explanation The server has started successfully and is open for e-business.
Action No action is required.
WSVR0002I: Server {0} open for e-business, problems occurred during startup
Explanation The server has started, but problems occurred during the server startup process.
Action Check the server error logs for error messages that provide more information about the specific problems.
WSVR0003E: Server {0} failed to start
{1}
Explanation The server has failed to start.
Action Check the server error logs for error messages that provide more information about the specific problems.
WSVR0004E: The server name, {0}, is not a valid name.
Explanation There is a mismatch between the name of the specified server and the server name specified in the corresponding server.xml file.
Action Make sure that the same server name is specified in both the directory and in the corresponding server.xml.
WSVR0005I: Server {0} open for recovery.
Explanation The server has started its recovery process.
Action No action is required.
WSVR0006I: Server recovery complete. Process stopping.
Explanation The recovery process has successfully completed and the server is stopping.
Action No action is required.
WSVR0007E: Could not find the {0} object in {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0008E: Error encountered reading {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Error occurred during startup
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Server {0} open for recovery, problems occurred during startup.
Explanation The server has started its recovery process, but problems occurred during the server startup process.
Action Check the server error logs for error messages that provide more information about the specific problems.
WSVR0016W: Classpath entry, {0}, in Resource, {1}, located at {2} has an invalid variable
Explanation A variable that was included in the class 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 this variable.
WSVR0017E: Error encountered binding the J2EE resource, {0}, as {1} from {2}
{3}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Unable to create CustomService, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: CustomService, {0}, failed to initialize.
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: CustomService, {0}, failed to shutdown.
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Native path entry, {0}, in Resource, {1}, located at {2} has an invalid variable
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 this variable.
WSVR0022W: The value, {0}, with Resource ID, {1}, located at {2} has an invalid 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.
WSVR0024I: Server {0} stopped
Explanation The server is stopped.
Action No action is required.
WSVR0025W: The native paths specified for isolated resource provider {0} will be ignored.
Explanation Native library loading is not supported for isolated resource providers.
Action Remove the native library paths from the isolated resource provider.
WSVR0026W: The class paths for the isolated resource provider {0} were updated, but the changes will not be applied until the server is restarted.
Explanation When the class paths of an isolated resource provider are updated, the corresponding class loader is not updated if it is already in use.
Action The server should be restarted for the changes to take effect.
WSVR0030E: ORB not initialized
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0031E: Unable to load container
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0032E: Object Adapter created already
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0033E: Unable to load security collaborator, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0034W: Invalid passivation directory specified: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0035E: Failure to initialized the container: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0036E: Failure to obtain initial naming context: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0037I: Starting EJB jar: {0}
Explanation The specified Enterprise JavaBeans (EJB) JAR file is being started as part of normal application start activities.
Action No action is required.
WSVR0038I: No JNDI name found for {0}, binding home name as {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0039E: Unable to start EJB jar, {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0040E: addEjbModule failed for {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0041I: Stopping EJB jar: {0}
Explanation The specified Enterprise JavaBeans (EJB) JAR file is being stopped as part of application shutdown activities.
Action No action is required.
WSVR0042E: Unable to stop {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0043E: Unbind failed for {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0044E: Unable to stop EJB jar, {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0045E: Unable to create sub-context {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0046E: Unable to bind, {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0047E: Batch naming operation failed : {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Binding {0} failed, no JNDI name found
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Binding {0} as {1}
Explanation Binding resource, {0}, with JNDI name, {1}.
Action No action is required.
WSVR0051W: Attempted to register a URL Provider, {0}, with a null protocol
Explanation The server has aborted its attempt to unregister a URL provider that is configured with a null protocol.
Action Check the configuration of the URL provider.
WSVR0052W: Attempted to unregister URLProvider with null protocol
Explanation The server has aborted its attempt to unregister a URL provider that is configured with a null protocol.
Action Check the configuration of the URL provider.
WSVR0055W: Unexpected objectToKey method callback for object {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Tie class of {0} can not be found.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0057I: EJB jar started: {0}
Explanation The specified Enterprise JavaBeans (EJB) JAR file has been started as part of normal application startup activities.
Action No action is required.
WSVR0058I: All EJBs will be initialized during application start
Explanation The default option to defer Enterprise JavaBeans (EJB) initialization has been disabled. All Enterprise JavaBeans (EJBs) will be initialized during the application startup process.
Action No action is required.
WSVR0059I: EJB jar stopped: {0}
Explanation The specified Enterprise JavaBean (EJB) JAR file has been stopped as part of application shutdown activities.
Action No action is required.
WSVR0062E: Unable to start EJB, {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0064W: Minimum threads for pool {0} was less than 0; changing from {1} to 0
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0065W: Maximum threads for pool {0} was less than 1; changing from {1} to 1
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0066W: Maximum threads for pool {0} was less than the minimum; changing from {1} to {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0067E: EJB container caught {0} and is throwing {1}.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0068E: Attempt to start EnterpriseBean {0} failed with exception: {1}
Explanation An error has occurred during the initialization and start of the Enterprise JavaBean (EJB) {0}.
Action Take action recommended in the message associated with exception {1}.
WSVR0071W: Nothing registered before for interface, {0}, override ignored for implementation, {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Ignoring undeclared override of interface, {0}, with implementation, {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Unable to read required resource: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0100W: An error occurred initializing, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0101W: An error occurred starting, {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: An error occurred stopping, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: An error occurred destroying, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: No type or class defined in {0} at line {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Both type, {0}, or class, {1}, are defined in {2} at line {3}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Invalid startup value {0} at line {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Duplicate component, {0}, in file {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0108W: Invalid attribute {0} in file {1} at line {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Component {0} not started since it is not specified for this platform in file {1} at line {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: EJB Timer Service is disabled.
Explanation 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.
Action 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.
WSVR0111W: EJB Timer Service could not be started, EJBs implementing the TimedObject interface will not function properly.
Explanation The EJB Timer Service might not be configured properly.
Action Verify the EJB Timer Service is configured properly.
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}.
Explanation The EJB Timer Service Poll interval property is not configured properly.
Action Change the value specified for the EJB Timer Service Poll interval property to a supported value.
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}.
Explanation The EJB Timer Service Number of timer threads property is not configured properly.
Action Change the value specified for the EJB Timer Service Number of timer threads property to a supported value.
WSVR0114I: Message-driven Enterprise JavaBean (EJB) message listener is disabled.
Explanation 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.
Action If a message-driven Enterprise JavaBean (EJB) is used on this node, a messaging service must be installed and enabled.
WSVR0115I: WebSphere RemoteObject cache size set to {0}.
Explanation The WebSphere RemoteObject cache size has been set based on the system property com.ibm.websphere.RemoteObjectCacheSize.
Action No action is required.
WSVR0116W: WebSphere RemoteObject cache size ({0}) not in valid range. Using default value ({1}).
Explanation A WebSphere RemoteObject cache size was specified using the system property com.ibm.websphere.RemoteObjectCacheSize. The value specified was not within the valid range.
Action Change the value specified for the RemoteObject cache size system property to a valid value.
WSVR0117W: WebSphere RemoteObject cache size ({0}) not a valid integer. Using default value ({1}).
Explanation A WebSphere RemoteObject cache size was specified using the system property com.ibm.websphere.RemoteObjectCacheSize. The value specified was not a valid integer.
Action Change the value specified for the RemoteObject cache size system property to a valid integer.
WSVR0119W: Unable to find MultibrokerDomain service, stateful session bean failover will not occur.
Explanation The multibroker domain service might be disabled.
Action Verify that the multibroker domain service is enabled.
WSVR0120E: An error occurred processing {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: An exception occurred getting a socket for port {0} on hostname {1} with an IP address of {2}.
{3}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0124E: Failed to look up service {0}. Component {1} marked disabled
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Missing entry for {0} in {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: The {0} component implements the {1} service, which is duplicated and ignored.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: The {0} component is a duplicate component ID. The duplicate component has been disabled.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0153E: A single components element must be defined for the {0} extension point in the {1} bundle..
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0154E: A components child element must be defined for the {0} extension point in the {1} bundle..
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Only component type elements must be defined for the {0} extension point in the {1} bundle..
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Either the class or type attribute must be specified in the component definition for the {0} extension point in the {1} bundle.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: A startup value, which is specified for the {0} component class and the {1} extension point within the {2} bundle, is not valid.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0158E: A startup value, which is specified for the {0} component type and the {1} extension point within the {2} bundle, is not valid.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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..
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: 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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: 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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
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.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0172E: In the {0} component for the {1} extension point within the {2} bundle, a child element value is not valid.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0173W: A metadata error occurred for the {0} component for the {1} extension point within the {2} bundle.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0174W: A duplicate component has been ignored. Ignore the {0} component for the {1} extension point within the {2} bundle.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0175E: The Application Server cannot locate the {0} component, which is a mandatory dependency for the {1} component. The {1} component has been disabled. Cannot find component for mandatory dependency {0}. Disable component: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: The following exception has occurred in the configAnalyzer class: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: The {0} component is disabled..
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0178I: The runtime provisioning feature is enabled. Some components will be started as they are needed.
Explanation This message is for informational purposes only.
Action Changes are not required for this user action.
WSVR0179I: The runtime provisioning feature is disabled. All components will be started.
Explanation This message is for informational purposes only.
Action Changes are not required for this user action.
WSVR0180E: Server {0} on node {1} was not found.
Explanation The specified values for the server and node are not configured.
Action Specify valid, configured values for these parameters.
WSVR0190I: Starting composition unit {0} in BLA {1}.
Explanation The specified composition unit in the specified Business Level Application (BLA) is being started.
Action No action is required.
WSVR0191I: Composition unit {0} in BLA {1} started.
Explanation The specified composition unit in the specified Business Level Application (BLA) has been started.
Action No action is required.
WSVR0192I: Stopping composition unit {0} in BLA {1}.
Explanation The specified composition unit in the specified Business Level Application (BLA) is being stopped.
Action No action is required.
WSVR0193I: Composition unit {0} in BLA {1} stopped.
Explanation The specified composition unit in the specified Business Level Application (BLA) has been stopped.
Action No action is required.
WSVR0194E: Composition unit {0} in BLA {1} failed to start.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0195E: Composition unit {0} in BLA {1} failed to stop.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Starting application: {0}
Explanation Starting application, {0}.
Action No action is required.
WSVR0201E: Application, {0}, failed to initialize
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Application, {0}, failed to start
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Application: {0} Application build level: {1}
Explanation The application {0} has the specified application build level {1}.
Action No action is required.
WSVR0204I: Application: {0} Application build level: Unknown
Explanation The application {0} does not have a specified application build level.
Action No action is required.
WSVR0205E: Module, {0}, of application, {1}, failed to initialize
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0206E: Module, {0}, of application, {1}, failed to start
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Another application edition {0} is running. Please stop it first. Failed to start application edition {1}.
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.
WSVR0208E: Unable to start EJB jar: {0}
{1}
Explanation An Enterprise JavaBean (EJB) JAR file has failed to start.
Action 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.
WSVR0209E: Unable to start EJB jar {0}, enterprise bean {1}
{2}
Explanation An Enterprise JavaBean (EJB) JAR file has failed to start.
Action Verify the Enterprise JavaBean (EJB) JAR file that contains the failed EJB {1} has been deployed, and look for error messages that appear between this message and the preceeding WSVR0037I message.
WSVR0210W: No modules defined for application, {0}, on server, {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Duplicate library, {0}, defined in {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0212W: Library, {0}, defined in {1} does not exist
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Classpath entry, {0}, in library, {1}, located at {2} has an invalid variable
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Application, {0}, already initialized.
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.
WSVR0215W: Starting application, {0}, failed. The application is not installed.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Stopping application, {0}, failed. The application is not started.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Stopping application: {0}
Explanation Application, {0}, is stopping
Action No action is required.
WSVR0218W: No modules defined for application, {0}, on server, {1}, in cluster, {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0219I: Application, {0}, is disabled
Explanation Application, {0}, is disabled and thus not started.
Action No action is required.
WSVR0220I: Application stopped: {0}
Explanation Application, {0}, is stopped.
Action No action is required.
WSVR0221I: Application started: {0}
Explanation Application {0} has started.
Action No action is required.
WSVR0222E: Module stop operation not permitted on Module, {0}, of application, {1}
Explanation The WAR file class loader scope does not allow you to perform stop operations on this module.
Action Change the scope of the WAR file class loader to allow an isolated WAR file class loader.
WSVR0223E: Module stop operations not permitted on Module, {0}, of application, {1}
Explanation Stop operations are not allowed on this type of module.
Action Perform the stop operation on the appplication instead of on the module.
WSVR0224E: Module start operations not permitted on Module, {0}, of application, {1}
Explanation Start operations are not allowed on this type of module.
Action Perform the start operation on the appplication instead of on the module.
WSVR0225I: User initiated module start operation requested on Module, {1}, of application, {0}
Explanation An MBean or AdminConsole request to start or update a module is being processed.
Action No action is required.
WSVR0226I: User initiated module start operation request completed on Module, {1}, of application, {0}
Explanation A managed bean (MBean) or an administrative console request to start or update a module has successfully completed.
Action No action is required.
WSVR0227I: User initiated module stop operation requested on Module, {1}, of application, {0}
Explanation 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.
Action No action is required.
WSVR0228I: User initiated module stop operation request completed on Module, {1}, of application, {0}
Explanation A managed bean (MBean) or an administrative console request to stop a module has successfully completed.
Action No action is required.
WSVR0230E: Invalid uri format encountered while processing cross document link: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0231E: Unrecognized resource type encountered during Application startup: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0232E: Unable to resolve cross document link identified by the uri: {0}, and referenced by document {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: The configuration for the isolated shared library {0} was updated, but the changes will not be applied until the server is restarted.
Explanation When the configuration of an isolated shared library is updated, the corresponding class loader is not updated if it is already in use.
Action The server should be restarted for the changes to take effect.
WSVR0241I: Undefined WebSphere variable "{0}" encountered while parsing string "{1}".
Explanation An undefined WebSphere variable was encountered while parsing a string. This variable might be optional.
Action 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}.
WSVR0242E: Unterminated WebSphere variable reference encountered while parsing string "{0}".
Explanation A closing parenthesis is missing in the string definition for a WebSphere variable reference.
Action Check the specified string and add the missing closing parenthesis.
WSVR0243E: Recursive WebSphere variable reference "{0}" encountered.
Explanation A string that was being parsed contains a variable which directly or indirectly references itself.
Action Check the specified string and remove the direct or indirect references.
WSVR0244E: An undefined {0} product variable has been encountered in the {1} property of the {2} configuration object.
Explanation An undefined product variable has been encountered when parsing a string property in a configuration object.
Action Define the specified product variable.
WSVR0245E: An unterminated product variable reference has been encountered when parsing the {0} value of the {1} property of the {2} configuration object.
Explanation A closing parenthesis or closing brace is missing in the string definition for a product variable reference.
Action Check the specified string and add the missing closing parenthesis or closing brace.
WSVR0246E: A recursive {0} product variable has been encountered in the {1} property of the {2} configuration object.
Explanation A string that was being parsed contains a variable which directly or indirectly references itself.
Action Check the specified string and remove the direct or indirect references.
WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages.
Explanation The message listener service might be disabled.
Action Enable the message listener service if it is disabled.
WSVR0315E: The configuration data for the thread pool named {0} contains an invalid entry, this threadpool is not avaiable for use.
Explanation 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.
Action Make sure that appropriate values are specified for the Maximum size and and Minimum size threadpool properties.
WSVR0320W: The deployed object classloading mode, {0}, will override the deprecated module deployment classloading mode, {1}, of the web module deployment, {2}.
Explanation 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.
Action 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.
WSVR0321I: The module deployment, {0}, contains a classloader. That classloader will be ignored.
Explanation 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.
Action 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.
WSVR0330E: An exception occurred while trying to retrieve the list of files in the directory {0}.
Explanation There might be a problem with the permissions associated with the specified directory.
Action Make sure that the specified directory has the correct permissions.
WSVR0331I: The {0} class loader plug-in has been loaded.
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.
WSVR0332I: Duplicate package definition detected for package {0}.
Explanation 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.
Action 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.
WSVR0400W: Unable to register the {0} MBean
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Unable to deregister the {0} MBean
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0402W: Invalid MBean name {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: The {0} command name is not valid.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0404E: The {0} server on the {1} node does not exist.
Explanation Either the server name or the node name was not specified correctly.
Action Specify the correct node name and server name.
WSVR0405I: Provisioning is enabled.
Explanation This message is for informational purposes only.
Action No action is required.
WSVR0406I: Provisioning is disabled.
Explanation This message is for informational purposes only.
Action No action is required.
WSVR0407E: The {0} command is not supported on the {1} node since it has {2} version of the product.
Explanation This command is only supported on a version equal to or greater than 7.0.
Action Do not attempt to run this command on this node.
WSVR0500E: Unable to parse {0} at line {1}, column {3}
{4}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0501E: Error creating component {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0600W: No thread context
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0601W: javaURLContext object missing for J2EEName {0}, caught exception
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: Attempt to access javaNameSpace from a ComponentMetaData that does not support a javaNameSpace.
Explanation Only Web components and Enterprise JavaBean (EJB) components support access to the space that contains the Java class names (javaNameSpace).
Action 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: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/ .
WSVR0604I: Attempt to register EJBContainer MBean: caught exception
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: 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}
Explanation A thread has been active for an extended period. This situation might indicate that the thread is in a deadlock or infinite loop situation.
Action 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: 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.
Explanation 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.
Action 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: Too many thread hangs have been falsely reported. The hang threshold is now being set to {0} seconds.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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: CMP Bean "{0}" is configured to use a CMP Connection Factory JNDI name of "{1}" resource. This resource does not exist.
Explanation 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.
Action Use the administrative console to select the specified data source for CMP use.
WSVR0622W: The startup thread pool "{0}" could not be found. A default pool will be used.
Explanation The thread pool associated with server startup could not be found in the configuration.
Action Configure a thread pool with the name specified in this message.
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.
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.
WSVR0624I: Server {0} recovery complete. Server stopped.
Explanation The server has completed recovery and has stopped.
Action No action is required.
WSVR0625W: Server {0} recovery complete, problems occurred during recovery. Server stopped. Server log files should contain failure information.
Explanation The server encountered problems during recovery and has stopped.
Action Examine the log files to see what failure messages were recorded there.
WSVR0626W: The ThreadPool setting on the ObjectRequestBroker service is deprecated.
Explanation The object request broker (ORB) service thread pool has been replaced by a thread pool manager service thread pool that has the same name.
Action 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.
WSVR0627W: A thread could not be acquired from the ORB thread pool after the maximum wait time of {0} milliseconds was exceeded.
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.
WSVR0628W: The directory "{0}" is not empty and its contents might be overriding WebSphere classes.
Explanation The specified 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 specified directory are compatible with the installed version of the product.
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:56:37 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.runtime.runtime.html

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