| 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 | 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| 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 | 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| 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 | The servlet destroy() method created an exception. This exception is an application error. |
| Action | Examine the exception message, the source code of the servlet, and the server logs to determine the root cause of the problem. |
| 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 | One of the service methods of the servlet created an exception. This exception is an application error. |
| Action | Examine the exception message, the source code of the servlet, and the server logs to determine the root cause of the problem. |
| 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 | The content length does not match the length of the post data. This error is an application error. |
| Action | Investigate the client to determine why the content-length field does not match the size of the post data. If the client is setting it correctly, investigate where in the network the content-length field becomes invalid. |
| 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 | An exception occurred when processing the request. |
| Action | Review the message to determine the cause of the error. |
| Explanation | Some data has already been written to the stream, and hence the buffer size can no longer be controlled. This is an application error. |
| Action | Either set the buffer size before writing data or reset the buffer before setting the size. |
| Explanation | A required class was not found. This is an application error. |
| Action | Make sure your class path reflects all of the classes you might be accessing. |
| Explanation | This is an application error. |
| Action | =The class mentioned needs to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet |
| Explanation | This error occurred when the request was being completed. The error could have happened because of a communication error within the Application Server, but should not have affected the processing of the request. This is a system error. |
| Action | None. |
| Explanation | The file was not found. This is an application error. |
| Action | Ensure that the specified file exists in the proper location. |
| Explanation | The attempted operation cannot be performed in an included servlet/JSP (Refer to the Servlet specification). This is an application error. |
| Action | Modify the failing servlet/JSP. |
| Explanation | The parameter name mentioned has no value. This parameter is required. This is an application error. |
| Action | Supply a value to the mentioned parameter. |
| Explanation | Application requested a PrintWriter after the ServletResponse OutputStream had already been obtained. This is an application error. |
| Action | Review application to determine if both PrintWriter and OutputStream were obtained. Modify the failing servlet/JSP to obtain only PrintWriter or OutputStream. |
| Explanation | Servlet could not find a required class that is needed to service the request. This is an application error. |
| Action | Verify that the class exists within the application. |
| Explanation | This is an application error. |
| Action | Modify the failing class to implement javax.servlet.Servlet or extend either javax.servlet.GenericServlet or javax.servlet.http.HttpServlet. |
| Explanation | The servlet class is corrupt. This is an application error. |
| Action | Re-compile the class and try again. |
| Explanation | A required class was not found. This is an application error. |
| Action | Make sure all required classes are placed in the folders and JAR files that represent the class path. |
| Explanation | The virtual host was not found. System action is required. |
| Action | Check the virtual host configuration in the virtualhosts.xml file, or through the administrative console. |
| Explanation | Unable to locate the virtual host that is defined to handle this request URI. System action is required. |
| Action | Check the virtual host configuration in the virtualhosts.xml file, or through the administrative console. |
| Explanation | This is an application error. |
| Action | Re-compile the servlet with all required components placed in the class path. |
| Explanation | The target threw an exception during initialization that was not caught by the user code. This is an application error. |
| Action | Account for the exception in target code. |
| Explanation | The code tried to do an illegal conversion of a header value. For example, from int to data, when such a conversion is not possible. This is an application error. |
| Action | Modify the failing servlet/JSP. |
| Explanation | The writer for this response has already been obtained. Use the existing writer. This is an application error. |
| Action | Review application to determine if both PrintWriter and OutputStream were obtained. Modify the failing servlet/JSP to obtain only PrintWriter or OutputStream. |
| Explanation | This is an application error. |
| Action | Recompile the servlet using only the classes in the application runtime class path. |
| Explanation | Internal exception. |
| 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | Internal exception. |
| 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | Internal exception. |
| 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | Internal exception. |
| 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | The servlet chain that has been defined can handle only requests. This is an application error. |
| Action | None. |
| Explanation | The incoming request might be badly formed or corrupted as a result of a client side application or network error. |
| Action | Review the client side application or network to determine why the request was truncated. |
| Explanation | This error occurred when the web container tried to load an internal implementation class. This is a system error. |
| Action | Check to make sure the original product class path has not been modified. |
| Explanation | The request tried to access a forbidden resource. |
| Action | Make sure the requesting entity has the required privileges. |
| Explanation | DefaultErrorReport was invoked, but no error was found. This is a system error. |
| Action | Review application to determine cause of problem. |
| Explanation | Error that caused the problem. |
| Action | none. |
| Explanation | Cannot serve the contents of a JSP file |
| Action | none. |
| Explanation | none. |
| Action | none. |
| Explanation | none. |
| Action | none. |
| Explanation | none. |
| Action | none. |
| Explanation | Package name of resource does not match the file package for the compiled class. This is an application error. |
| Action | Check that the class resides in the proper package directory. |
| Explanation | This is an application error. |
| Action | Check that the classname has been defined in the server using the proper case and fully qualified package. |
| Explanation | This is an application error. |
| Action | Check that the class was transferred to the file system using a binary transfer mode. |
| Explanation | This is an application error. |
| Action | Check that the class was compiled using the proper case (as defined in the class definition). |
| Explanation | This is an application error. |
| Action | Check that the class file was not renamed after it was compiled. |
| Explanation | An unexpected exception occurred and details were provided on the resulting error page. This is a system error. |
| Action | Check the System.out and System.err logs for more information on the exception generated. |
| Explanation | none |
| Action | none |
| Explanation | none |
| Action | none |
| Explanation | See reported error. |
| Action | none. |
| Explanation | This is a system error. |
| Action | Check the FFDC logs for more details on the error. |
| Explanation | This is a system error. |
| Action | Check the FFDC logs for more details on the error |
| Explanation | This is an application error. |
| Action | Enter a leading slash before the path and try again. |
| Explanation | none. |
| Action | none. |
| Explanation | none. |
| Action | none. |
| Explanation | none. |
| Action | none. |
| Explanation | The init() method of the target resource ran successfully and the target has been places into service. |
| Action | none. |
| Explanation | none. |
| Action | none. |
| Explanation | The reaper thread removes servlets that have been inactive for longer than the reaper inactive limit. |
| Action | none. |
| Explanation | The reaper thread removes the mappings for JSP files and other extensions that have been inactive longer the the reaper inactive limit. |
| Action | None. |
| Explanation | none. |
| Action | none. |
| Explanation | Exception occurred in the reaper thread processing. This is a system error. |
| Action | Reaper processing is a form of garbage collection. |
| Explanation | none. |
| Action | none. |
| Explanation | SyncToOSThread synchronizes the Java EE role identity to the OS thread. The OS thread identity is made equal to the Java EE role identity for the duration of the request. This message indicates that while an application has been configured to use SyncToOSThread functionality, the server it is installed into is not configured to support SyncToOSThread capabilities. System action is required. |
| Action | If SyncToOSThread capabilities are desired for the server in question, refer to the product inf for a description about how to enable SyncToOSThread for a server. |
| Explanation | The specified web module is associated to the virtualhost mentioned, and can be accessed through any of the host/port combinations for that virtualhost. |
| Action | None. |
| Explanation | A thread pool configuration exists under the web container. Changes made to this configuration item will not result in changes in the system. |
| Action | None. |
| Explanation | Transports have been changed to use Channel Chains. Refer to the product docume to review information on Channel Chains, and how to migrate the existing transports to be channel chain based. The thread pool configuration under the web container will not be used to these transports. |
| Action | Use the migration utilities to migrate your configuration model from the transports to the new channel chains. |
| Explanation | The destroy() method of the target resource ran successfully and the target has been removed from service. |
| Action | none. |
| Explanation | The request encoding that is specified on the request is not valid. This is an application error. |
| Action | Review logs to determine whether the specified encoding is a valid encoding. |
| Explanation | Could not find a web group (web module) or virtual host to handle the request. This is an application error. |
| Action | Be sure the web group and virtual host is defined and deployed. |
| Explanation | Web Container is not initialized until an application has been installed. This is a system error. |
| Action | Install an application to initialize the web container. |
| Explanation | A thread is no longer tied to a single connection. System action is required. |
| Action | Refer to the product documentation for more details. |
| Explanation | System action is required. |
| Action | Configure this property under the Logging Service (see the product documentation for more details on HTTP Access Logger). |
| Explanation | The property can no longer be configured at the transport level and must be configured at the web container level. System action is required. |
| Action | Configure this property at the web container level. |
| Explanation | None. |
| Action | See the error page exception for a description of the problem with the specified error page. |
| Explanation | The specified annotation helper has not been defined. This is a system error. |
| Action | Check for the definition of the specified annotation helper and add it if necessary. |
| Explanation | The specified annotation helper is not the expected type. This is a system error. |
| Action | Check the annotation helper implementation class and fix it. |
| Explanation | The specified annotation helper could not be instantiated. This is a system error. |
| Action | Check the exception logs for the reason that the annotation helper could not be instantiated. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | Could not obtain a valid Session Context for the web application. System action is required. |
| Action | Verify that the Session Manager is configured correctly. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | A servlet mapping that is specified in the webconfig.xml file is not valid. System action is required. |
| Action | Check the servlet mappings in webconfig.xml file and make appropriate changes. |
| Explanation | This is an application error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | None. |
| Explanation | This is an application error. |
| Action | Review the logs. |
| Explanation | This is an application error. |
| Action | Check for mapping clash in the webconfig.xml file. |
| Explanation | This is an application error. |
| Action | Verify that the mapping is valid. |
| Explanation | This is an application error. |
| Action | Review the logs. |
| Explanation | This is an application error. |
| Action | Remove the duplicate mapping. |
| Explanation | This is an application error. |
| Action | Set fileServingEnabled=false in the ibm-web-ext.xmi file, which is located in the WEB-INF folder. |
| Explanation | This is an application error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is an application error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | none. |
| Explanation | This is a system error. |
| Action | none. |
| Explanation | This is a system error. |
| Action | none. |
| Explanation | System action is required. |
| Action | Check the status of the directory, including existence, access privileges and available space. |
| Explanation | System action is required. |
| Action | Check the status of the directory, including existence, access privileges and available space. |
| Explanation | Informational message logged for a servlet by use of the ServletContext. |
| Action | none. |
| Explanation | Error exception logged for a servlet by use of the ServletContext. |
| Action | Review the exception to determine the cause of the error and the action required. Additional information for might be available in the server logs. |
| Explanation | Error message and exception logged for a servlet for a servlet by use of the ServletContext. |
| Action | Review the message and exception to determine the cause of the error and the action required. Additional information for might be available in the server logs. |
| Explanation | HttpServletResponse.sendError was called with a status code but no explanation. |
| Action | Review the logs to determine the status code of the error. |
| Explanation | Informational message and exception logged for a servlet by use of the ServletContext.. |
| Action | Review the message and exception to determine if any action is required. Additional information might be available in the server logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | The desired path is already assigned in a servlet mapping. This is an application error. |
| Action | Change or remove the mapping from your application configuration. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | There is no servlet definition for the servlet mapping. |
| Action | Verify that your web.xml file has a servlet definition for this servlet mapping. |
| Explanation | Web Container expects a wrapped request object to be an instance of a class of which it is not. This is an application error. |
| Action | Change code to implement the expected interface. |
| Explanation | The object pool service improves the performance of the web container, but it has been disabled. This is a system error. |
| Action | Enable the object pool service. |
| Explanation | ARD is not enabled correctly. System action is required. |
| Action | Make sure ARD is enabled in the Web Container settings and a dispatch type of CLIENT_SIDE or SERVER_SIDE is specified in the application settings. |
| Explanation | There was no servlet mapping for the filter and it cannot be added. This is an application error. |
| Action | Change the application descriptors to 2.5 level if you are using a * mapping. |
| Explanation | Filtering by asterisk is not allowed because disabling serving all servlets by classname is handled by the com.ibm.ws.webcontainer.disallowserveservletsbyclassname custom property. This is an application error. |
| Action | Set com.ibm.ws.webcontainer.disallowserveservletsbyclassname to true to block serving all classes by classname. |
| Explanation | The requested servlet is on the block list provided by the com.ibm.ws.webcontainer.donotservebyclassname custom property. This is an application error. |
| Action | If this is not the desired behavior, update the com.ibm.ws.webcontainer.donotservebyclassname custom property. |
| Explanation | System action is required. |
| Action | Verify that the custom property is correct. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | This is a system error. |
| Action | Review the logs. |
| Explanation | An exception occurred. |
| Action | Review the logs. |
| Explanation | The request path maps to a context root on a non-matching virtual host. |
| Action | Check to see if an additional virtual host alias needs to be added. |
| Explanation | The request path maps to a context root on a non-matching virtual host. |
| Action | Follow the instructions in the product documentation to add a new virtual host alias. |
| Explanation | A character, which is not valid, exists in the query string and has been ignored. |
| Action | A user action is not required. |
| Explanation | The servlet failed to initialize because an error occurred when a resource was injected. |
| Action | Verify that the injected resources exist and are accessible to the servlet. |
| Explanation | The filter failed to initialize because an error occurred when a resource was injected. |
| Action | Verify that the injected resources exist and are accessible to the filter. |
| Explanation | The filter did not load during start up. |
| Action | Examine the server logs to determine the cause of the error. |
| Explanation | The listener failed to initialize because an error occurred when a resource was injected. |
| Action | Verify that the injected resources exist and are accessible to the listener. To re-initialize the listener, restart the listener application. |
| Explanation | The requests through either the HttpQueueInboundDefault or the HttpQueueInboundDefaultSecure chain might not be properly handled if the Asynchronous Request Dispatcher is not enabled at the server level. |
| Action | If Asynchronous Request Dispatcher is not enabled at the server level, make sure either the WCInboundDefault or the WCInboundDefaultSecure chain is enabled and running. If neither of these chains is running, you must enable the Asynchronous Request Dispatcher if it is not already enabled because the server will send the requests through either the HttpQueueInboundDefault or the HttpQueueInboundDefaultSecure chain. |
| Explanation | Your requests are on the HttpQueueInboundDefault or HttpQueueInboundDefaultSecure chain, but the Asynchronous Request Dispatcher is not enabled at the server level. Therefore, the HttpQueueInboundDefault and HttpQueueInboundDefaultSecure chains might not handle these requests properly. |
| Action | Either enable the Asynchronous Request Dispatcher at the server level, or enable either the WCInboundDefault or the WCInboundDefaultSecure chain, and make sure it is running. |
| Explanation | The number of parameters contained in the inbound request exceeds the maximum number of parameters that can be included in a inbound request. |
| Action | Ensure that all of the parameters in the inbound request are valid, and that the total number parameters does not exceed the maximum allowed per request. |
| Explanation | The number of parameter key hash code collisions exceeds the maximum number of parameter key hash code collisions allowed per inbound request. The parameter keys that generate duplicate hash codes might have been added to the request maliciously, thereby causing a large number of parameter key hash code collisions. |
| Action | Ensure that all of the parameters in the inbound request are valid. |
| 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 | The requested blocking write cannot be completed because nonblocking I/O has already started. |
| Action | Review the application to determine where the blocking write was performed. For example this could be from a servlet after registering the WriteListener, or from a WriteListener which does a second write after calling the isReady() API. Once the blocking write is determined, change the application to ensure it is performed as part of the WriteListener and/or after calling isReady(). |
| Explanation | An exception occurred during the application WriteListener onError() API. |
| Explanation | An exception occurred while creating an instance of the class. As a result, the constructor injection fails. The WebContainer continues with other injections. |
| Action | Review the logs to determine the exception thrown from the application implementation of onError() API and how to address the problem. Note that if an I/O exception occurred, then the onError() API cannot write output. |
| Action | Examine the class to see if construction injection is used. If constructor injection is not used, ignore the message. If constructor injection is used, search the errors logs to determine the cause of the problem. |
| Explanation | A class in the web module could not be initialized so it cannot be scanned for annotations. |
| Action | Verify the class exists and has all of its dependencies in the classpath. |
| Explanation | You can dynamically add servlets only before the ServletContext is initialized. |
| Action | Move the code that is calling the current method into a ServletContainerInitalizer onStartup or a ServletContextListener contextInitialized method. |
| Explanation | You can dynamically add filters only before the ServletContext is initialized. |
| Action | Move the code calling the current method into a ServletContainerInitalizer onStartup or a ServletContextListener contextInitialized method. |
| Explanation | The variable argument URL-pattern parameter passed to ServletRegistration.addMapping must be non-null and not empty. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The variable argument URL-pattern parameter that is passed to ServletRegistration.addMapping must be non-null and not empty. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The variable argument URL-pattern parameter that is passed to FilterRegistration.addMappingForUrlPatterns must be non-null and not empty. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The variable argument URL-pattern parameter that is passed to FilterRegistration.addMappingForUrlPatterns must be non-null and not empty. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The variable argument servlet name parameter passed to FilterRegistration.addMappingForServletNames must be non-null and not empty. |
| Action | Modify the application code according to error the explanation. |
| Explanation | The variable argument servlet name parameter that is passed to FilterRegistration.addMappingForServletNames must be non-null and not empty. |
| Action | Modify the application code according to the error explanation. |
| Explanation | An unexpected internal server error occurred when initializing the target mappings. |
| Action | Collect server logs and contact IBM support. |
| Explanation | One of the servlets or filters in the request does not support asynchronous servlets. |
| Action | Do not use asynchronous servlets or enable asynchronous processing for all the servlets and filters in the chain by adding the async-supported element to the component definitions. |
| Explanation | Certain operations cannot be executed from a programmatically added listener, because there is no configuration option to restrict their execution when they are defined in a Tag Library Descriptor (TLD). |
| Action | Add the listener using an annotation or using the web.xml file to enable the execution of this method. |
| Explanation | You cannot add a ServletContextListener from another ServletContextListener |
| Action | Either add the ServletContextListener to the web.xml file or web-fragment.xml file, annotate it with the @WebListener annotation, or programmatically add it from ServletContainerInitializer#onStartup |
| Explanation | The listener being programmatically added does not implement a valid listener type |
| Action | Modify the application code to add a listener of the accepted type |
| Explanation | An exception occurred while creating the listener instance |
| Action | An exception occurred while creating the listener instance |
| Explanation | An exception occurred while trying to add a listener |
| Action | Verify the listener is a valid type and available to the application |
| Explanation | Some annotations can be applied only to classes that extend the correct type. |
| Action | Modify the class to extend the correct super class. |
| Explanation | The class cannot specify both urlPatterns and value in the annotation. |
| Action | Modify the class to include only one of the urlPatterns or value attribute. |
| Explanation | The class must specify patterns in the annotation with the urlPatterns or value attribute. |
| Action | Modify the class to add one of the urlPatterns or value attributes. |
| Explanation | The class must specify a valid name in the annotation |
| Action | Modify the class to specify a valid name in the annotation |
| Explanation | The servlet does not accept multipart requests. |
| Action | Add a @MultipartConfig annotation to this servlet or add a multipart-config element to this servlet in the web.xml file. |
| Explanation | The file being uploaded with the multipart/form-data request is larger than the maximum configured size. |
| Action | Increase the file size attribute of the multipart configuration for the given servlet. |
| Explanation | The multipart/form-data request is larger than the maximum configured size. |
| Action | Increase the request size attribute of the multipart configuration for the given servlet. |
| Explanation | There was an exception uploading the file. |
| Action | Investigate nested error and perform appropriate action. |
| Explanation | The request must be of type multipart/form-data to be able to handle this method. |
| Action | Modify the servlets making previous requests such that the current request is of type multipart/form-data. |
| Explanation | An error or timeout resulting from an async dispatch will invoke any registered async listener and then the error page mechanism, if not listener, dispatches or completes. |
| Action | Fix the cause of the error by looking at the exception and modifying application code or be sure to provide an AsyncListener or error page to handle the error case. |
| Explanation | This exception should never occur as the thread pools will queue up the work. |
| Action | If this exception occurs, contact support. |
| Explanation | I/O errors can occur when invoking an AsyncListener if it is writing to the response concurrently with another thread or another process has closed the response. |
| Action | It is recommended that AsyncListeners call only complete or dispatch, but not write to the response. Otherwise, the user is responsible for doing their own synchronization to prevent an IOException. |
| Explanation | When two requests are made to the same resource the first time, a race condition can occur when trying to add the mapping to the web application. |
| Action | This is normally a benign condition that can be ignored. Only report this exception if there are issues serving any requests to the resources in question. |
| Explanation | Because creation of the search path involves file system access, IOExceptions might occur. |
| Action | Verify that the path is correct and there are no hardware issues. |
| Explanation | An unexpected ServletException occurred while adding a servlet dynamically. This exception can occur, for example, if the MBean names of two servlets collide. |
| Action | Review the logs and contact support. |
| Explanation | The class was not found in the class loader when processing the ServletContainerInitializer HandlesTypes annotation. |
| Action | Make sure the class exists within the web module class loader. |
| Explanation | The class was not found in the class loader when processing the ServletContainerInitializer HandlesTypes annotation. |
| Action | Make sure the class exists within the web module class loader. |
| Explanation | A problem occurred while initializing the application"s ServletContainerInitializers. |
| Action | Verify that the ServletContainerInitializer is configured correctly. |
| Explanation | An IOException can occur for a variety of reasons related to I/O. |
| Action | Check to see if the class has been removed. |
| Explanation | An IllegalAccessException occurred while calling newInstance on the servlet. |
| Action | Verify that there is a public, no argument constructor on the servlet. |
| Explanation | An InstantiationException occurs when trying to create a new instance of an interface or abstract class. |
| Action | Change the class being instantiated to a concrete class or remove the definition as a servlet. |
| Explanation | An exception occurred while processing reference data. Application will attempt to start anyway. |
| Action | Investigate the cause of the exception and determine if application still functions properly, despite these failures. |
| Explanation | The method startAsync cannot be called after a complete according to the Servlet specification. |
| Action | Verify that there are no code logic or timing issues causing this illegal behavior. |
| Explanation | The startAsync method must be called from within the context of a container dispatch, whether it is the original request or a subsequent async dispatch. |
| Action | Verify that there are no code logic or timing issues causing this illegal behavior. |
| Explanation | The startAsync method cannot be called multiple times from the same dispatch. A call to AsyncContext.dispatch would allow you to call startAsync again. |
| Action | Verify that there are no code logic or timing issues causing this illegal behavior. |
| Explanation | The Servlet specification states you can call dispatch only once per call to startAsync. |
| Action | Remove the additional call to dispatch. |
| Explanation | An internal error caused the reference context that enables injection to not be initialized properly. |
| Action | Check for errors earlier in the logs that might have caused initialization to fail. |
| Explanation | IOExceptions can occur when looking at JAR files if the file is changed or closed during traversal. |
| Action | Verify the JAR file is valid and is not being updated during traversal. |
| Explanation | The context has already been initialized. No updates are allowed to the session configuration. |
| Action | You can only modify the session configuration before the application is initialized. |
| Explanation | Programmatic session configuration has been disabled on this server. |
| Action | Enable programmatic session configuration. |
| Explanation | An error occurred while invoking a call to AsyncContext dispatch. |
| Action | See the cause of the exception. |
| Explanation | The file serving attribute com.ibm.ws.webcontainer.optimizefileservingsize could not be parsed property. |
| Action | Change the value of the attribute to a valid integer value. |
| Explanation | The same pattern was specified twice for the URL patterns to deny for file serving. |
| Action | Check the file serving attributes in your ibm-web-ext.xmi or ibm-web-ext.xml file. |
| Explanation | An internal server error occurred that destroyed the servlet. |
| Action | See the cause of the exception. |
| Explanation | Classpath errors occurred when serving the servlet. |
| Action | Place servlet class on classpath of the application server. |
| Explanation | An internal server error occurred while unloading the servlet. |
| Action | See the cause of the exception. |
| Explanation | Servlet could not find a required class needed to service the request. This is an application error. |
| Action | Verify the class exists within the application. |
| Explanation | A NumberFormatException occurred while trying to set the single thread model pool size. |
| Action | Verify the value for the single thread model pool size is a valid integer. |
| Explanation | A NumberFormatException occurred while trying to set the single thread model servlet maximum idle time. |
| Action | Verify that the value for the single thread model servlet maximum idle time is a valid integer. |
| Explanation | An unexpected exception occurred while flushing out the rest of the response data. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected exception occurred while closing the output stream. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected exception occurred while initializing the output stream. |
| Action | Gather server logs and contact IBM service. |
| Explanation | Java 2 Security policy prevented deleting the temporary directory |
| Action | Check Java 2 Security policy to verify whether this access should be allowed. |
| Explanation | An unexpected exception occurred while trying to retrieve the session context. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected exception occurred during resource injection. |
| Action | Gather server logs and contact IBM service. |
| Explanation | Problem invoking postConstruct or preDestroy. |
| Action | See cause. |
| Explanation | An unexpected exception occurred while initializing the security collaborator. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected exception occurred while initializing the login processor. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected exception occurred while initializing the logout processor. |
| Action | Gather server logs and contact IBM service. |
| Explanation | Unknown error related to the web container configuration. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected exception occurred while adding the WebContainerService. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected exception occurred while handling an extension point. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected exception occurred while removing the web module. |
| Action | Gather server logs and contact IBM service. |
| Explanation | The Session registry is null, possibly because the SessionManager did not start correctly. Web applications will fail. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected error occurred while starting the web container channel chains. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected configuration exception occurred. |
| Action | Gather server logs and contact IBM service. |
| Explanation | Unexpected isUserInRole exception, returning of isUserInRole false. |
| Action | Unexpected isUserInRole exception, returning of isUserInRole false. |
| Explanation | An unexpected internal server error occurred while adding a web application collaborator. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected internal server error occurred while adding the static file processor. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected internal server error occurred while registering web module MBean. |
| Action | Gather server logs and contact IBM service. |
| Explanation | An unexpected error occurred while populating the namespace. |
| Action | Check the server logs and exception to determine what might have caused the namespace binding problem. |
| Explanation | An IOException was thrown from WebContainer"s handleRequest method. |
| Action | Gather server logs and contact IBM support. |
| Explanation | An exception occurred while retrieving the peer certificate. |
| Action | See cause. |
| Explanation | The createStatsInstance() method created an exception when it was called to create the statistics instance. No statistic were collected. |
| Action | Examine the server logs to determine the root cause of the problem. |
| Explanation | Error removing PMI statistics instance. |
| Action | Gather server logs and contact IBM service. |
| Explanation | Error creating PMI statistics group. |
| Action | Gather server logs and contact IBM service. |
| Explanation | Error occurred while preparing the servlet wrapper for initialization. |
| Action | See cause. |
| Explanation | An UnavailableException was thrown from the servlet. |
| Action | See cause. |
| Explanation | An exception occurred while invoking the async error mechanism. |
| Action | See cause. |
| Explanation | The servlet class name is null so the request cannot be handled. |
| Action | Verify that a valid servlet class was provided for the servlet. |
| Explanation | Once a response is committed, you cannot set more response headers. |
| Action | Verify whether this call is necessary. If the header must be sent, set it before committing the response. |
| Explanation | When scheduling a work item with an asynchronous beans work manager, workRejected might be called if an error occurs while starting the work item. |
| Action | See cause. |
| Explanation | When scheduling a work item with an asynchronous beans work manager, an exception might be thrown if the work queue is full and the configured work queue full action is to fail. |
| Action | Evaluate whether the work queue full action should be to block until the queue is not full or handle this exception in your application code. |
| Explanation | A filter mapping is incomplete without a URL pattern or servlet name to map to. |
| Action | Add a URL pattern or servlet name to the filter mapping. |
| Explanation | A servlet mapping is incomplete without a URL pattern to map to. |
| Action | Add a URL pattern to the servlet mapping. |
| Explanation | The restartWebApplication method no longer does anything. Use the ApplicationManager MBean to start and restart an application. |
| Action | The restartWebApplication method no longer does anything. Use the ApplicationManager MBean to start and restart an application. |
| Explanation | There was an error adding a virtual host alias because one already exists with the same pattern. |
| Action | Edit your virtual host alias and remove any duplicates. |
| Explanation | An unexpected internal error has caused a mismatch between the expected state of the output buffer and the actual state. |
| Action | Gather server logs and contact IBM service. |
| Explanation | Illegal value for responsebuffersize custom property. |
| Action | Check the value of the responsebuffersize custom property. |
| Explanation | An internal server error occurred while creating the channel object. |
| Action | Gather server logs and contact IBM support. |
| Explanation | An unexpected servlet engine exception occurred. This is a system error. |
| Action | Check the System.out and System.err logs for more information on the exception generated. |
| Explanation | The administrative console should not allow you to pick an invalid timer manager JNDI name. |
| Action | Verify that the timer manager selected in the web container panel is valid. |
| Explanation | An exception occurred while invoking the async listeners. |
| Action | See cause. |
| Explanation | This is an unexpected internal error. |
| Action | Gather web container trace and contact IBM support. |
| Explanation | There must be at least one async timer thread. |
| Action | Check your server configuration to see what the value is set to. |
| Explanation | An exception was thrown from a filter. |
| Action | See cause. |
| Explanation | The ServletContainerInitializer specified by the Extension Point could not be initialized. |
| Action | Check the class specified in the Extension Point. |
| Explanation | The administrator has disabled changing the cookie configuration for the cookie matching the domain, name, and path |
| Action | Either modify the application to use a different cookie name, domain, or path or modify the restricted programmatic session cookie values |
| Explanation | There was a problem retrieving the restricted cookie patterns from the configuration. |
| Action | Verify that the cell.xml file exists and is readable. |
| Explanation | Error processing has already been invoked by another thread. |
| Action | Make sure the application can handle an exception. If it is necessary that this method return, even if the call doesn"t succeed, contact IBM support. |
| Explanation | A servlet with the same name already exists for this application. |
| Action | No action necessary. Check for conflicts in the deployment descriptor, annotations, and source code that could dynamically add this servlet configuration. |
| Explanation | The AsyncListener that is referenced in the error message threw an Exception. The Exception is an application error. |
| Action | Verify the AsyncListener source code and the server logs for the root cause of the application error. |
| Explanation | An exception was thrown from a ServletContainerInitializer while invoking the onStartup method. |
| Action | Review the Exception to determine the cause of the error. |
| Explanation | Failed to create the HttpUpgradeHandler. |
| Action | Check the FFDC logs for more details on the error. |
| Explanation | You cannot start certain operations from a programmatically added listener because there is no configuration option to restrict their launch when they are defined in a Tag Library Descriptor (TLD). |
| Action | Add the listener using an annotation or in the web.xml file to enable starting this method. |
| Explanation | Failed to upgrade the request because HttpUpgradeHandler object passed is null. |
| Action | Make sure that the correct HttpUpgradeHandler object is provided. |
| Explanation | The variable argument passed to the setReadListener API must be a valid readListener object. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The variable argument passed to the WriteListener API must be a valid writeListener object. |
| Action | Modify the application code according to the error explanation. |
| Explanation | You can set the ReadListener on the request only if async is started or the init method of an UpgradeHandler is called. |
| Action | Modify the application code according to the error explanation. |
| Explanation | You can set the WriteListener only on the request if async is started or the init method of an UpgradeHandler is called. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The ReadListener cannot be set more than once. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The WriteListener cannot be set more than once. |
| Action | Modify the application code according to the error explanation. |
| Explanation | If isReady returns false it is illegal to call a read method. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The variable argument byte[] passed to the read or write API must not be null. |
| Action | Modify the application code according to the error explanation. |
| Explanation | Either variable arguments offset was negative, the length was negative, or the length was greater than byte[].length - offset. |
| Action | Modify the application code and verify that the offset value that is provided to read or write API is not negative. Ensure that the length value provided to read API is not negative. Also ensure that the length value provided is greater than byte[] length minus offset value that is provided. |
| Explanation | While setting the ReadListener, the listener attempts to read, which failed. |
| Action | Review the JVM logs for the exception. |
| Explanation | To change the session ID for a request, first ensure that the request being used has a session associated with it. |
| Action | Modify the application code according to the error explanation. |
| Explanation | From Servlet 3.1 AsyncContext.getRequest() and AsyncContext.getResponse() must throw an IllegalStateException if complete() or any of the dispatch() methods have been called in the asynchronous cycle. |
| Action | Modify the application code according to the error explanation. |
| Explanation | There is an application error. A servlet mapping URL pattern should not map to multiple servlets. |
| Action | Change the URL pattern for the servlet mapping. |
| Explanation | The write API on the OutputStream object and read API on the InputStream object state that an IOException might be thrown if the stream has been closed. |
| Action | Modify the application code according to the error explanation. |
| Explanation | The servlet name is used in filter mapping, but its definition has not been defined. |
| Action | Define the servlet which is used in the servlet name filter mapping. |
| Explanation | A cookie name cannot be configured for multiple SameSite attribute values. The attribute is not added for the cookie. |
| Action | Check the deployment descriptor configuration to make sure the cookie name is configured for only one of the following SameSite attribute values: "SameSiteCookies_Lax", "SameSiteCookies_None", or "SameSiteCookies_Strict". |
| Explanation | A cookie name cannot be configured for multiple SameSite attribute values. This cookie name has already been identified as a duplicate. |
| Action | Check the deployment descriptor configuration to make sure the cookie name is configured for only one of the following SameSite attribute values: "SameSiteCookies_Lax", "SameSiteCookies_None", or "SameSiteCookies_Strict". |
| Explanation | The number of files that are uploaded by the multipart/form-data request exceeded the set limit. |
| Action | Increase the maximum number of files that can be uploaded for a request by setting the com.ibm.ws.webcontainer.maxFileCount webContainer custom property. The default value is 5000. For unlimited file upload, set the value to -1. |