WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, 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 This is an informational message. No action is required.
WSVR0002I: Server {0} open for e-business, problems occurred during startup
Explanation The server has started, but problems occurred during server start.
Action Check server logs for any errors or problems.
WSVR0003E: Server {0} failed to start
{1}
Explanation The server has failed to started.
Action Check server logs for any errors or problems.
WSVR0004E: The server name, {0}, is not a valid name.
Explanation There is a mismatch between the name of the server speicified and the server name in the corresponding server.xml.
Action Make sure that the server name specified matches both the directory name for the server and the server name in the corresponding server.xml.
WSVR0005I: Server {0} open for recovery.
Explanation The server has started recovery.
Action This is an informational message. No action is required.
WSVR0006I: Server recovery complete. Process stopping.
Explanation The server has recovered and is stopping.
Action This is an informational message. 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0008E: Error encountered reading {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0009E: Error occurred during startup
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0010I: Server {0} open for recovery, problems occurred during startup.
Explanation The server has started recovery. Problems occurred during startup.
Action Check server logs for any errors or problems.
WSVR0016W: Classpath entry, {0}, in Resource, {1}, located at {2} has an invalid variable
Explanation A variable used in the classpath definition of the resource is not defined or does not contain a valid value.
Action Define the missing variable or provide a valid value for the missing variable.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0018W: Unable to create CustomService, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0019W: CustomService, {0}, failed to initialize.
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0020W: CustomService, {0}, failed to shutdown.
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 the missing 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 This is an informational message. No action is required.
WSVR0030E: ORB not initialized
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0031E: Unable to load container
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0032E: Object Adapter created already
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0033E: Unable to load security collaborator, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0034W: Invalid passivation directory specified: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0035E: Failure to initialized the container: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0036E: Failure to obtain initial naming context: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0037I: Starting EJB jar: {0}
Explanation The specified EJB jar is being started as part of normal application start activities.
Action None.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0040E: addEjbModule failed for {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0041I: Stopping EJB jar: {0}
Explanation The specified EJB jar is being stopped as part of application shutdown activities.
Action None.
WSVR0042E: Unable to stop {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0043E: Unbind failed for {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0044E: Unable to stop EJB jar, {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0045E: Unable to create sub-context {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0046E: Unable to bind, {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0047E: Batch naming operation failed : {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0048W: Binding {0} failed, no JNDI name found
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0049I: Binding {0} as {1}
Explanation Binding resource, {0}, with JNDI name, {1}.
Action This is an informational message. No action is required.
WSVR0051W: Attempted to register a URL Provider, {0}, with a null protocol
Explanation The server has aborted the attempt of registering a URL Provider with null protocol.
Action Please check the configuration of the URL Provider.
WSVR0052W: Attempted to unregister URLProvider with null protocol
Explanation The server has aborted the attempt of unregistering a URL Provider with null protocol.
Action Please 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0057I: EJB jar started: {0}
Explanation The specified EJB jar has been started as part of normal application start activities.
Action None.
WSVR0058I: All EJBs will be initialized during application start
Explanation The default option to defer EJB initialization has been disabled, therefore all EJBs will be initialized during application start.
Action None.
WSVR0059I: EJB jar stopped: {0}
Explanation The specified EJB jar has been stopped as part of application shutdown activities.
Action None.
WSVR0062E: Unable to start EJB, {0}: {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0068E: Attempt to start EnterpriseBean {0} failed with exception: {1}
Explanation An error has occurred during the initialization and start of an EnterpriseBean {0}.
Action Take action recommended in the message associated with exception {1}.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0073W: Unable to read required resource: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0100W: An error occurred initializing, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0101W: An error occurred starting, {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0102E: An error occurred stopping, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0103E: An error occurred destroying, {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0107W: Duplicate component, {0}, in file {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0110I: EJB Timer Service is disabled.
Explanation The EJB Timer Service has been disabled by configuring the number of threads to zero, EJBs implementing the javax.ejb.TimedObject interface will not function properly.
Action If the EJB Timer Service is to be used on this node it must be enabled by setting the number of threads greater than zero.
WSVR0111W: EJB Timer Service could not be started, EJBs implementing the TimedObject interface will not function properly.
Explanation The EJB Timer Service may 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 Configured poll interval for the EJB Timer Service is not set properly.
Action Change the configured poll interval for the EJB Timer Service to a supported value.
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 Configured number of threads for the EJB Timer Service is not set properly.
Action Change the configured number of threads for the EJB Timer Service to a supported value.
WSVR0114I: MessageDrivenBean Listener is disabled.
Explanation The MessageDrivenBean Message Listener has been disabled by either not installing or disabling the Messaging Service, EJBs implementing the javax.ejb.MessageDrivenBean interface will not function properly.
Action If MessageDrivenBeans are to be used on this node a Messaging Service must be installed and enabled.
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 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", but the value specified was not within the valid range.
Action Change 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", but the value specified was not a valid integer.
Action Change 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 may be disabled.
Action Verify 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0150E: Missing entry for {0} in {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0200I: Starting application: {0}
Explanation Starting application, {0}.
Action This is an informational message. 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0202E: Application, {0}, failed to start
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0203I: Application: {0} Application build level: {1}
Explanation The application {0} has the specified application build level {1}.
Action This is an informational message. No action is required.
WSVR0204I: Application: {0} Application build level: Unknown
Explanation The application {0} does not have a specified application build level.
Action This is an informational message. 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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 EJB jar has failed to start.
Action Look for error messages that appear between this message and the preeceeding WSVR0037I message. If you find one, it may be related to the cause of this message. If none is found, use the exception that appears as part of this message as a possible cause of this message.
WSVR0209E: Unable to start EJB jar {0}, enterprise bean {1}
{2}
Explanation An EJB has failed to start.
Action Verify the EJB jar that contains the failed EJB {1} has been deployed and look for error messages that appear between this message and the preeceeding WSVR0037I message.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0211W: Duplicate library, {0}, defined in {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0217I: Stopping application: {0}
Explanation Application, {0}, is stopping
Action This is an informational message. 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0219I: Application, {0}, is disabled
Explanation Application, {0}, is disabled and thus not started.
Action This is an informational message. No action is required.
WSVR0220I: Application stopped: {0}
Explanation Application, {0}, is stopped.
Action This is an informational message. No action is required.
WSVR0221I: Application started: {0}
Explanation Application, {0}, is started.
Action This is an informational message. No action is required.
WSVR0222E: Module stop operation not permitted on Module, {0}, of application, {1}
Explanation The WAR classloader scope prohibits module stop operations.
Action The WAR classloader scope must be set such as to provide a isolated WAR classloader.
WSVR0223E: Module stop operations not permitted on Module, {0}, of application, {1}
Explanation Stop operations are not allowed on modules of this type.
Action Perform the stop operation on the appplication instead.
WSVR0224E: Module start operations not permitted on Module, {0}, of application, {1}
Explanation Start operations are not allowed on modules of this type.
Action Perform the start operation on the appplication instead.
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 This is an informational message. No action is required.
WSVR0226I: User initiated module start operation request completed on Module, {1}, of application, {0}
Explanation An MBean or AdminConsole request to start or update a module has successfully been processed.
Action This is an informational message. No action is required.
WSVR0227I: User initiated module stop operation requested on Module, {1}, of application, {0}
Explanation An MBean or AdminConsole request to stop a module is being processed, this may be occuring as the result of application update.
Action This is an informational message. No action is required.
WSVR0228I: User initiated module stop operation request completed on Module, {1}, of application, {0}
Explanation An MBean or AdminConsole request to stop a module has successfully been processed.
Action This is an informational message. 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0241I: Undefined WebSphere variable "{0}" encountered while parsing string "{1}".
Explanation An undefined WebSphere variable was encountered while parsing a string. This variable may be optional.
Action Define the WebSphere variable if it is not optional. If variable substitution is not intended, then $$ should be used as escape sequence. Otherwise, use the correct syntax like ${VAR_NAME}.
WSVR0242E: Unterminated WebSphere variable reference encountered while parsing string "{0}".
Explanation An unterminated WebSphere variable reference was encountered while parsing a string, meaning a closing parenthesis is missing in the string definition.
Action Verify the string definition for any unterminated WebSphere variable reference with missing parenthesis.
WSVR0243E: Recursive WebSphere variable reference "{0}" encountered.
Explanation A recursive WebSphere variable reference was encountered while parsing a string, meaning a variable is referenced recursively in a variable definition.
Action Check for any recursive WebSphere variable references in the WebSphere variable configuration.
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 may be disabled.
Action Verify the message listener service is enabled.
WSVR0315E: The configuration data for the thread pool named {0} contains an invalid entry, this threadpool is not avaiable for use.
Explanation The maximum size must be greater tha zero, and also greater than or equal to the minimum size.
Action Verify (via the admin console) the maximum and minimum size of the threadpool are specified correctly.
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 classloader, the classloading mode of that classloader takes precedence over the deprecated classloading mode of the web module itself.
Action The configuration is usable. However, to stop receiving this message, update the classloading mode of the web module to match the classloading mode of the contained classloader. Also, be aware of the deprecation of the web module deployment classloading mode.
WSVR0321I: The module deployment, {0}, contains a classloader. That classloader will be ignored.
Explanation The configuration model allows a classloader to be contained by module deployments other than web module deployments. Classloaders contained by module deployments other than web module deployments have no effect.
Action The configuration is usable. No configuration update is required. However, to stop receiving this message, remove the classloader that is contained by the noted module deployment.
WSVR0330E: An exception occurred while trying to retrieve the list of files in the directory {0}.
Explanation There may be a problem with the permissions associated with this directory.
Action Verify the permissions on this directory.
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.
WSVR0400W: Unable to register the {0} MBean
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0401W: Unable to deregister the {0} MBean
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0402W: Invalid MBean name {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0501E: Error creating component {0}
{1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0600W: No thread context
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0602W: Attempt to access javaNameSpace from a ComponentMetaData that does not support a javaNameSpace.
Explanation Only Web-Components and EJB-Components support access to the javaNameSpace.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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.
Explanation A thread has been active for an extended period. This may indicate that the thread is hung, including deadlock and infinite loop situations.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 has now completed.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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 CMP which is configured to use a Connection Factory resource is not available. The CMP bean will not function because the resource is not defined by the administrator.
Action Create this Connection Factory by ensuring this data source is selected for CMP use in the administrative console.
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 given in the warning 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 This is an informational message. 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 had 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 ObjectRequestBroker service ThreadPool has been replaced by a ThreadPoolManager service ThreadPool with the same name.
Action This value is still used in this release, but will be removed in a future release. You may update the ThreadPoolManager service ThreadPool configuration to match the ObjectRequestBroker service configuration and remove the ObjectRequestBroker service configuration.
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 directory is meant to be used for temporary patches. Classes contained in this directory will override WebSphere classes.
Action Verify that the classes contained in the directory are compatible with the version of WebSphere installed.
Reference topic    

Terms of Use | Feedback

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

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