WSVR

WSVR0001I: Server {0} open for e-business
WSVR0002I: Server {0} open for e-business, problems occurred during startup
WSVR0003E: Server {0} failed to start
{1}
WSVR0004E: The server name, {0}, is not a valid name.
WSVR0005I: Server {0} open for recovery.
WSVR0006I: Server recovery complete. Process stopping.
WSVR0007E: Could not find the {0} object in {1}
WSVR0008E: Error encountered reading {0}
{1}
WSVR0009E: Error occurred during startup
{0}
WSVR0010I: Server {0} open for recovery, problems occurred during startup.
WSVR0016W: Classpath entry, {0}, in Resource, {1}, located at {2} has an invalid variable
WSVR0017E: Error encountered binding the J2EE resource, {0}, as {1} from {2}
{3}
WSVR0018E: An exception occurred starting Eclipse:
{0}
WSVR0018W: Unable to create CustomService, {0}
{1}
WSVR0019E: An exception occurred starting Eclipse. See the log file {0}.
WSVR0019W: CustomService, {0}, failed to initialize.
{1}
WSVR0020W: CustomService, {0}, failed to shutdown.
{1}
WSVR0021W: Native path entry, {0}, in Resource, {1}, located at {2} has an invalid variable
WSVR0022W: The value, {0}, with Resource ID, {1}, located at {2} has an invalid variable
WSVR0023I: Server {0} is stopping
WSVR0024I: Server {0} stopped
WSVR0025I: Creating temporary product license
WSVR0025W: The native paths specified for isolated resource provider {0} will be ignored.
WSVR0026I: Error occurred while validating product license
WSVR0026W: The class paths for the isolated resource provider {0} were updated, but the changes will not be applied until the server is restarted.
WSVR0027I: The product will expire in {0} days.
WSVR0028I: The product has expired.
Please re-install or purchase the product.
WSVR0030E: ORB not initialized
WSVR0031E: Unable to load container
{0}
WSVR0032E: Object Adapter created already
WSVR0033E: Unable to load security collaborator, {0}
{1}
WSVR0034W: Invalid passivation directory specified: {0}
WSVR0035E: Failure to initialized the container: {0}
WSVR0036E: Failure to obtain initial naming context: {0}
WSVR0037I: Starting EJB jar: {0}
WSVR0038I: No JNDI name found for {0}, binding home name as {1}
WSVR0039E: Unable to start EJB jar, {0}: {1}
WSVR0040E: addEjbModule failed for {0}
{1}
WSVR0041I: Stopping EJB jar: {0}
WSVR0042E: Unable to stop {0}: {1}
WSVR0043E: Unbind failed for {0}: {1}
WSVR0044E: Unable to stop EJB jar, {0}: {1}
WSVR0045E: Unable to create sub-context {0}: {1}
WSVR0046E: Unable to bind, {0}: {1}
WSVR0047E: Batch naming operation failed : {0}
WSVR0048W: Binding {0} failed, no JNDI name found
WSVR0049I: Binding {0} as {1}
WSVR0051W: Attempted to register a URL Provider, {0}, with a null protocol
WSVR0052W: Attempted to unregister URLProvider with null protocol
WSVR0055W: Unexpected objectToKey method callback for object {0}.
WSVR0056W: Tie class of {0} can not be found.
WSVR0057I: EJB jar started: {0}
WSVR0058I: All EJBs will be initialized during application start
WSVR0059I: EJB jar stopped: {0}
WSVR0062E: Unable to start EJB, {0}: {1}
WSVR0064W: Minimum threads for pool {0} was less than 0; changing from {1} to 0
WSVR0065W: Maximum threads for pool {0} was less than 1; changing from {1} to 1
WSVR0066W: Maximum threads for pool {0} was less than the minimum; changing from {1} to {2}
WSVR0067E: EJB container caught {0} and is throwing {1}.
WSVR0068E: Attempt to start EnterpriseBean {0} failed with exception: {1}
WSVR0071W: Nothing registered before for interface, {0}, override ignored for implementation, {1}
WSVR0072W: Ignoring undeclared override of interface, {0}, with implementation, {1}
WSVR0073W: Unable to read required resource: {0}
WSVR0100W: An error occurred initializing, {0}
{1}
WSVR0101W: An error occurred starting, {0}
WSVR0102E: An error occurred stopping, {0}
{1}
WSVR0103E: An error occurred destroying, {0}
{1}
WSVR0104E: No type or class defined in {0} at line {1}
WSVR0105E: Both type, {0}, or class, {1}, are defined in {2} at line {3}
WSVR0106E: Invalid startup value {0} at line {1}
WSVR0107W: Duplicate component, {0}, in file {1}
WSVR0108W: Invalid attribute {0} in file {1} at line {2}
WSVR0109I: Component {0} not started since it is not specified for this platform in file {1} at line {2}
WSVR0110I: EJB Timer Service is disabled.
WSVR0111W: EJB Timer Service could not be started, EJBs implementing the TimedObject interface will not function 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}.
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}.
WSVR0114I: Message-driven Enterprise JavaBean (EJB) message listener is disabled.
WSVR0115I: WebSphere RemoteObject cache size set to {0}.
WSVR0116W: WebSphere RemoteObject cache size ({0}) not in valid range. Using default value ({1}).
WSVR0117W: WebSphere RemoteObject cache size ({0}) not a valid integer. Using default value ({1}).
WSVR0119W: Unable to find MultibrokerDomain service, stateful session bean failover will not occur.
WSVR0120E: An error occurred processing {0}
{1}
WSVR0121E: An exception occurred getting a socket for port {0} on hostname {1} with an IP address of {2}.
{3}
WSVR0124E: Failed to look up service {0}. Component {1} marked disabled
WSVR0150E: Missing entry for {0} in {1}
WSVR0151E: The {0} component implements the {1} service, which is duplicated and ignored.
WSVR0152E: The {0} component is a duplicate component ID. The duplicate component has been disabled.
WSVR0153E: A single components element must be defined for the {0} extension point in the {1} bundle..
WSVR0154E: A components child element must be defined for the {0} extension point in the {1} bundle..
WSVR0155E: Only component type elements must be defined for the {0} extension point in the {1} bundle..
WSVR0156E: Either the class or type attribute must be specified in the component definition for the {0} extension point in the {1} bundle.
WSVR0157E: A startup value, which is specified for the {0} component class and the {1} extension point within the {2} bundle, is not valid.
WSVR0158E: A startup value, which is specified for the {0} component type and the {1} extension point within the {2} bundle, is not valid.
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.
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.
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.
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..
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.
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.
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.
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.
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.
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.
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.
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.
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.
WSVR0172E: In the {0} component for the {1} extension point within the {2} bundle, a child element value is not valid.
WSVR0173W: A metadata error occurred for the {0} component for the {1} extension point within the {2} bundle.
WSVR0174W: A duplicate component has been ignored. Ignore the {0} component for the {1} extension point within the {2} bundle.
WSVR0175E: The Application Server cannot locate the {0} component, which is a mandatory dependency for the {1} component. The {1} component has been disabled.
WSVR0176E: The following exception has occurred in the configAnalyzer class: {0}
WSVR0177E: The {0} component is disabled..
WSVR0178I: The runtime provisioning feature is enabled. Some components will be started as they are needed.
WSVR0179I: The runtime provisioning feature is disabled. All components will be started.
WSVR0180E: Server {0} on node {1} was not found.
WSVR0190I: Starting composition unit {0} in BLA {1}.
WSVR0191I: Composition unit {0} in BLA {1} started.
WSVR0192I: Stopping composition unit {0} in BLA {1}.
WSVR0193I: Composition unit {0} in BLA {1} stopped.
WSVR0194E: Composition unit {0} in BLA {1} failed to start.
WSVR0195E: Composition unit {0} in BLA {1} failed to stop.
WSVR0200I: Starting application: {0}
WSVR0201E: Application, {0}, failed to initialize
{1}
WSVR0202E: Application, {0}, failed to start
{1}
WSVR0203I: Application: {0} Application build level: {1}
WSVR0204I: Application: {0} Application build level: Unknown
WSVR0205E: Module, {0}, of application, {1}, failed to initialize
WSVR0206E: Module, {0}, of application, {1}, failed to start
WSVR0207W: Another application edition {0} is running. Please stop it first. Failed to start application edition {1}.
WSVR0208E: Unable to start EJB jar: {0}
{1}
WSVR0209E: Unable to start EJB jar {0}, enterprise bean {1}
{2}
WSVR0210W: No modules defined for application, {0}, on server, {1}
WSVR0211W: Duplicate library, {0}, defined in {1}
WSVR0212W: Library, {0}, defined in {1} does not exist
WSVR0213W: Classpath entry, {0}, in library, {1}, located at {2} has an invalid variable
WSVR0214W: Application, {0}, already initialized.
WSVR0215W: Starting application, {0}, failed. The application is not installed.
WSVR0216W: Stopping application, {0}, failed. The application is not started.
WSVR0217I: Stopping application: {0}
WSVR0218W: No modules defined for application, {0}, on server, {1}, in cluster, {2}
WSVR0219I: Application, {0}, is disabled
WSVR0220I: Application stopped: {0}
WSVR0221I: Application started: {0}
WSVR0222E: Module stop operation not permitted on Module, {0}, of application, {1}
WSVR0223E: Module stop operations not permitted on Module, {0}, of application, {1}
WSVR0224E: Module start operations not permitted on Module, {0}, of application, {1}
WSVR0225I: User initiated module start operation requested on Module, {1}, of application, {0}
WSVR0226I: User initiated module start operation request completed on Module, {1}, of application, {0}
WSVR0227I: User initiated module stop operation requested on Module, {1}, of application, {0}
WSVR0228I: User initiated module stop operation request completed on Module, {1}, of application, {0}
WSVR0230E: Invalid uri format encountered while processing cross document link: {0}
WSVR0231E: Unrecognized resource type encountered during Application startup: {0}
WSVR0232E: Unable to resolve cross document link identified by the uri: {0}, and referenced by document {1}
WSVR0233W: The configuration for the isolated shared library {0} was updated, but the changes will not be applied until the server is restarted.
WSVR0234E: Failed to stop the {0} module in the {1} application.
WSVR0241I: Undefined WebSphere variable "{0}" encountered while parsing string "{1}".
WSVR0242E: Unterminated WebSphere variable reference encountered while parsing string "{0}".
WSVR0243E: Recursive WebSphere variable reference "{0}" encountered.
WSVR0244E: An undefined {0} product variable has been encountered in the {1} property of the {2} configuration object.
WSVR0245E: An unterminated product variable reference has been encountered when parsing the {0} value of the {1} property of the {2} configuration object.
WSVR0246E: A recursive {0} product variable has been encountered in the {1} property of the {2} configuration object.
WSVR0300I: Problems found in {0}
WSVR0301W: Invalid value type, {0}, expecting {1} at line {2}
WSVR0302W: Invalid value, {0}, at line {1}
WSVR0303W: Invalid element tagname, {0}, at line {1}
WSVR0304E: Unsupported encoding, {0}
WSVR0305W: Invalid attribute, {0}, at line {1}
WSVR0306E: Unsupported XMI version
WSVR0307W: Invalid namespace, {0}, at line {1}
WSVR0308W: Unknown package, {0}, at line {1}
WSVR0309E: No packages have been registered
WSVR0310W: Unable to resolve reference for, {0}, at line {1}
WSVR0311W: Unknown exception
{0}
WSVR0312E: Unknown exception
{0}
WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages.
WSVR0314E: Failed to parse {0} at line {1}, column {2}
{3}
WSVR0315E: The configuration data for the thread pool named {0} contains an invalid entry, this threadpool is not avaiable for use.
WSVR0320W: The deployed object classloading mode, {0}, will override the deprecated module deployment classloading mode, {1}, of the web module deployment, {2}.
WSVR0321I: The module deployment, {0}, contains a classloader. That classloader will be ignored.
WSVR0322W: The Java virtual machine classpath of the product contains paths that might cause class loading problems for the product or its applications: {0}
WSVR0330E: An exception occurred while trying to retrieve the list of files in the directory {0}.
WSVR0331I: The {0} class loader plug-in has been loaded.
WSVR0332I: Duplicate package definition detected for package {0}.
WSVR0333W: Setting encodeResourceURLs to false has been deprecated.
WSVR0400W: Unable to register the {0} MBean
{1}
WSVR0401W: Unable to deregister the {0} MBean
{1}
WSVR0402W: Invalid MBean name {0}
{1}
WSVR0403E: The {0} command name is not valid.
WSVR0404E: The {0} server on the {1} node does not exist.
WSVR0405I: Provisioning is enabled.
WSVR0406I: Provisioning is disabled.
WSVR0407E: The {0} command is not supported on the {1} node since it has {2} version of the product.
WSVR0500E: Unable to parse {0} at line {1}, column {3}
{4}
WSVR0501E: Error creating component {0}
{1}
WSVR0600W: No thread context
WSVR0601W: javaURLContext object missing for J2EEName {0}, caught exception
{1}
WSVR0602W: Attempt to access javaNameSpace from a ComponentMetaData that does not support a javaNameSpace.
WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData.
WSVR0604I: Attempt to register EJBContainer MBean: caught exception
{0}
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}
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.
WSVR0607W: Too many thread hangs have been falsely reported. The hang threshold is now being set to {0} seconds.
WSVR0614W: The was.install.root system property is not set. Some product classes might not be found.
WSVR0615W: The user.install.root system property is not set. Some product classes might not be found.
WSVR0616W: Some product classes might not be found.
WSVR0617E: The plugins directory cannot be accessed
WSVR0618E: The target application class failed to load
WSVR0621E: CMP Bean "{0}" is configured to use a CMP Connection Factory JNDI name of "{1}" resource. This resource does not exist.
WSVR0622W: The startup thread pool "{0}" could not be found. A default pool will be used.
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.
WSVR0624I: Server {0} recovery complete. Server stopped.
WSVR0625W: Server {0} recovery complete, problems occurred during recovery. Server stopped. Server log files should contain failure information.
WSVR0626W: The ThreadPool setting on the ObjectRequestBroker service is deprecated.
WSVR0627W: A thread could not be acquired from the ORB thread pool after the maximum wait time of {0} milliseconds was exceeded.
WSVR0628W: The directory "{0}" is not empty and its contents might be overriding WebSphere classes.
WSVR0629I: The request buffer for thread pool "{0}" has reached its capacity.
WSVR0630I: Growable thread pool "{0}" has been expanded beyond its initially-defined maximum capacity. The pool size is currently "{1}".
WSVR0631E: The Selectable Bundle {0} could not be installed into the OSGI server cache at {1}. Exception information: {2}
WSVR0632E: The OSGI server cache directory at {0} could not be deleted. Exception information: {1}
WSVR0633E: The OSGI server cache directory at {0} could not be created. Exception information: {1}
WSVR0634E: Unable to locate ApplicationServer in {0}.
WSVR0635E: Unable to locate Cluster Information in {0}.
WSVR0636E: Unexpected error occurred when attempting to switch selectable bundle implementations. Exception information: {0}
WSVR0637E: An attempt to initialize the AsyncFileOperations service failed. The service is already initialized. The execution stack trace is {0}.
WSVR0638E: An error occurred when the SelectableBundleSyncHandler attempted to dispatch a thread. The exception is {0}.
WSVR0639E: An error occurred while processing asynchronous file operation request by the RuntimeSyncHandler. The exception is {0}.
WSVR0640E: Unable to get Eclipse extension point using the extension point identifier "{0}".
WSVR0641E: Unable to get Eclipse extension registry.
WSVR0642E: Unexpected error occurred while attempting to access the "{0}" Eclipse extension point. Error data: {1}
WSVR0643I: No selectable bundle providers are defined.
WSVR0644E: The Selectable Bundle Provider prefix "{0}" has been previously defined, selectable bundles for this provider will not be processed.
WSVR0645W: Application {0} is deployed, but lacks a composition unit descriptor so cannot start.
WSVR0651I: The {0} growable thread pool has grown to {1} times its initially-configured maximum of {2}.
WSVR0652W: The size of thread pool "{0}" has reached {1} percent of its maximum.
WSVR0653I: Restarting web module {0} of application: {1}.
WSVR0654I: Restarting application: {0}.
WSVR0655I: The {0} application artifact updated at {1}.
WSVR0656W: Support for Java SE 6 with WebSphere Application Server traditional ends in April 2018. To stay current and reduce the risk of security exposures, update to Java SE 8.
WSVR0657E: The server failed to collect endpoint information for the {0} node because the serverindex references an endpoint that does not exist.
WSVR0658E: The server failed to collect endpoint information for the {0} node because the serverindex contains an <endPointRefs> element.
WSVR0659E: The server failed to collect endpoint information for the {0} node because the serverindex contains partial information about the {1} endpoint.
WSVR0660W: Support for Java SE 7.0 and 7.1 with WebSphere Application Server traditional ends in July 2022. To stay current and reduce the risk of security exposures, update to Java SE 8.
WSVR0661W: Some bundles failed to resolve during the {0} server startup. The server logged OSGi bundle diagnostics to the {1} file.
WSVR0662W: Support for WebSphere Application Server traditional on the {0} operating system ends on September 30, 2022. For more information, see https://ibm.biz/WAS_SolarisHPUX_EOS
WSVR0700E: No executable specification found for property: {0}
WSVR0701E: Failed to load Extension class: {0}
WSVR0702W: Invalid Extension Point id: {0}
WSVR0703W: Invalid Extension id: {0}. The OSGi bundle cache might be stale of corrupt. To attempt to resolve this problem, run the osgiCfgInit utility with the -all option to reset all OSGi bundle caches, and then restart the application.
WSVR0704E: Translation not found for id: {0}
WSVR0705E: An error occured parsing {0}, element {1}
WSVR0706E: An error occured parsing plugin descriptor, system id {0}, at line {1}
WSVR0707W: Extension Point ({0}) not available for Extension: {1}
WSVR0708W: No Plugins to resolve
WSVR0710W: The {1} server is configured to use the {0} Java SDK, but this Java SDK version is not available. Instead, the server is starting with the version {2} Java runtime environment.
WSVR0800I: Initializing core configuration models
WSVR0801I: Initializing all server configuration models