CWWKE

CWWKE0001I: The server {0} has been launched.
CWWKE0002I: The kernel started after {0}
CWWKE0003I: The bootstrap locations have changed, so the server will be clean started.
CWWKE0004E: The system could not resolve locations for server installation.
CWWKE0005E: The runtime environment could not be launched.
CWWKE0006E: Please enable the orb feature for ORB support.
CWWKE0007E: The system did not successfully convert the following file from EBCDIC to ASCII: {0}
CWWKE0008E: The bootstrap properties URI is malformed. uri={0}, reason={1}
CWWKE0009E: The system cannot find the following file and this file will not be included in the server dump archive: {0}
CWWKE0010E: The required server.xml file must exist and be readable. Path: {0} Reason: {1}
CWWKE0011E: The --archive parameter requires an argument: --archive="<file to archive>"
CWWKE0012E: The specified server name contains a character that is not valid (name={0}). Valid characters are: Unicode alphanumeric (e.g. 0-9, a-z, A-Z), underscore (_), dash (-), plus (+), and period (.). A server name cannot begin with a dash (-) or period (.).
CWWKE0013E: Unknown option: {0}
CWWKE0014E: The system could not open or read the specified bootstrap properties. Path: {0} Reason: {1}
CWWKE0015E: Internal errors occurred while starting the server.
CWWKE0016E: The bootstrap JAR file requires the AllPermission security configuration in order to launch the runtime environment and the OSGi framework ({0}).
CWWKE0017E: The process detected a 31-bit JVM that is not supported. The runtime environment requires 64-bit Java 8 version or higher.
CWWKE0018E: An exception occurred while launching the runtime environment: {0}
CWWKE0019E: The required framework definition was not specified.
CWWKE0020E: The specified framework definition ({0}) does not exist.
CWWKE0021E: The specified framework bundle ({0}) does not exist.
CWWKE0022E: The required kernel definition was not specified.
CWWKE0023E: The specified kernel definition ({0}) does not exist.
CWWKE0024E: The ({0}) value for the ({1}) option is not valid.
CWWKE0025E: The value of {0} must refer to a directory. The specified value references an existing file resource. Value: {1}
CWWKE0026W: The system could not write the platform cache file ({0}). Exception: {1}
CWWKE0027W: Only one server may be specified on the command line; subsequent names will be ignored (server={0}, ignored={1}).
CWWKE0028E: The ({0}) option is not applicable for the command.
CWWKE0029E: An instance of server {0} is already running.
CWWKE0030E: An exception occurred while creating server {0}. serverPath: {1} Reason: {2}
CWWKE0031E: Specified {0} server does not exist; use the create action to create a new server. serverPath: {1}
CWWKE0032E: One or more exceptions occurred while installing platform bundles.
CWWKE0033E: Platform bundles could not be found.
CWWKE0034E: No bundles were installed, please verify install image.
CWWKE0035E: There was a problem with the specified initial log file. logPath={0}
CWWKE0036I: The server {0} stopped after {1}.
CWWKE0037E: {0} is not a supported console protocol. The telnet protocol will be used instead.
CWWKE0038E: The required log provider was not specified.
CWWKE0039E: The specified log provider JAR file or bundle ({0}) does not exist.
CWWKE0040E: The platform bundles could not be resolved against the cache. Restart the server with a clean start.
CWWKE0041I: The platform cache is out of sync. Restarting the framework.
CWWKE0042E: The correct Java version is not running. The runtime environment requires Java 8 or higher.
CWWKE0043E: The launch location is not a local file. ({0})
CWWKE0044E: There is no write permission for server directory {0}
CWWKE0045E: It was not possible to create the server called {0} because the server directory {1} already exists.
CWWKE0046E: An implementation of the Java Attach API could not be found.
CWWKE0047E: The process control agent stopped with an unexpected exception {0}
CWWKE0048W: A running instance of the server with name {0} and server directory {1} could not be found.
CWWKE0049E: Server {0} could not be stopped.
CWWKE0050E: Could not initialize server command listener. Server directory {0} is not valid.
CWWKE0051E: Server {0} could not be packaged.
CWWKE0052E: Failed to initialize the server command listener because of an IO exception {0}
CWWKE0053W: Unrecognized command {0}
CWWKE0054E: Unable to open file {0}.
CWWKE0055I: Server shutdown requested on {0,date,full} at {0,time,short}. The server {1} is shutting down.
CWWKE0056E: Unable to zip up directory due to an IO exception {0}.
CWWKE0057I: Introspect request received. The server is dumping status.
CWWKE0058W: Unable to use option --include={0}, will use --include=all instead.
CWWKE0059W: Unable to write file {0} due to an IO exception {1}.
CWWKE0060W: Ignoring iFix jar {0} because base jar {1} does not exist.
CWWKE0061W: The z/OS coded character set identifier for encoding {0} does not exist. Text files will not be tagged.
CWWKE0062W: Text files will not be tagged because __chattr service failed with errno {0}.
CWWKE0063W: Unable to register the native method with descriptor name {0}.
CWWKE0064E: Unable to load z/OS native library from {0}.
CWWKE0065E: An exception occurred while creating server {0}. External activity was detected at the server path ({1}) so the server creation was stopped.
CWWKE0066E: A directory cannot be created for the {0} server at the following location: {1}.
CWWKE0067I: Java dump request received.
CWWKE0068I: Java dump created: {0}
CWWKE0069W: Java dump type {0} is not supported.
CWWKE0070W: The loose file {0} is invalid.
CWWKE0071W: Ignoring interim fix {0} because base version {1} does not exist.
CWWKE0072E: The BLST specification string {0} is invalid. The specification must be of the form: <symbolic-name>;version="<version-range>".
CWWKE0073E: Failed to resolve the BLST file for {0}.
CWWKE0074E: Failed to locate the platform directory.
CWWKE0075E: Failed to read the kernel version range from the bootstrap manifest.
CWWKE0076E: Unable to query server {0} to determine features to retain.
CWWKE0077E: Unable to stop server {0}, started to determine features to retain.
CWWKE0078E: Unable to determine features to retain for server {0}.
CWWKE0079E: Packaging the server {0} failed due to a missing server manifest.
CWWKE0080E: Unable to load property {0} in file {1}.
CWWKE0081E: Unable to package server {0} with requested operating system filter {1} due to missing resource {2}.
CWWKE0082E: Unable to package server {0} due to an IO exception {1}.
CWWKE0083E: The --os parameter can only be used with --include=minify.
CWWKE0084I: The server {0} is stopping because thread {1} ({2}) called the method {3}: {4}
CWWKE0085I: The server {0} is stopping because the JVM is exiting.
CWWKE0086E: The {0} option must include an equals sign (=) before the specified value.
CWWKE0087W: Server start was initiated for server {0}, but it is not possible to tell if startup was completed because the server command port is disabled.
CWWKE0088W: Server start was initiated for server {0} with process ID {1}, but it is not possible to tell if startup has completed because the server command port is disabled.
CWWKE0089E: Server {0} could not be stopped because the server command port is disabled.
CWWKE0090W: Server {0} dump complete in {1}. Some information could not be obtained because the server command port is disabled, preventing direct communication with the running server.
CWWKE0091E: Server {0} dump could not be taken because the server command port is disabled.
CWWKE0092I: Java System Transaction Dump (SYSTDUMP) request is complete.
CWWKE0093W: The server could not create the location {0} when trying to write the file {1}.
CWWKE0094W: The server cannot package the application files because one or more location symbols in the {0} file is unknown.
CWWKE0095W: The server cannot package application files specified in the {0} loose configuration application XML file because it cannot find them.
CWWKE0096W: Too many symbolic links were encountered when the system tried to resolve the following path: {0}.
CWWKE0099W: Unable to use option --include={0}, will use --include=wlp instead.
CWWKE0100I: This product is licensed for development, and limited production use. The full license terms can be viewed here: {0}
CWWKE0101I: This product is licensed for development use. The full license terms can be viewed here: {0}
CWWKE0101W: The specified parameter is not a string or string array. {1}={2} for {0}
CWWKE0102E: The system is not able to determine the Java specification level from the system properties. The value is not specified or not specified correctly. The system properties contains the following value for java.specification.level: {0}
CWWKE0102W: The specified parameter is not a string or string collection. {1}={2} for {0}
CWWKE0103E: Unable to create a server.env file in the following location: {0}
CWWKE0103W: The specified parameter does not represent a boolean value. {1}={2} for {0}
CWWKE0104I: This product is a beta and cannot be used in production. The full license terms can be viewed here: {0}
CWWKE0104W: The specified parameter does not represent a long value. {1}={2} for {0}
CWWKE0105E: Starting server {0} using the z/OS STC procedure {1} might have failed before the PID file was created. Check STC output for verification.
CWWKE0105W: The specified parameter does not represent an integer value. {1}={2} for {0}
CWWKE0106E: The z/OS STC procedure {0} failed to start. The start returned with MGCRE return code {1}.
CWWKE0106W: The specified parameter does not represent an integer array. {1}={2} for {0}
CWWKE0107E: The z/OS STC procedure {0} could not be started. The maximum length of the start command has been exceeded.
CWWKE0107W: The specified parameter does not represent a duration value. {1}={2} for {0}
CWWKE0108I: The product extension {0} was programmatically enabled. The product identifier of the product extension is {1}. The product install location of the product extension is {2}.
CWWKE0200E: The specified location is unreachable. It is not a child of a known or configured path; path={0}.
CWWKE0201E: Unable to create symbol; the specified location exists, and conflicts with required type: {0}={1}.
CWWKE0202E: The specified temporary directory location does not exist and could not be created: {0}.
CWWKE0203I: The java.io.tempdir was specified with a relative path. The resolved path is {0}.
CWWKE0204E: Unable to initialize the platform location service; reason={0}.
CWWKE0205W: The framework is shutting down because of a previous initialization error.
CWWKE0400W: The specified parameter does not specify a valid file name filter. {0}={1}
CWWKE0401W: The specified parameter does not represent a valid monitoring interval. {0}={1}
CWWKE0402W: The specified cache location could not be allocated, so all information about monitored files will be stored in memory. {0}={1}
CWWKE0403W: An exception occurred while creating a monitor for {0}. Monitoring for this resource is disabled. The exception message was: {1}
CWWKE0404E: The cache file {0} could not be deleted.
CWWKE0405W: An exception occurred while notifying a monitor of the following file creations, modifications, and deletions: {0}, {1}, {2}. The monitor class is {3}. The exception message was: {4}
CWWKE0406W: More than {0} exceptions occurred while notifying a monitor of changes. The monitor class is {1}. This FileMonitor has now been disabled.
CWWKE0500E: Input console is not available.
CWWKE0501E: Unable to read input from console. The exception message is: {0}.
CWWKE0502E: Unknown task: {0}.
CWWKE0503E: The version file {0} was not found.
CWWKE0504E: Unable to read the file {0}. The exception message is: {1}.
CWWKE0505E: Unable to write the file {0}. The exception message is: {1}.
CWWKE0506E: Unable to initialize the task {0}. The exception message is: {1}.
CWWKE0507E: The product checksums file {0} was not found.
CWWKE0508E: The checksum file {0} can not be loaded.
CWWKE0509E: A malformed Unicode escape appears in the file {0}. The exception message is: {1}.
CWWKE0510E: There is no properties file under this directory {0}.
CWWKE0511E: The version properties directory {0} does not exist.
CWWKE0512E: {0} is not a directory.
CWWKE0513E: Unable to read the file {0}.
CWWKE0514E: An invalid option, {0}, was supplied on the command line. Valid options are: [{1}]
CWWKE0600E: This tool requires a Java SDK, but it was launched using a JRE: {0}
CWWKE0601E: This tool requires a Java compiler to be available. Ensure that the java.compiler module is available.
CWWKE0651E: A server {0} command was received, but the infrastructure for pausing components is not available. The request cannot be processed.
CWWKE0700W: {0} {1} {2} {3}
CWWKE0701E: {0} {1} {2} {3}
CWWKE0702E: {0}
CWWKE0703I: {0} {1} {2} {3}
CWWKE0704A: {0} {1} {2} {3}
CWWKE0800W: An attempt was made to retrieve an initial context for [{0}] but no JNDI feature is configured.
CWWKE0900E: The specified client name contains a character that is not valid (name={0}). Valid characters are: Unicode alphanumeric (e.g. 0-9, a-z, A-Z), underscore (_), dash (-), plus (+), and period (.). A client name cannot begin with a dash (-) or period (.).
CWWKE0901W: Only one client may be specified on the command line; subsequent names will be ignored (client={0}, ignored={1}).
CWWKE0902E: An exception occurred while creating client {0}. clientPath: {1} Reason: {2}
CWWKE0903E: Specified {0} client does not exist; use the create action to create a new client. clientPath: {1}
CWWKE0904E: It was not possible to create the client called {0} because the client directory {1} already exists.
CWWKE0905E: An exception occurred while creating client {0}. External activity was detected at the client path ({1}) so the client creation was stopped.
CWWKE0906E: An exception occurred while creating client {0} at location {1}.
CWWKE0907I: The client {0} has been launched.
CWWKE0908I: The client {0} stopped after {1}.
CWWKE0909I: Server {0} started with Java 2 Security enabled
CWWKE0910E: Failure to set the default Security Manager due to exception: {0}. This occurs if the security manager has already been set and its checkPermission method does not allow it to be replaced.
CWWKE0911E: Failure to set the NoRethrow Security Manager due to exception: {0}. This occurs if the security manager has already been set and its checkPermission method does not allow it to be replaced.
CWWKE0912W: Current Java 2 Security policy reported a potential violation of Java 2 Security Permission. {0}Permission:{1}Code:{2}{3}Stack Trace:{4}Code Base Location:{5}
CWWKE0913E: An unexpected exception is caught when trying to determine the code base location. Exception: {0}.
CWWKE0914W: The current Java 2 Security policy reported a potential violation of a Java 2 Security Permission. Refer to the Knowledge Center for further information.{0}Permission:{1}Code:{2}Code Base Location:{3}
CWWKE0915W: The current Java 2 Security policy report a potential violation of a Java 2 Security Permission. Stack Trace:{0}
CWWKE0916E: CWWKE0916E: The client feature was not enabled. Review the error messages.
CWWKE0917E: The client application reported an error.
CWWKE0918E: Unable to perform the requested operation. Refer to the logs on Liberty profile server {0} on host {1} at location {2} for request {3} for details.
CWWKE0919I: Offending class is: {0}
CWWKE0920I: At code base location: {0}
CWWKE0921W: Current Java 2 Security policy reported a potential violation of Java 2 Security Permission. {0}
CWWKE0922E: The package command cannot complete because the installation is missing the lib/extract directory.
CWWKE0923I: A request was received to pause all pause capable components in the server.
CWWKE0924I: A request was received to pause the following components in the server: {0}
CWWKE0925I: A request was received to resume all paused components in the server.
CWWKE0926I: A request was received to resume the following components in the server: {0}
CWWKE0927E: A pause request was received, but the infrastructure for pausing components is not available. The request cannot be processed.
CWWKE0928E: A resume request was received, but the infrastructure for pausing components is not available. The request cannot be processed.
CWWKE0929E: A pause request completed, but the following components failed to pause: {0}
CWWKE0930E: A resume request completed, but the following components failed to resume: {0}
CWWKE0931W: A request was received to pause specific components, but the component list on the target option was empty. No action was taken.
CWWKE0932W: A request was received to resume specific components, but the component list on the target option was empty. No action was taken.
CWWKE0933W: A pause request was received, but no pause capable components were found in the server. No action was taken.
CWWKE0934W: A resume request was received, but no pause capable components were found in the server. No action was taken.
CWWKE0935W: A pause request was received, but the following components could not be found: {0}
CWWKE0936W: A resume request was received, but the following components were not found: {0}
CWWKE0937W: A status request was received, but the following components were not found: {0}
CWWKE0938I: A pause request completed.
CWWKE0939I: A resume request completed.
CWWKE0940I: The {0} product extension has a product identifier of {1} and a product installation location of {2}. This product extension was enabled by specifying the WLP_PRODUCT_EXT_DIR environment variable.
CWWKE0941W: The variable declaration {0} specified in server.env is invalid because it contains non-alphanumeric characters in the variable name. The value will not be used.
CWWKE0942E: The z/OS STC procedure {0} failed to start. The procedure name is not valid. Ensure that the procedure name is no longer than eight characters and does not contain a comma.
CWWKE0943E: The z/OS STC procedure {0} failed to start. The {1} job name is not valid. Ensure that the job name is no longer than eight characters and does not contain a comma.
CWWKE0944E: A pause request was received for server {0}, but the server command port is disabled. The request cannot be processed. Enable the command port, and try again.
CWWKE0945E: A resume request was received for server {0}, but the server command port is disabled. The request cannot be processed. Enable the command port, and try again.
CWWKE0946W: A status request was received for specific components, but the component list on the target option was empty. No action was taken.
CWWKE0947E: Unexpected operating system memory information was encountered in {0}: {1}
CWWKE0947W: A --server-root option with an empty argument is not allowed when Product Extensions are installed. The default argument of wlp will be used.
CWWKE0948E: Available memory information is not implemented on this operating system.
CWWKE0948W: A --server-root option with --include=runnable is not an allowed combination. The default argument of wlp is used for the server root.
CWWKE0949E: Page size information is not implemented on this operating system.
CWWKE0950E: The {0} program failed to run. The return code is {1}. The output is {2}
CWWKE0950E: The archive filename must end with .jar when the runnable option is used.
CWWKE0951E: The archive file name must not end with a .jar file extension when the usr option is used.
CWWKE0952E: Version information cannot be read from the directory {0}.
CWWKE0953W: This version of {0} is an unsupported early release version.
CWWKE0954E: The specified ({0}) checkpoint phase is empty or unknown.
CWWKE0955E: The websphere.java.security property was set in the bootstrap.properties file but the Java version is {0}. This property enables the Java Security Manager and is not valid with Java 18 or later.
CWWKE0956E: Failed to set the Java Security Manager due to exception: {0}. This occurs if the server is using Java 18 or later, and the Java system property "java.security.manager" was not set to "allow".
CWWKE0957E: The checkpoint server workarea directory cannot be restored from the {0} directory.
CWWKE0958E: The server checkpoint request failed because the websphere.java.security property was set in the bootstrap.properties file. This property enables the Java Security Manager and is not valid when a server checkpoint occurs.
CWWKE0959E: The server checkpoint request failed because the existing checkpoint image cannot be deleted from the {0} directory.
CWWKE0960E: The server checkpoint request failed because the {0} directory cannot be backed up.
CWWKE0961I: Restoring the checkpoint server process failed. Check the {0} log to determine why the checkpoint process was not restored. Launching the server without using the checkpoint image.
CWWKE0962E: The server checkpoint request failed. The following output is from the CRIU {0} file that contains details on why the checkpoint failed.
CWWKE0963E: The server checkpoint request failed because netlink system calls were unsuccessful. If SELinux is enabled in enforcing mode, netlink system calls might be blocked by the SELinux "virt_sandbox_use_netlink" policy setting. Either disable SELinux or enable the netlink system calls with the "setsebool virt_sandbox_use_netlink 1" command.
CWWKE0964E: Restoring the checkpoint server process failed. Check the {0} log to determine why the checkpoint process was not restored. The server did not launch because checkpoint restore recovery is disabled.
CWWKE0965W: The {0} server lock file does not exist.
CWWKE0966W: The {0} server command file does not exist.
CWWKE0967W: A timeout occurred while waiting for the server to release the {0} server lock file.
CWWKE0968W: A timeout occurred while waiting for the server process to stop.
CWWKE0969W: A manual PREFERRED_PLATFORM_VERSION environment variable was specified during server packaging.
CWWKE0970E: Unable to read the server.env file at the {} location.
CWWKE1100I: Waiting for up to {0} seconds for the server to quiesce.
CWWKE1101I: Server quiesce complete.
CWWKE1102W: The quiesce operation did not complete. The server will now stop.
CWWKE1103I: Waiting for up to {0} seconds for the client to quiesce.
CWWKE1104I: Client quiesce complete.
CWWKE1105W: {0} runtime updates did not complete during the quiesce period.
CWWKE1106W: {0} shutdown operations did not complete during the quiesce period.
CWWKE1107W: {0} threads did not complete during the quiesce period.
CWWKE1200W: All threads in the Liberty default executor appear to be hung. Liberty automatically increased the number of threads from {0} to {1}. However, all threads still appear to be hung.
CWWKE1201E: A task cannot be submitted to executor {0} because the task queue with maxQueueSize of {1} remains at capacity after waiting {2} nanoseconds.
CWWKE1202E: A task cannot be submitted because the executor {0} has been shut down.
CWWKE1203E: Configuration update to {0} is not permitted because the executor {1} has been shut down.
CWWKE1204E: Executor {0} was unable to submit {1} of the {2} tasks within the allotted interval of {3} {4}.
CWWKE1205E: The {0} executor was unable to start the {1} task after {2} nanoseconds because the task exceeded its startTimeout of {3} nanoseconds.
CWWKE1206W: The ''{0}'' value that is specified for the ''quiesceTimeout'' attribute on the ''executor'' element in the ''server.xml'' file is not valid. The default value of 30 seconds is used instead.