CWWKZ

CWWKZ0001I: Application {0} started in {1} seconds.

Explanation

The server has started the application successfully.

Action

No action is required.

CWWKZ0002E: An exception occurred while starting the application {0}. The exception message was: {1}

Explanation

The server could not start the application.

Action

Read the exception message for information.

CWWKZ0003I: The application {0} updated in {1} seconds.

Explanation

The server has updated the application successfully.

Action

No action is required.

CWWKZ0004E: An exception occurred while starting the application {0}. The exception message was: {1}

Explanation

The server could not update the application.

Action

Read the exception message for further information.

CWWKZ0005E: The server is not configured to handle the resource at location {0}.

Explanation

The server is not currently configured with all the required features for resources of this type, so the resource could not be started.

Action

Modify the server configuration to include all the features that are required to support this type of resource.

CWWKZ0006E: The server could not create a download location at {0} for the {1} application.

Explanation

When trying to download an application to install, the server could not create the download directory.

Action

Ensure that there is enough disk space for the download.

CWWKZ0007W: An exception occurred while downloading the file from {0}. The exception message was: {1}

Explanation

The server could not download the application.

Action

If you intended the server to download the application, check that the file is available for download.

CWWKZ0008E: An internal error has occurred. The system could not get the location service that is required to resolve file locations.

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/ .

CWWKZ0009I: The application {0} has stopped successfully.

Explanation

The server has stopped the application successfully.

Action

No action is required.

CWWKZ0010E: An exception occurred while stopping the application {0}. The exception message was: {1}

Explanation

The server could not stop the application.

Action

Ensure that the application is in a state where it can be stopped.

CWWKZ0011E: An exception occurred while searching for the file {0}. The exception message was: {1}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWWKZ0012I: The application {0} was not started.

Explanation

The application could not be started because of earlier errors.

Action

Check the application configuration and check the logs for errors during the application start.

CWWKZ0013E: It is not possible to start two applications called {0}.

Explanation

The application name must be unique. This might be because two applications have been configured to have the same name, or a single application has been deployed both by configuration in the server.xml file and by putting the application in the dropins directory.

Action

If two applications have the same name, remove or rename one of the applications. If a single application has been deployed in two different ways, change the configuration so that only one deployment method is used.

CWWKZ0014W: The application {0} could not be started as it could not be found at location {1}.

Explanation

When trying to start the application, the server could not find the application at the specified location (or relative locations if it was a relative path).

Action

Check that the location defined is correct for the application.

CWWKZ0015E: An application has been configured with no location or name.

Explanation

An application has been configured without specifying a location or a name.

Action

Update the configuration to add a location.

CWWKZ0016E: The application {0} has not been configured with a location.

Explanation

An application has been configured without specifying a location.

Action

Update the configuration to add a location.

CWWKZ0017E: It was not possible to infer the application type for application {0} from the location {1}.

Explanation

An application was configured without specifying a type. The type could not be determined from the location.

Action

Update the configuration to add a type.

CWWKZ0018I: Starting application {0}.

Explanation

The application is being started.

Action

No action is required.

CWWKZ0019I: Application {0} partly started in {1} seconds. The server will continue to start the application in the background.

Explanation

The whole application could not start. This might happen with an ear containing two wars where only one war will start.

Action

Resolve the problem with the part of the application that could not start and redeploy the application.

CWWKZ0020I: Application {0} not updated.

Explanation

The application could not be started because of earlier errors.

Action

Check the application configuration and check the logs for errors during the application start.

CWWKZ0021E: The server is not configured to handle the resource at location {0}.

Explanation

The server is not currently configured with all the required features for resources of this type, so the resource could not be started.

Action

Modify the server configuration to include all the features that are required to support this type of resource.

CWWKZ0022W: Application {0} has not started in {1} seconds.

Explanation

The application did not start in the expected time. This could be because the server is overloaded or the application is large. If the application is starting as part of server startup, the server startup will finish without waiting for the application to start.

Action

If the application takes a long time to start then no action is required; otherwise check the server logs to see if other messages indicate a cause.

