Explanation | The platform uses symbolic paths to provide rudimentary protection from arbitrary access to the file system when the location service is used to resolve specified paths. README.TXT contains information about how symbolic paths are configured. |
Action | Check bootstrap.properties for configured paths, and ensure that the configured path is a child of existing symbols or is associated with an explicitly defined symbol. |
Explanation | The path specified for a symbol exists, and is a different type of resource than the path specifies (for example, the symbol describes a file, but the resource is a directory). |
Action | Ensure the path is specified correctly. Directory paths must end with a /. Ensure the path refers to a resource that either does not exist, or exists and is of the required type. |
Explanation | The directory specified as the java.io.tmpdir (either through a system property or a platform-specific environment variable) does not exist and could not be created. |
Action | Ensure the specified directory exists and has read/write permissions. |
Explanation | The directory specified as the java.io.tmpdir (either through a system property or a platform-specific environment variable) was relative, and is resolved relative to the launch directory. |
Action | No action is required. |
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/ . |
Explanation | The framework is shutting down because of a previous error during initialization. |
Action | Resolve the error then restart the server. |