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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | This is a Web Container exception which can be caused by one of three things: 1. An error occured while preinvoking the security collaborator. 2. An error occured while processing the server connection. 3. An error occured while processing the servlet request. |
Action | Examine the server logs to determine the root cause of the problem. |
Explanation | This is a transport error which occurs when bad data has been encountered. |
Action | If this problem persists, check the transport configuration that is associated with the transport that is causing the error. |
Explanation | This internal error occurs when the plug-in forces the application server dispatchers to handle more than one request at a time. |
Action | Check the logs for an IllegalStateException which should occur just before this error. |
Explanation | This is a Web Container exception which can be caused by one of three things: 1. An error occured while preinvoking the security collaborator. 2. An error occured while processing the server connection. 3. An error occured while processing the servlet request. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Pooled resources don't contain any SQEvents |
Action | No user action is required. |
Explanation | Problems occured when closing the server queue. |
Action | Examine server logs for exceptions. |
Explanation | The virtual host containing requested application is not found. |
Action | Check the virtual host on which application is installed. Make sure virtual host configuration has alias with host and port defined as invoked by clients. |
Explanation | This error occured because of a bad or missing X.509 certificate. |
Action | Check the logs for the exception to see the exact trace. Regenerate or obtain a new certificate if the error persists. |
Explanation | An error occured while processing a queued service event. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This error occured because two installed applications were found to have the same context root (path). This may lead to indeterminate behaviour. |
Action | One of the applications will need to be uninstalled, and then reinstalled using a different context root. If for some reason itis not possible to uninstall and reinstall, contact IBM support. |
Explanation | This is an internal system error and is probably caused by an earlier failure.. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The specified transport name is not valid. |
Action | Define a transport conforming to the transport definition rules. |
Explanation | Failed to add the web group specified in the message to the web container. |
Action | Check the definitions for the web group (web module) in web.xml. |
Explanation | Error in the JNDI service. |
Action | Be sure that you have defined a JNDI service and that its port is not in use by another application. |
Explanation | Connection queue has overflowed. |
Action | Increase the size of the connection queue. |
Explanation | iiopredirector XML contains invalid XML syntax |
Action | Examine the iiopredirector xml for syntax conformance. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Attempting to output a buffer of size less than 0. |
Action | Only write buffers of size of 0 or greater. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Initialization parameter name not found. |
Action | Specify a parameter name in the web.xml file. |
Explanation | Uncaught exception created in servlet service method. |
Action | Varies by root cause. |
Explanation | Could not initialize the web application specified in the message. |
Action | Check all definitions for this web application (web module) in the application.xml and web.xml files. |
Explanation | Invalid format found for a request header. |
Action | Check client header creation. |
Explanation | Could not find the specified web group (web module). |
Action | Be sure the web group is defined and deployed. Also check to be sure that a host and port have been defined for your virtual hosts and that there are no host/port conflicts across your virtual hosts. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An error was encountered in the specified servlet. |
Action | Varies by reported cause. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Could not find a definition for the specified virtual host. |
Action | Verify that the virtual host is defined in the virtualhosts.xml file. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Could not set an attribute. |
Action | Make sure the attribute conforms to attribute guidelines. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | An error was encountered in the specified servlet. |
Action | Varies by reported cause. |
Explanation | Class specified to object pool is not accessible. |
Action | Be sure the class is on the object pool's classpath. |
Explanation | Error encountered reading plug-in configuration. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Could not shutdown server. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The specified path is not a directory. |
Action | Make sure the directory exists or that you are requesting the right directory. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | Error encountered stopping a transport. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | WebAppSecurityCollaborator. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | A remote object is not serializable. |
Action | Be sure your remote objects implement the Serializable interface. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Problem invoking the specified servlet. |
Action | Be sure the servlet is defined and accessible. |
Explanation | Total read equals zero. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Internal error encountered. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Could not find the specified resource for a servlet. |
Action | Be sure the resource exists and has been defined. |
Explanation | JarFileClassProvider is invalid. File has been updated. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | An error occurred during a servlet destroy. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | The specified servlet is being loaded for service. |
Action | No user action is required. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Internal engine error. |
Action | Gather server logs and contact IBM service. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Invalid date format. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Servlet is being destroyed after wait has timed out. |
Action | No action is required. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Input class is not poolable. |
Action | Implement the IPoolable interface in the input class. |
Explanation | Could not destroy specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Could not bind the specified host name to the specified serlvet host. |
Action | Make sure the host name has been specified correctly and that the servlet host has been specified in virtualhosts.xml. |
Explanation | The specified directory is not valid. |
Action | Check directory specification for errors. |
Explanation | Using first server specification found. |
Action | No action is required. |
Explanation | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | Unable to restart a web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | AdminListener. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Could not invoke service method for the specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | Exception received in http transport. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | The specified attribute is not supported. |
Action | Remove the attribute from any XML file that contains it. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Could not load the specified Web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | A request or response serviced by a servlet is not of type HTTP. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | No servlet host found. |
Action | Verify that the virtual hosts are defined in the virtualhosts.xml. |
Explanation | Internal server error. |
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 | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Could not find the specified resource. |
Action | Be sure the resource exists. |
Explanation | Failure to restart WebGroup. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Could not initialize the default server. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Could not remove an attribute. |
Action | The attribute might not have been present. Be sure attribute exists and retry. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Could not get the specified remote attribute. |
Action | Could be caused by connectivity problems. Wait and try again. |
Explanation | The specified servlet could not be found. |
Action | Make sure the servlet exists and is defined properly in the web.xml file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Specified servlet is temporarily unavailable. |
Action | Wait and retry operation. Servlet might have been removed from service by server administrator. |
Explanation | Could not start the transport for the administration service. |
Action | Gather logs and contact IBM support. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Could not instantiate a class for use by the object pool. |
Action | Be sure the class exists and is visible on the application classpath. |
Explanation | Could not initialize the specified servlet. |
Action | Make sure the servlet class file is available on the application classpath. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Two initialization parameters have the same xml id. |
Action | Make sure all initialization parameters have unique id's. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Problem releasing a session. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Unable to remove the specified remote attribute. |
Action | Potentially a network problem. Wait and try again. |
Explanation | Servlet is no longer available for service. |
Action | Restart the web application containing the servlet. |
Explanation | Missing flag value. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Failure to create distributed attribute list. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Could not find a virtual host for the web application. |
Action | Be sure the web application is bound to a valid virtual host. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Problem invoking the specified error reporter. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | The integer format is not valid. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | IO error encountered. |
Action | Varies depending on reported root cause. |
Explanation | Attempting to output a buffer of size less than 0. |
Action | Only write buffers of size of 0 or greater. |
Explanation | The specified servlet host could not be found. |
Action | Be sure the virtual host specifications in virtualhosts.xml are valid. |
Explanation | A servlet encountered the specified error. |
Action | Varies by root cause. |
Explanation | Problem encountered while shutting down the server. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | The specified initialization parameter is missing a value. |
Action | Be sure the definition for the parameter in the web.xml file is complete. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Internal server error. |
Action | Gather server logs and contact IBM Service. |
Explanation | Problem encountered invoking the specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | The server connection was reset. |
Action | Retry any previously failing operations. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The content length is not valid. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Problem encountered parsing servlet parameters. |
Action | Check parameter definitions in the web.xml file. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Problem encountered disabling the specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Security problem encountered during request processing. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Security problem encountered during request processing. |
Action | Varies with root cause. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Servlet mapping defined with the specified servlet, but servlet was not defined. |
Action | Make sure the servlet is defined in the web.xml file. |
Explanation | Could not find the bindings for the web application. |
Action | Be sure that the ibm-web-bnd.xmi file exists for the application. |
Explanation | Number format problem in the specified environment entry. |
Action | Correct the environment entry. |
Explanation | The type encountered in java:comp binding is not valid. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Failure starting a server transport. |
Action | Be sure that the defined transport port is not in use by another application. |
Explanation | A virtual host has not been bound to the specified web module. |
Action | Specify a virtual host in the web application's ibm-web-bnd.xmi file. |
Explanation | Unable to load the specified WAR file. Most likely a definition problem. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Could not find the definition for the specified web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Problem encountered reading the web module definition for the web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | A resource defined in the web application is empty. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Problem encountered reading the web module definition for the web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Problem encountered removing the specified web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Could not load the specified file. |
Action | Be sure the specified file exists. |
Explanation | Could not load the specified file. |
Action | Be sure the specified file exists. |
Explanation | An attempt was made to set the response buffer size after the response was already commited. |
Action | Remove the setBufferSize() call or move it to a position before the response commit. |
Explanation | Could not determine the context path for a web application. |
Action | Be sure a context path has been defined for the web application in the application.xml file. |
Explanation | Could not load the specified session context. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Problem encountered rolling back the specified user transaction. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | Application server identifier. |
Action | No action is required. |
Explanation | The servlet specification level supported by the application server. |
Action | No action is required. |
Explanation | The JSP specification level supported by the application server. |
Action | No action is required. |
Explanation | Two web applications on the same virtual host share the same context root. |
Action | Either change the context root of one of the web applications or move one to a different virtual host. |
Explanation | Could not restart the specified web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | No virtual host has been bound to the web application. Using default. |
Action | If a different virtual host is desired, specify one in the web application bindings. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Session manager has not been configured for the web container. |
Action | Define the session manager properties in the server.xml file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A JSP file that is deployed in web.xml and is indicated to load-on-startup failed to translate or compile. |
Action | Examine the server logs in order to determine the root cause of the failure. If there are no related messages or they do not help to resolve the problem, contact IBM Support. |
Explanation | LocalTransaction rolled-back due to setRollbackOnly action by the application |
Action | Examine the server logs to determine the root cause of the failure. Also check your application for setRollBackOnly calls. |
Explanation | A Java ServerPages (JSP) file that uses server-side Javascript with the BSF engine has been detected. |
Action | Replace the server-side Javascript with other mechanisms, such as Java ServerPages (JSP) Version 2.0 Expression Language. |
Explanation | The specified keystore or truststore type is not valid. |
Action | Modify the Secure Sockets Layer (SSL) configuration so that the keystore or truststore type is a valid type. You can check the keystore and truststore types by loading them in iKeyMan tool, which is located in the install_root/bin directory. |
Explanation | A problem has occured attempting to access a resource provided by a resource manager (such as a database). |
Action | Ensure the expected resource managers and resources are accessible. For example, ensure that all data sources are correctly defined. |
Explanation | An SQLException occured when attempting to close a connection to the resource manager. |
Action | No action is required, as this should not affect the running of the transaction service. |