CWWKZ0053E: An exception occurred while trying to stop the {0} application automatically.

Explanation

The application monitor could not find the application running on the server.

Action

No action is required.

CWWKZ0054E: The application monitoring service could not find a suitable name for the {0} application.

Explanation

The application monitoring service uses the file name, without the extension, to generate the application name. The application monitoring service could not determine an application name after the extension was removed from the file name.

Action

Ensure that the file name for the application does not start with a period (.) and has a name before the file extension.

CWWKZ0055E: The application monitoring service could not determine the type of the {0} application.

Explanation

The application monitoring service could not determine the type of the application from either its file extension or parent directory.

Action

Ensure that the file for the application either has an file extension that identifies the application type, or is under a directory whose name identifies the application type.

CWWKZ0056E: An exception occurred while trying to automatically start the {0} application.

Explanation

The application monitor could not start the application.

Action

No action is required.

CWWKZ0057E: When reading the cached list of started applications from the application monitor ({0}), line number {1} was not valid. The line was: {2}.

Explanation

The application monitor could not read the list of all started applications.

Action

Start the server with a cold start.

CWWKZ0058I: Monitoring {0} for applications.

Explanation

The server is monitoring a directory for applications to be deployed.

Action

No action is required.

CWWKZ0059E: The {0} application installed from {1} has been deleted while it is still configured.

Explanation

An application that is currently configured in the server.xml file has been deleted.

Action

If the deletion was intentional, remove the application configuration from the server.xml file.

CWWKZ0060E: The server could not clean up the old monitored directory at {0}.

Explanation

The old directory could not be removed even though it is no longer in use.

Action

If the old directory is no longer needed, remove it. If it is still needed no action is required.

CWWKZ0060W: Unable to monitor the {0} application.

Explanation

An application was installed but monitoring was not started on it so if a file is updated within the application the change will not be detected by the server.

Action

When updating files in this application the application will need to be uninstalled and re-installed into the server.

CWWKZ0061E: Application {0} at location {1} is inside the monitored directory {2}. The application element will be ignored.

Explanation

An application element in the server configuration has defined the location of the application to be inside the directory that is monitored for applications. As a result the application element will be ignored, and the application will be started using the contents of the monitored directory if the application is present in that the monitored directory.

Action

Either correct the application element or change the location of the monitored directory.

CWWKZ0062I: The {0} application has been updated, but not restarted.

Explanation

A minor change has occurred in the specified application, and the change has been deemed minor enough that there is no need to restart the application.

Action

No action is required.

CWWKZ0063I: Default setting for use of Jandex has been modified to true for all applications.

Explanation

For all applications, and when Jandex indexes are available, class and annotation data is obtained from Jandex indexes, unless Jandex usage is disabled specifically for the application.

Action

No action is required.

CWWKZ0064I: Jandex use is enabled for application {0}.

Explanation

For the specified application, when Jandex indexes are available, class and annotation data is obtained from Jandex indexes.

Action

No action is required.

CWWKZ0065I: Jandex use is disabled for application {0}.

Explanation

Jandex index is disabled for the specified application.

Action

No action is required.

CWWKZ0066E: The following applications cannot start because the value of their startAfter attributes result in a cycle: {0}

Explanation

None of the applications can start because each one depends on one of the other applications to be started first.

Action

Change the value of the startAfter attribute for applications involved in the cycle so that they do not have circular dependencies.

CWWKZ0067W: The drop-ins application at location {0} cannot start because it is also configured.

Explanation

An application in the server configuration specifies a location in the monitored drop-ins directory.

Action

Move the application to a different location.

CWWKZ0101E: The file {0} could not be copied to location {1} during the start of the {2} application.

Explanation

Before the application is started, the application file is copied to a new location. The file copy operation did not succeed, so the application was not started.

Action

Examine the source and destination file locations to see if the problem can be resolved.

CWWKZ0102E: The ear file {0} could not be extracted to location {1}. The exception message was: {2}

Explanation

