Explanation | Attempting to output a buffer of size less than 0. This is an application error. |
Action | Only write buffers of size of 0 or greater. |
Explanation | Attempting to output a buffer of size less than 0. This is an application error. |
Action | Only write buffers of size of 0 or greater. |
Explanation | Uncaught exception created in servlet service method. This is an application error. |
Action | Varies by root cause. |
Explanation | Uncaught exception created in servlet service method. This is an application error. |
Action | Varies by root cause. |
Explanation | Could not initialize the web application specified in the message. Check the error log for more details. |
Action | Look in the error log to determine the root cause of this problem. |
Explanation | Could not initialize the web application specified in the message. Check the error log for more details. |
Action | Look in the error log to determine the root cause of this problem. |
Explanation | Format found for a request header is not valid. |
Action | Check client header creation. |
Explanation | Format found for a request header is not valid. |
Action | Check client header creation. |
Explanation | The specified servlet has been unloaded after the destroy method has been called. |
Action | none. |
Explanation | The specified servlet has been unloaded after the destroy method has been called. |
Action | none. |
Explanation | The specified path is not a directory. |
Action | Make sure the directory exists or that you are requesting the right directory. |
Explanation | The specified path is not a directory. |
Action | Make sure the directory exists or that you are requesting the right directory. |
Explanation | WebAppSecurityCollaborator. This is a system error. |
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 | WebAppSecurityCollaborator. This is a system error. |
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. This is an application error. |
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. This is an application error. |
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 | Date 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 | Date 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 | Servlet is being destroyed after wait has timed out. |
Action | none. |
Explanation | Servlet is being destroyed after wait has timed out. |
Action | none. |
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 | Could not destroy specified servlet. This is an application error. |
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 destroy specified servlet. This is an application error. |
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 servlet host. |
Action | Make sure the host name has been specified correctly and that the servlet host has been specified in virtualhosts.xml. |
Explanation | Could not bind the specified host name to the specified servlet 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 | The specified directory is not valid. |
Action | Check directory specification for errors. |
Explanation | Servlet is still handling the request. Waiting for request to complete before calling destroy. |
Action | none. |
Explanation | Servlet is still handling the request. Waiting for request to complete before calling destroy. |
Action | none. |
Explanation | An exception was thrown by one of the service methods of the servlet. This is an application error. |
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 | Uncaught exception created in one of the service methods of the servlet. This is an application error. |
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 | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | Internal server error. This could be caused by network tuning issues, the content-length being specified incorrectly, or the length or size of an attachment. This is an application error. |
Action | Gather logs and contact IBM service. |
Explanation | Internal server error. This could be caused by network tuning issues, the content-length being specified incorrectly, or the length or size of an attachment. This is an application error. |
Action | Gather logs and contact IBM service. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Specified servlet is temporarily unavailable. |
Action | Wait and retry operation. Servlet might have been removed from service by server administrator. |
Explanation | Specified servlet is temporarily unavailable. |
Action | Wait and retry operation. Servlet might have been removed from service by server administrator. |
Explanation | A session cannot be accessed. The session manager featureset has not been started. |
Action | Make sure that the server configuration depends upon the session featureset. |
Explanation | A session cannot be accessed. The session manager feature set has not been started. |
Action | Make sure that the server configuration depends upon the session feature set. |
Explanation | The specified servlet is being unloaded from service. |
Action | none. |
Explanation | The specified servlet is being unloaded from service. |
Action | none. |
Explanation | Could not instantiate a class for use by the object pool. This is a system error. |
Action | Be sure the class exists and is visible on the application class path. |
Explanation | Could not instantiate a class for use by the object pool. This is a system error. |
Action | Be sure the class exists and is visible on the application class path. |
Explanation | Could not initialize the specified servlet. This is an application error. |
Action | Make sure the servlet class file is available on the application class path. |
Explanation | Could not initialize the specified servlet. This is an application error. |
Action | Make sure the servlet class file is available on the application class path. |
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 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 | 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 | 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 | 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 | 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 | 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 | IO error encountered. |
Action | Varies depending on reported root cause. |
Explanation | IO error encountered. |
Action | Varies depending on reported root cause. |
Explanation | Attempting to output a buffer of size less than 0. This is an application error. |
Action | Only write buffers of size of 0 or greater. |
Explanation | Attempting to output a buffer of size less than 0. This is an application error. |
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 | 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 encountered parsing servlet parameters. |
Action | Verify the client is sending the full request. |
Explanation | Problem encountered parsing servlet parameters. |
Action | Verify the client is sending the full request. |
Explanation | Security problem encountered during request processing. This is a system error. |
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. This is a system error. |
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. This is a system error. |
Action | Varies with root cause. |
Explanation | Security problem encountered during request processing. This is a system error. |
Action | Varies with root cause. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Could not load the specified file. System action is required. |
Action | Be sure the specified file exists and is in the correct format according to java.utils.Properties. |
Explanation | Could not load the specified file. System action is required. |
Action | Be sure the specified file exists and is in the correct format according to java.utils.Properties. |
Explanation | Could not load the specified file. System action is required. |
Action | Be sure the specified file existsand is in the correct format according to java.utils.Properties. |
Explanation | Could not load the specified file. System action is required. |
Action | Be sure the specified file existsand is in the correct format according to java.utils.Properties. |
Explanation | An attempt was made to set the response buffer size after the response was already committed. This is an application error. |
Action | Remove the setBufferSize() call or move it to a position before the response commit. |
Explanation | An attempt was made to set the response buffer size after the response was already committed. This is an application error. |
Action | Remove the setBufferSize() call or move it to a position before the response commit. |
Explanation | Problem encountered rolling back the specified user transaction. This is an application error. |
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. This is an application error. |
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 | none. |
Explanation | Application server identifier. |
Action | none. |
Explanation | The servlet specification level supported by the application server. |
Action | none. |
Explanation | The servlet specification level supported by the application server. |
Action | none. |
Explanation | The JSP specification level supported by the application server. |
Action | none. |
Explanation | The JSP specification level supported by the application server. |
Action | none. |
Explanation | Two web applications on the same virtual host share the same context root. This is an application error. |
Action | Either change the context root of one of the web applications or move one to a different virtual host. |
Explanation | Two web applications on the same virtual host share the same context root. This is an application error. |
Action | Either change the context root of one of the web applications or move one to a different virtual host. |
Explanation | WebModule is starting and being made available for service. |
Action | none. |
Explanation | Web module is starting and being made available for service. |
Action | none. |
Explanation | Informational message {2} logged via ServletContext.log from application {0} with context root {1}. |
Action | none. |
Explanation | Informational message logged via ServletContext.log from an application. |
Action | none. |
Explanation | Informational message {2} logged via ServletContext.log from application {0} with context root {1} and stack trace {3}. |
Action | none. |
Explanation | Informational message and stack trace logged via ServletContext.log from an application. |
Action | none. |
Explanation | Exception that occurred when processing the request. |
Action | Review the message to determine the root cause of the problem. |
Explanation | Exception that occurred when processing the request. |
Action | Review the message to determine the root cause of the problem. |
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 | 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 the classes you may be accessing |
Explanation | A required class was not found. This is an application error. |
Action | Make sure your class path reflects all the classes you may 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 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 is an error that occurs when the request was being completed. This 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 | This is an error that occurs when the request was being completed. This 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 mentioned file was not found. This is an application error. |
Action | Ensure that the mentioned file is in place. |
Explanation | The mentioned file was not found. This is an application error. |
Action | Ensure that the mentioned file is in place. |
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 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 with the mentioned name has no value. This is a required parameter. This is an application error. |
Action | Supply a value to the mentioned parameter. |
Explanation | The parameter with the mentioned name has no value. This is a required parameter. 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 OuputStream were obtained. Modify the failing servlet/JSP to only obtain one or the other. |
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 OuputStream were obtained. Modify the failing servlet/JSP to only obtain one or the other. |
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 | 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 | This is an application error. |
Action | Modify the failing class to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet |
Explanation | This is an application error. |
Action | Modify the failing class to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet |
Explanation | The servlet class was found to be corrupted. This is an application error. |
Action | Re-compile the class and try again. |
Explanation | The servlet class was found to be corrupted. 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/jars representing the class path |
Explanation | A required class was not found. This is an application error. |
Action | Make sure all required classes are placed in the folders/jars representing 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 | 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 Virtual Host 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 | Unable to locate Virtual Host 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 | 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 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. eg., from int to Data, when such a conversion is not possible. This is an application error. |
Action | Modify the failing servlet/JSP. |
Explanation | The code tried to do an illegal conversion of a header value. eg., 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 OuputStream were obtained. Modify the failing servlet/JSP to only obtain one or the other. |
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 OuputStream were obtained. Modify the failing servlet/JSP to only obtain one or the other. |
Explanation | This is an application error. |
Action | Recompile the servlet using only the classes in the application's runtime class path. |
Explanation | This is an application error. |
Action | Recompile the servlet using only the classes in the application's 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: 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 | 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: 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 | 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: 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 | 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: 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 | 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: 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 | 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: 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 | 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: 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 | 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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The servlet chain that has been defined can only handle HTTP requests. This is an application error. |
Action | none. |
Explanation | The servlet chain that has been defined can only handle HTTP requests. This is an application error. |
Action | none. |
Explanation | The incoming request may be corrupted. This is an application error. |
Action | none. |
Explanation | The incoming request may be corrupted. 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 webcontainer tried to load an internal implementation class. This is a system error. |
Action | Check to make sure the original WAS class path has not been modified. |
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 | 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 | 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 | Error that caused the problem. |
Action | none. |
Explanation | Cannot serve the contents of a JSP file |
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 | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | Package name of resource does not match the compiled class file's package. This is an application error. |
Action | Check that the class resides in the proper package directory. |
Explanation | Package name of resource does not match the compiled class file's package. 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 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 filesystem using a binary transfer mode. |
Explanation | This is an application error. |
Action | Check that the class was transferred to the filesystem 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 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 | 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 | 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 | none |
Action | none |
Explanation | none |
Action | none |
Explanation | See reported error. |
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 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 | Supply a leading slash before the path and try again. |
Explanation | This is an application error. |
Action | Supply a leading slash before the path and try again. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
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 | The init() method of the target resource ran successfully and the target has been places into service. |
Action | none. |
Explanation | none. |
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 servlets that have been inactive for longer than the reaper inactive limit. |
Action | none. |
Explanation | The reaper thread removes the mappings for jsps and other extensions that have been inactive longer the the reaper inactive limit. |
Action | none. |
Explanation | The reaper thread removes the mappings for jsps and other extensions that have been inactive longer the the reaper inactive limit. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | Exception occurred in the reaper thread processing. This is a system error. |
Action | Reaper processing is just a form of garbage collection. |
Explanation | Exception occurred in the reaper thread processing. This is a system error. |
Action | Reaper processing is just a form of garbage collection. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | SyncToOSThread synchronizes the Java EE role identity to the OS thread, meaning that 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 utilize 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 information center for a description as to how to enable SyncToOSThread for a server. |
Explanation | SyncToOSThread synchronizes the Java EE role identity to the OS thread, meaning that 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 utilize 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 information center for a description as to how to enable SyncToOSThread for a server. |
Explanation | The specified web module has been associated to the virtualhost mentioned, and can be accessed through any of the host/port combinations for that virtualhost. |
Action | none. |
Explanation | The specified web module has been associated to the virtualhost mentioned, and can be accessed through any of the host/port combinations for that virtualhost. |
Action | none. |
Explanation | There exists a ThreadPool configuration under the webcontainer. Any changes made to this configuration item will not result in changes in the system. |
Action | none. |
Explanation | There exists a thread pool configuration under the web container. Any 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 information center to review information on Channel Chains, and how to migrate the existing transports to be channel chain based. The thread pool configuration under the webcontainer 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 | Transports have been changed to use Channel Chains. Refer to the information center 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 destroy() method of the target resource ran successfully and the target has been removed from service. |
Action | none. |
Explanation | Request encoding 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 | Request encoding 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 | 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 | WebContainer is not initialized until an application has been installed. This is a system error. |
Action | Install an application to initialize the webcontainer. |
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 information center for more details. |
Explanation | A thread is no longer tied to a single connection. System action is required. |
Action | Refer to the information center for more details. |
Explanation | System action is required. |
Action | Configure this property under the Logging Service (see information center for more details on HTTP Access Logger). |
Explanation | System action is required. |
Action | Configure this property under the Logging Service (see information center for more details on HTTP Access Logger). |
Explanation | The {0} property can no longer be configured at the transport level and must be configured at the webcontainer level. System action is required. |
Action | Configure this property at the webcontainer level. |
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 | 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 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 of the expected type. This is a system error. |
Action | Check the annotation helper implementation class and fix it. |
Explanation | The specified annotation helper is not of 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 | 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 | 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 WebApp. System action is required. |
Action | Check if the Session Manager is configured correctly. |
Explanation | Could not obtain a valid Session Context for the web application. System action is required. |
Action | Check if the Session Manager is configured correctly. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | A servlet mapping specified in the webconfig.xml is not valid. System action is required. |
Action | Check the servlet mappings in webconfig.xml and make appropriate changes |
Explanation | A servlet mapping specified in the webconfig.xml is not valid. System action is required. |
Action | Check the servlet mappings in webconfig.xml and make appropriate changes |
Explanation | This is an application error. |
Action | Review the logs. |
Explanation | This is an application error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | none. |
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 | Review the logs. |
Explanation | This is an application error. |
Action | Check for mapping clash in webconfig.xml |
Explanation | This is an application error. |
Action | Check for mapping clash in webconfig.xml |
Explanation | This is an application error. |
Action | Verify the mapping is valid. |
Explanation | This is an application error. |
Action | Verify the mapping is valid. |
Explanation | This is an application error. |
Action | Review the logs. |
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 | Remove the duplicate mapping. |
Explanation | This is an application error. |
Action | Set fileServingEnabled=false in the ibm-web-ext.xmi file which is under WEB-INF folder. |
Explanation | This is an application error. |
Action | Set fileServingEnabled=false in the ibm-web-ext.xmi file which is under WEB-INF folder. |
Explanation | This is an application 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. |
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 a system error. |
Action | Review the logs. |
Explanation | This is an application 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. |
Action | Review the logs. |
Explanation | This is a system error 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 | 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 | 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 | 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 | none. |
Action | none. |
Explanation | Informational message logged for a servlet by use of the ServletContext. |
Action | none. |
Explanation | none. |
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 may be available in the server logs. |
Explanation | none. |
Action | none. |
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 may 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 | HttpServletResponse.sendError was called with a status code but no explanation. |
Action | Review the logs to determine the status code of the error. |
Explanation | none. |
Action | none. |
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 for may 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 | 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 | 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 | 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 | Check your web.xml has a servlet definition for this servlet mapping. |
Explanation | There is no servlet definition for the servlet mapping. |
Action | Check your web.xml has a servlet definition for this servlet mapping. |
Explanation | WebContainer 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 | 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 webcontainer, but it has been disabled. This is a system error. |
Action | It is recommended to enable the object pool service. |
Explanation | The object pool service improves the performance of the web container, but it has been disabled. This is a system error. |
Action | It is recommended to 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 | ARD is not enabled correctly. System action is required. |
Action | Make sure ARD is enabled in the WebContainer 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 so 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 | There was no servlet mapping for the filter so 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 | 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 custom property com.ibm.ws.webcontainer.donotservebyclassname. This is an application error. |
Action | If this is not the desired behavior, update the property com.ibm.ws.webcontainer.donotservebyclassname. |
Explanation | The requested servlet is on the block list provided by the custom property com.ibm.ws.webcontainer.donotservebyclassname. This is an application error. |
Action | If this is not the desired behavior, update the property com.ibm.ws.webcontainer.donotservebyclassname. |
Explanation | System action is required. |
Action | Verify the custom property is correct |
Explanation | System action is required. |
Action | Verify 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 | 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 | 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 | 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 Information Center to add a new virtual host alias. |
Explanation | The request path maps to a context root on a non-matching virtual host. |
Action | Follow the instructions in the Information Center 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 | 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 | A class in the web module could not be instantiated so it cannot be scanned for annotations. |
Action | Verify the class exists and has all of its dependencies in the classpath. |
Explanation | Servlets and filters can only be dynamically added during the contextInitalized phase of application startup. |
Action | Move the code calling the current method into a ServletContextInitalizer's contextInitalized method. |
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 startup. |
Action | Examine the server logs to determine the root cause of the problem. |
Explanation | The listener failed to initialize because an error occured 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 hashcodes 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 | Application code threw an unexpected exception. |
Action | Review the stack trace to identify the root cause of the problem. |
Explanation | An attempt was made to get or adjust an InputStream for this response, but a BufferedReader has already been obtained. |
Action | Modify the failing servlet or JSP to use either a BufferedReader instance or an InputStream instance but not both. |
Explanation | An attempt was made to get a BufferedReader for this response, but an InputStream has already been obtained. |
Action | Modify the failing servlet or JSP to obtain either a BufferedReader instance or an InputStream instance but not both. |
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. |
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. |
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 | Servlets can only be dynamically added before the ServletContext is initialized. |
Action | Move the code calling the current method into a ServletContainerInitalizer's onStartup or a ServletContextListener's contextInitialized method. |
Explanation | Filters can only be dynamically added before the ServletContext is initialized. |
Action | Move the code calling the current method into a ServletContainerInitalizer's onStartup or a ServletContextListener's contextInitialized method. |
Explanation | The variable argument url-pattern parameter passed to ServletRegistration.addMapping must be non-null and non-empty. |
Action | Modify application code according to error explanation. |
Explanation | The variable argument url-pattern parameter passed to ServletRegistration.addMapping must be non-null and non-empty. |
Action | Modify application code according to error explanation. |
Explanation | The variable argument url-pattern parameter passed to FilterRegistration.addMappingForUrlPatterns must be non-null and non-empty. |
Action | Modify application code according to error explanation. |
Explanation | The variable argument url-pattern parameter passed to FilterRegistration.addMappingForUrlPatterns must be non-null and non-empty. |
Action | Modify application code according to error explanation. |
Explanation | The variable argument servlet name parameter passed to FilterRegistration.addMappingForServletNames must be non-null and non-empty. |
Action | Modify application code according to error explanation. |
Explanation | The variable argument servlet name parameter passed to FilterRegistration.addMappingForServletNames must be non-null and non-empty. |
Action | Modify application code according to 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 since there is no configuration option to restrict their execution when they are defined in a Tag Library Descriptor (TLD). |
Action | Add the listener via an annotation or via the web.xml to enable the execution of this method. |
Explanation | A ServletContextListener can not be added from another ServletContextListener |
Action | Either add the ServletContextListener to the web.xml or web-fragment.xml, 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 only be applied to classes which extend the correct type. |
Action | Modify the class to extend the correct super class |
Explanation | The class can not specify both urlPatterns and value in the annotation |
Action | Modify the class to only include one of the urlPatterns or value attribute |
Explanation | The class must specify patterns in the annotation via 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. |
Explanation | The file being uploaded via 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 gracefully handle the error case. |
Explanation | This exception should never occur as the thread pools will queue up the work. |
Action | If this exception occurs, please contact support. |
Explanation | I/O errors can occur when invoking an AsyncListener if it is writing to the response concurrently with another thread or something else has closed the response. |
Action | It is recommended that AsyncListeners should only call complete or dispatch, but not write to the response. Otherwise, the customer 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 in trying to add the mapping to the web application. |
Action | This is normally a benign condition that can be ignored. Only report this if there are issues serving any requests to the resources in question. |
Explanation | Because creation of the search path involves file system access, IOExceptions may occur. |
Action | Verify that the path is correct and there are no hardware issues. |
Explanation | An unexpected ServletException occurred adding a servlet dynamically. This 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's 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's 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 any number of reasons related to I/O. |
Action | Check if the class has been removed. |
Explanation | An IllegalAccessException occurred calling newInstance on the servlet. |
Action | Verify 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 processing reference data. Application will attempt to start anyway. |
Action | Investigate the root cause of the exception and determine if application still functions properly despite these failures. |
Explanation | The method startAsync cannot be called after a complete per the Servlet specification. |
Action | Verify there are no code logic or timing issues causing this illegal behavior. |
Explanation | The method startAsync must be called from within the context of a container dispatch be it the original request or a subsequent async dispatch. |
Action | Verify there are no code logic or timing issues causing this illegal behavior. |
Explanation | The method startAsync cannot be called multiple times from the same dispatch. A call to AsyncContext.dispatch would allow you to call startAsync again. |
Action | Verify there are no code logic or timing issues causing this illegal behavior. |
Explanation | The Servlet specification states you can only call dispatch 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 may 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 root 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 | Please check the file serving attributes in your ibm-web-ext.xmi or ibm-web-ext.xml file. |
Explanation | An internal server error occurred destroying the servlet. |
Action | See the root 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 unloading the servlet. |
Action | See the root 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 when 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 when trying to set the single thread model servlet maximum idle time. |
Action | Verify the value for the single thread model servlet maximum idle time is a valid integer. |
Explanation | An unexpected exception occurred flushng out the rest of the response data. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected exception occurred closing the output stream. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected exception occurred 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 when 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 root cause. |
Explanation | An unexpected exception occurred initializing the security collaborator. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected exception occurred initializing the login processor. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected exception occurred 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 adding the WebContainerService. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected exception occurred handling an extension point. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected exception occurred 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 up correctly. Web applications WILL fail. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected error occurred starting the web container channel chains. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected configuration exceptoin 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 exceptoin occurred. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected configuration exceptoin occurred. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected configuration exceptoin occurred. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected configuration exceptoin occurred. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected configuration exceptoin occurred. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected configuration exceptoin occurred. |
Action | Gather server logs and contact IBM service. |
Explanation | An unexpected configuration exceptoin 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 internal server error occurred while populating the namespace. |
Action | Gather server logs and contact IBM service. |
Explanation | An IOException was thrown from WebContainer's handleRequest method. |
Action | Gather server logs and contact IBM support. |
Explanation | An exception occurred retrieving the peer certificate. |
Action | See root cause. |
Explanation | Error creating PMI statistics instance. |
Action | Gather server logs and contact IBM service. |
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 root cause. |
Explanation | An UnavailableException was thrown from the servlet. |
Action | See root cause. |
Explanation | An exception occurred invoking the async error mechanism. |
Action | See root cause. |
Explanation | The servlet class name is null so the request cannot be handled. |
Action | Verify 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 really needs to be sent, it should be set before committing the response. |
Explanation | When scheduling a work item with an asynchronous beans work manager, workRejected may be called if an error happens starting the work item. |
Action | See root cause. |
Explanation | When scheduling a work item with an asynchronous beans work manager, an exception may 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 method restartWebApplication no longer does anything. Use the ApplicationManager MBean to start and restart an application. |
Action | The method restartWebApplication 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 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 the timer manager selected in the web container panel is valid. |
Explanation | An exception occurred invoking the async listeners. |
Action | See root 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 root 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 exists and is readable. |
Explanation | Error processing has already been invoked by another thread. |
Action | Make sure the application can handle an exception here. 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 servlet container is loaded with a version that corresponds to the Java EE specification of that servlet feature. The container was loaded with no version defined. |
Action | Check the server.xml file for existence of either a servlet-3.0 or servlet-3.1 feature. One of these features should be defined, but not both. |
Explanation | The web application is being stopped and the request cannot complete. This action might be caused by the server being shut down while the request is being handled. |
Action | Resubmit the request after the application is available. |
Explanation | All filters and the target servlet for a request need to support async processing to use the async mode for servlet requests. |
Action | Either update the specified filter or servlet to support async processing, or update the servlet to not use the async programming APIs. |
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 | Failed to create the HttpUpgradeHandler. |
Action | Check the FFDC logs for more details on the error. |
Explanation | The servlet-3.1 feature is not in use. It is possible that an earlier version of servlet is already in use. |
Action | Add the servlet-3.1 feature to your server.xml file. |
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 | While generating the plugin configuration file, multiple applications were determined to be using the same context root. |
Action | Determine whether this is configured as intended and fix if it is not. |
Explanation | Using localhost as the host name will only work if the target application server is running on the same machine. |
Action | Modify the host name if the application server is not in fact running locally. |
Explanation | A virtual host will not be available if no applications are defined. |
Action | Update the server configuration to define at least one application prior to generating the plugin configuration file. |
Explanation | Generation of a new plugin configuration file occurs on each server restart, and when applications in the server are added, removed or changed. |
Action | This file can be reviewed for correctness, then moved to the location of your web server plugin to direct HTTP traffic to the applications in this server. The pluginUtility can merge files so that requests can be directed across multiple application servers. If the file was generated because of application changes you might need to update the existing configuration file on the web server host. |
Explanation | A user request resulted in creation of a new plugin configuration file. |
Action | This file can be reviewed for correctness, then moved to the location of your web server plugin to direct HTTP traffic to the applications in this server. The pluginUtility can merge files so that requests can be directed across multiple application servers. |
Explanation | The administered-object of the same name cannot be configured in different web-fragment.xml files if it is missing in the web.xml. |
Action | Configure the administered-object with the same name in the web.xml to override the ones from web-fragment.xml files. |
Explanation | The jms-connection-factory of the same name cannot be configured in different web-fragment.xml files if it is missing in the web.xml. |
Action | Configure the jms-connection-factory with the same name in the web.xml to override the ones from web-fragment.xml files. |
Explanation | The jms-destination of the same name cannot be configured in different web-fragment.xml files if it is missing in the web.xml. |
Action | Configure the jms-destination with the same name in the web.xml to override the ones from web-fragment.xml files. |
Explanation | The connection-factory of the same name cannot be configured in different web-fragment.xml files if it is missing in the web.xml. |
Action | Configure the connection-factory with the same name in the web.xml to override the ones from web-fragment.xml files. |
Explanation | The <distributable/> element was not found in the web fragment. Therefore, the module is not marked distributable. |
Action | Set the <distributable/> element in the web-fragment.xml for all web fragments in the module if you want it marked distributable. |
Explanation | One or more applications specify a virtual host that does not exist. The virtual host configuration may be missing or may contain errors. |
Action | For applications that specify a virtual host via ibm-web-bnd.xml or ibm-web-bnd.xmi files, ensure that a matching virtualHost element is defined in the server.xml file. |
Explanation | The values of default error pages in different web-fragment.xml files must be the same. |
Action | Use the same default error page in the different web-fragment.xml files or configure a default error page the web.xml file to override the default error page from web-fragment.xml files. |
Explanation | It is not allowed to configure the mail-session of the same name in different web-fragment.xml files, while it is missing in the web.xml |
Action | Configure the mail-session with the same name in the web.xml to override the ones from web-fragment.xml files. |
Explanation | It is not allowed to configure the data-source of the same name in different web-fragment.xml files, while it is missing in the web.xml |
Action | Configure the data-source with the same name in the web.xml to override the ones from web-fragment.xml files. |
Explanation | It is not allowed to configure the JNDI references of the same name in different web-fragment.xml files, while it is missing in the web.xml |
Action | Configure the JNDI reference in the web.xml without any injection-targets to include those from each web-fragment.xml or configure all the required configurations in the web.xml file. |
Explanation | It is not allowed to configure the web-fragment itself in <before> and <after> elements |
Action | Remove the web-fragment name from <before> and <after> elements |
Explanation | It is not allowed to configure <others/> in both <before> and <after> elements. |
Action | Remove <others/> from <before> or <after> element. |
Explanation | Circular references are found in the web-fragment.xml files when using relative ordering. |
Action | Fix the circular references using <before> or <after> element in the web-fragment.xml files or use <absolute-ordering> element in the web.xml file. |
Explanation | Unique name is required for the element in each web-fragment.xml file while when using relative sorting ordering. |
Action | Assign unique name for each web-fragment.xml while when using relative sorting ordering or Configure Use absolute sorting <absolute-ordering> element in the web.xml file. |
Explanation | The values of same configuration in the different web-fragment.xml files must be the same. |
Action | Use the same values in the different web-fragment.xml files or configure it in the web.xml file to override those from web-fragment.xml files. |
Explanation | The values of same configuration in the different web-fragment.xml files must be the same. |
Action | Use the same values in the different web-fragment.xml files or configure it in the web.xml file to override those from web-fragment.xml files. |
Explanation | Usually, manifest class path elements are references to JAR files. If the referenced element is necessary to the application, the message indicates a serious problem and should not be ignored. If the referenced element is not necessary to the application, the message indicates a harmless problem and may be ignored. Either the referenced element is absent, is in an incorrect location, or the referenced element is in a correct location and the manifest class path element references a different, incorrect, location. When an element is necessary, it is most commonly indicated by a failure of the application to locate a class or other resource, or by the application locating the wrong version of a class or resource. A common cause of a manifest class path element not being resolved is an update to the structure of an application which made a referenced element obsolete. Another common cause of a manifest class path element not being resolved is the addition of a third party JAR file to an application, where the third party JAR file references a location which was also not added to the application. |
Action | Add, rename, or move application elements, or update the manifest class path by modifying or removing manifest class path elements which cannot be resolved. Manifest class path elements are resolved relative to the location of the enclosing archive file. |
Explanation | The class path is not specified correctly. It must be a relative URI string that points to a jar file or a folder. |
Action | Update the jar file's MANIFEST.MF to provide correct Class-Path definition. |
Explanation | The userid or password has not been specified, or is the empty string. These are not valid as userids or passwords. |
Action | Update the application's configuration to correct the run-as definition. |
Explanation | The configuration of a role in an application has provided a list of run-as definitions, but one of those definitions could not be located. |
Action | Update the application's configuration to provide the run-as definition. |
Explanation | A run-as definition defined by a security role could not be determined due to an exception. |
Action | Investigate the cause of the exception and correct the application configuration. |
Explanation | The configuration of an application has provided a list of special subjects, but the name of one of the special subjects could not be found in that configuration. |
Action | Update the application's configuration to correct the definition of the special subject. |
Explanation | The configuration of a role in an application has provided a list of special subject definitions, but one of those definitions could not be located. |
Action | Update the application's configuration to provide the special subject definition. |
Explanation | A special subject defined by a security role could not be determined due to an exception. |
Action | Investigate the cause of the exception and correct the application configuration. |
Explanation | The configuration of an application has provided a list of groups, but the name of one of the groups could not be found in that configuration. |
Action | Update the application's configuration to correct the definition of the group. |
Explanation | The configuration of a role in an application has provided a list of group definitions, but one of those definitions could not be located. |
Action | Update the application's configuration to provide the group. |
Explanation | A group defined by a security role could not be determined due to an exception. |
Action | Investigate the cause of the exception and correct the application configuration. |
Explanation | The configuration of an application has provided a list of users, but the name of one of the users could not be found in that configuration. |
Action | Update the application's configuration to correct the definition of the user. |
Explanation | The configuration of a role in an application has provided a list of user definitions, but one of those definitions could not be located. |
Action | Update the application's configuration to provide the user. |
Explanation | A user defined by a security role could not be determined due to an exception. |
Action | Investigate the cause of the exception and correct the application configuration. |
Explanation | The configuration of an application has provided a list of security roles, but the name of one of the roles could not be found in that configuration. |
Action | Update the application's configuration to correct the definition of the role. |
Explanation | An application security role definition could not be found, but it is referenced in the application-bnd file. |
Action | Update the application's configuration to provide the role. |
Explanation | An application security role could not be determined due to an exception. |
Action | Investigate the cause of the exception and correct the application configuration. |
Explanation | The security roles for an application could not be determined from the server's configuration as no application-bnd file could be located for the application. |
Action | Update the application to provide the application-bnd file. |
Explanation | The security roles for an application could not be determined from the application-bnd file provided by the application due to an exception. |
Action | Investigate the cause of the exception and correct the application configuration. |
Explanation | A @WebFilter annotation must have at least one of the attributes value, urlPatterns or servletNames. |
Action | Specifiy at least one of the required attributes of the @WebFilter annotation. |
Explanation | A @WebFilter annotation is not permitted to have a urlPatterns attribute if it has a value. |
Action | Ensure that any URL pattern specified in the value of the @WebFilter annotation has been specified in the urlPatterns attribute, and remove the value. It is recommended to use value only if the only attribute on the annotation is the URL pattern. |
Explanation | A @WebServlet annotation is not permitted to have a urlPatterns attribute if it has a value. |
Action | Ensure that any URL pattern specified in the value of the @WebServlet annotation has been specified in the urlPatterns attribute, and remove the value. It is recommended to use value only if the only attribute on the annotation is the URL pattern. |
Explanation | A @WebServlet annotation must have either a value or a urlPatterns attribute. Exactly one must be specified; both must not be omitted. |
Action | Specify any required URL pattern in the value or the urlPatterns attribute of the @WebServlet annotation. It is recommended to use value only if the only attribute on the annotation is the URL pattern. |
Explanation | A class annotated with a @WebServlet annotation must implement the specified interface. |
Action | Ensure that any class annotated with a @WebServlet annotation implements the required interface. |
Explanation | A class annotated with a @WebFilter annotation must implement the specified interface. |
Action | Ensure that any class annotated with a @WebFilter annotation implements the required interface. |
Explanation | A class annotated with a @WebListener annotation must implement one of the interfaces javax.servlet.ServletContextListener, javax.servlet.ServletContextAttributeListener, javax.servlet.ServletRequestListener, javax.servlet.ServletRequestAttributeListener, javax.servlet.http.HttpSessionListener or javax.servlet.http.HttpSessionAttributeListener. |
Action | Ensure that any class annotated with a @WebListener annotation implements one of the interfaces required. |
Explanation | To enable deletion of JAR files within an installed web application the JAR files need to be set up to be deleted, this process failed |
Action | To delete JAR files within an installed web application the server must be stopped prior to deletion |
Explanation | The application has been updated. |
Action | No action is required. |
Explanation | The application has been removed from web container. |
Action | No action is required. |
Explanation | Valid values for the res-auth attribute are "Shareable" and "Unshareable". |
Action | Modify the value of res-sharing-scope. |
Explanation | Valid values for the res-auth attribute are "Application" and "Container". |
Action | Modify the value of res-auth attribute. |
Explanation | The application has been added to web container. |
Action | No action is required. |
Explanation | The resource can not be found using the specified resource reference name. |
Action | Modify the value of res-ref-name. |