Express (Distributed operating systems), v8.0 > Reference > Messages
CWSAH
CWSAH0001E: An internal error occurred. No asset name could be found for the web application {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0002E: An internal error occurred. No application metadata was found for {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0003E: An internal error occurred. No web application bundle static path was found for application {0} for the bundle {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0004E: An internal error occurred. Cannot determine the correct application metadata for the web application bundle {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0005W: No static path was identified for the fragment {1} with version {2} in application {0}.
Explanation The static path for the web application bundle fragment was not found in the application metadata. Action See the exception for details.
CWSAH0006W: Could not identify fragments for bundle {1} in application {0} because of exception {2}.
Explanation The PackageAdmin service cannot identify any fragments on the specified bundle. Action See the exception for details.
CWSAH0007E: An internal error occurred. The runtime environment could not determine the configured context root for bundle {0} in application {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0008E: An error occurred during EventAdmin post: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0009E: An internal error occurred. The runtime environment could not translate the URL {0} from bundle {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0010E: An internal error occurred. The runtime environment could not create the classpath for bundle {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0011E: An internal error occurred. The runtime environment could not start the web bundle {0} because of exception {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0012E: An internal error occurred. The runtime environment could not stop the web bundle {0} because of exception {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0013E: An internal error occurred. The runtime environment could not update the web bundle {0} because of exception {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0014E: An internal error occurred. The runtime environment could not find the temporary directory needed to represent the OSGI application {0} as an EAR.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0015E: An internal error occurred. The runtime environment could not create the temporary directory {0} needed to represent the OSGI application as an EAR.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0016E: An internal error occurred. The runtime environment could not open the EAR {0} representation of the OSGI application.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0017E: An internal error occurred. The runtime environment could not copy the welcome files to the staging directory.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0018E: An internal error occurred. The runtime environment could not delete current content from {0} as requested.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAH0019W: The order of the bundle classpath entries was found to be {0}. This conflicts with the requested processing order for web fragments {1}
Explanation Both Bundle Classpath and Servlet 3 Web Fragments are able to specify an order for processing entries. The bundle classpath is always honored for an OSGi web archive bundle (WAB). If the ordering requested by web fragments is not in agreement with the bundle classpath, then the behavior is undefined. Action If behavior is not as expected, either alter the bundle classpath to the derived processing order for web fragments, or alter the web fragment metadata to create an ordering that matches the bundle classpath.