The server could not start the application, because the ear file could not be extracted.

Action

Read the exception message for information. Additional details might be available in the exception log.

CWWKZ0103E: The ear file {0} could not be extracted to location {1}.

Explanation

The server could not start the application, because the ear file could not be extracted.

Action

Examine the ear file to ensure it is a valid archive.

CWWKZ0104E: The directory {0} could not be created during the start of the {1} application.

Explanation

Before the application is started, a directory is created. The directory create operation did not succeed, so the application was not started.

Action

Examine the directory location to see if the problem can be resolved.

CWWKZ0105E: The bundle context was not available to start the {0} application.

Explanation

The server could not start the application. This might be an internal error.

Action

Examine the message and exception logs for related errors.

CWWKZ0106E: Could not start web application {0}.

Explanation

An earlier error prevented the application from being installed.

Action

Check the location in the application configuration.

CWWKZ0107E: An internal error occurred. Unable to adapt cache for web module {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWWKZ0107E: An internal error occurred. Unable to adapt cache for web module {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWWKZ0108E: The application manager is unable to adapt cache for connector module {0}

Explanation

An internal error occurred during the installation of a connector module. The module info was not added to the cache.

Action

See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

CWWKZ0111E: Application {0} encountered a error when accessing application library {1}: {2}

Explanation

An internal error occurred when accessing the contents of the library. That library will not available for use.

Action

Review the contents of the application to ensure that an archive is present for the library.

CWWKZ0112E: Application {0} encountered an error when listing application libraries: {1}

Explanation

An error occurred while listing application libraries. The list of application libraries will be incomplete.

Action

See the exception information for additional details.

CWWKZ0113E: Application {0} encountered a parse error when processing application descriptor {1}: {2}

Explanation

An error occurred while parsing the application descriptor. No modules will be available for the application.

Action

See the exception information for additional details. Review the contents of the application descriptor to ensure that the contents are valid as XML data.

CWWKZ0113E: Application {0} encountered a parse error when processing application descriptor {1}: {2}

Explanation

An error occurred while parsing the application descriptor. No modules will be available for the application.

Action

See the exception information for additional details. Review the contents of the application descriptor to ensure that the contents are valid as XML data.

CWWKZ0114E: Application {0} encountered an error when accessing the contents of module {1} of type {2}: {3}

Explanation

An internal error occurred when accessing the contents of the module. The module will not be made available for use.

Action

See the exception information for additional details.

CWWKZ0115E: Application {0} obtained a null value when accessing the contents of candidate module {1} of type {2}

Explanation

An internal error occurred when accessing the contents of a module. The application may be missing an archive for the module. The module will not be made available for use.

Action

Review the contents of the application to ensure that an archive is present for the module.

CWWKZ0116E: Application {0} failed to finish creation of module {1} of type {2}: {3}

Explanation

An internal error occurred while finishing creation of a module. The module will not be made available for use.

Action

See the exception information for additional details.

CWWKZ0117E: Application {0} failed to locate module {1} of type {2}

Explanation

No archive is available for a module listed in the application descriptor. The module will not be made available for use.

Action

See the exception information for additional details. Review the contents of the application to ensure that an archive is present for the module.

CWWKZ0118E: Application {0} encountered a parse error when processing descriptor {1} of module {2} of type {3}: {4}

Explanation

An error occurred while parsing the module deployment descriptor. The module will not be made available for use.

Action

See the exception information for additional details. Review the contents of the application descriptor to ensure that the contents are valid as XML data.

CWWKZ0120E: Application {0} failed to access classes for module {1} of type {2}: {3}

Explanation

An internal error occurred while attempting to scan a JAR file for EJB annotations. The JAR will not be available as an EJB JAR.

Action

See the exception information for additional details.

CWWKZ0121E: Application {0} failed to access annotations for module {1} of type {2}: {3}

Explanation

An internal error occurred while attempting to scan a JAR file for EJB annotations. The JAR will not be available as an EJB JAR.

Action

See the exception information for additional details.

CWWKZ0122W: Application {0} declares multiple modules with URI {1} in META-INF/application.xml.

Explanation

Multiple modules point to the same archive. Only one module will be made available for use.

Action

Review the contents of the application descriptor to ensure that each module points to a unique archive.

CWWKZ0123E: Application {0} failed to read the META-INF/MANIFEST.MF file for the {1} module. Exception: {2}

Explanation

While trying to determine if the module is an EJB or an application client module, an error occurred trying to read the META-INF/MANIFEST.MF file. This module will not be treated as an application client module.

Action

See the exception information for additional details. Review the contents of the application to ensure that the META-INF/MANIFEST.MF path is a file and not a directory, and ensure that the MANIFEST.MF file is valid.

CWWKZ0124E: Application {0} does not contain any modules.

Explanation

The application does not declare any modules in the application.xml file, and the application does not contain any module archives.

Action

Add a module archive to the application, and restart the application.

CWWKZ0125E: Application {0} does not contain the Main-Class attribute in the META-INF/MANIFEST.MF file of the {1} module.

Explanation

The META-INF/MANIFEST.MF file in the module either does not exist or does not contain the Main-Class attribute. This module will not be treated as an application client module.

Action

Make sure that the META-INF/MANIFEST.MF file for the application contains the Main-Class attribute.

CWWKZ0126W: The {0} context root value that is specified on the {1} application has no effect.

Explanation

The context-root property is not valid for an enterprise application. The value will not be used for any web modules contained within the enterprise application.

Action

Remove the context-root property from the application element in the server configuration.

CWWKZ0127E: There are multiple client modules in the application. Provide the default client module name.

Explanation

If there are multiple client modules packaged in the application, provide the client module name to run.

Action

Specify the client module to run by providing its name using defaultClientModule attribute in <enterpriseApplication/>.

CWWKZ0128E: There are multiple client modules with the same name {0}.

Explanation

There are multiple client modules and some of them are using the same name.

Action

Provide unique names for the client modules in the application.

CWWKZ0129E: Cannot find the client module {0} in the application.

Explanation

The specified client module does not exist in the application.

Action

Make sure the client module exists in the application.

CWWKZ0130E: Could not start application client {0}.

Explanation

An earlier error prevented the application from being installed.

Action

Check the location in the application configuration.

CWWKZ0131W: Could not expand the application {0} because of the exception {1}.

Explanation

The application could not be expanded to a temporary directory. The application will continue to run but behavior of certain methods that access application files may be affected.

Action

Attempt to resolve the issue in the exception message and either restart the server or update the application.

CWWKZ0132W: The file {0} in the archive {1} will not be extracted because the path is not contained within the archive.

Explanation

The file's path specifies a relative directory. Extracting the file would result in the file being located outside of the archive's root directory.

Action

Remove any files with relative paths from the archive.

CWWKZ0133I: The {0} application at the {1} location is being expanded to the {2} directory.

Explanation

The archive file for the application is being expanded because automatic expansion of applications was configured.

Action

No action is required.

CWWKZ0134I: The {0} application is using the loose application definition at the {1} location.

Explanation

The location for the application points to an XML file that defines a loose application.

Action

No action is required.

CWWKZ0135I: The {0} application is using the expanded directory at the {1} location.

Explanation

The location for the application points to a directory rather than an archive file.

Action

No action is required.

CWWKZ0136I: The {0} application is using the archive file at the {1} location.

Explanation

The location for the application points to a binary archive file. The archive file will not be expanded on disk because automatic expansion of applications was not configured.

Action

No action is required.

CWWKZ0137W: Could not expand the {0} application at the {1} location that is specified by the expandLocation property.

Explanation

The application could not be expanded to the location specified by the expandLocation property. The ${server.config.dir}/apps/expanded/ default location was used for the application.

Action

Correct the value that is specified by the expandLocation property and either restart the server or update the application.

CWWKZ0201E: An error occurred initializing the WAB installer.

Explanation

The server could not initialize the Web Application Bundle (WAB) installer, so WABs have not been installed.

Action