WebSphere Process Server messages     Operating Systems: All supported
CWLAG0201E: The Artifact Loader encountered an error while indexing the archive file {0}. The system returned the following error: {1}.
Explanation: The archive file is a malformed .jar, .rar, .ear, or .zip file.
User Action: Replace the malformed file with a correct one and make sure it is accessible if you need it. If you do not need it, remove it.

 

CWLAG0202E: The Artifact Loader encountered an error while indexing the directory {0}. The system returned the following error: {1}.
Explanation: A file path or a subdirectory path in the directory was parsed as a malformed URL.
User Action: Find the file or directory name in the exception message, and add read and write access to it for the current user to make sure it is accessible to the Artifact Loader.

 

CWLAG0203E: The Artifact Loader encountered an error while searching artifacts for the class loader {0}. The system returned the following error: {1}.
Explanation: The Artifact Loader cannot index the class loader, so some of the contents in the class loader may not be loadable. The most likely reason is that there is a malformed archive file in the class path of the class loader.
User Action: Find the malformed archive file in the exception message and replace the file with a well-formed one.

 

CWLAG0204I: The Artifact Loader is activated for module {0}.
Explanation: This is an informational message.
User Action: No action is required.

 

CWLAG0205I: The Artifact Loader is initialized for module {0}.
Explanation: This is an informational message. The application run time can now use the Artifact Loader to load artifacts.
User Action: No action is required.

 

CWLAG0246E: The Artifact Loader encountered the following error while relaying the state event to the listener: {0}.
Explanation: The most likely reason for this error is that the relayed listener component encountered an error when processing the state event.
User Action: In the log file, find the exception in the listener component area, which is before the Artifact Loader area. The exception includes instructions for fixing the problem. Follow those instructions.

 

CWLAG0253W: The Artifact Loader cannot open a file. The system returned the following error: {0}.
Explanation: A likely cause of the error is that the file specified in the error is corrupt.
User Action: Use WebSphere Integration Developer to check the error in the file, fix the error, and then redeploy the revised enterprise archive (EAR) file.

 

CWLAG0254W: The Artifact Loader tried to close a file but was not successful. The system returned the following error: {0}.
Explanation: The Artifact Loader tried to close the specified file, but failed. The file might be in use by another active process.
User Action: Identify the process that is using the specified file and end the process, or close all unnecessary applications and restart the server.

 

CWLAG0300E: The Artifact Loader cannot find the application "{0}" in the same cell. The error is {1}.
Explanation: A likely cause of the problem is that the application is not installed in the cell or was not installed successfully.
User Action: Ensure the specified application is deployed on any server in the same cell, or reinstall the application if it did not install successfully.

 

CWLAG0301E: The Artifact Loader cannot find the application "{0}" in the destination {1}. The error is {2}.
Explanation: The remote Artifact Loader cannot retrieve the specified artifact in the remote application. A possible cause of this problem is that the destination server is not running or the application is not installed on the destination.
User Action: If the destination server is not running, start it. If the application is not installed, install it and make sure it is running on the server.

 

CWLAG0302E: The remote Artifact Loader cannot query the application {0}. The error is {1}.
Explanation: A likely cause of the problem is that the Remote Artifact Loader application is stopped.
User Action: Start the RemoteAL application on the remote server from the administration console of WebSphere Application Server.

 

CWLAG0303I: The Artifact Loader activated the MBean {0}.
Explanation: This is an informational message.
User Action: No action is required.

 

CWLAG0305W: The Artifact Loader failed to connect to MBean on {0}. The error is {1}.
Explanation: The remote server or its MBean might be stopped.
User Action: Restart the remote server. If the error persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.

 

CWLAG0306I: The AdminTask command {0} executed successfully for the RALConfiguration {1}.
Explanation: This is an informational message.
User Action: No action is required.

 

CWLAG0307I: The editRALServerSecurity method executed successfully.
Explanation: This is an informational message.
User Action: No action is required.

 

CWLAG0450W: The document "{0}" cannot be parsed for the following reason: {1}.
Explanation: The document located by the Artifact Loader is malformed or is missing.
User Action: 1.If the file exists, use WebSphere Integration Developer to ensure that the document is well-formed. 2. If the file is missing, find the artifact file that specifies the schemaLocation to the missing document in the application, change it to a valid location, and then redeploy the enterprise archive (EAR) file.

 

CWLAG0502E: The Artifact Loader found the schema location {0}, which cannot be converted into a URL. The system returned the following error: {1}.
Explanation: A likely cause of the problem is that the URL in the schemaLocation attribute is not valid, so the application cannot load the specified file according to the schemaLocation setting.
User Action: In the error message, find the artifact file that specifies the problem schemaLocation in the application. In the file, change attribute setting to a valid one, and then redeploy the enterprise archive (EAR) file.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009