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 | 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 | 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 | 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. 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 | 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 | 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 | 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 | 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 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 | Specified servlet is temporarily unavailable. |
Action | Wait and retry operation. Servlet might have been removed from service by server administrator. |
Explanation | The specified servlet is being unloaded from service. |
Action | none. |
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 | 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 | 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 | 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 | 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 | 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 | 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 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 | 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 | The servlet 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 | WebModule 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 {2} logged via ServletContext.log from application {0} with context root {1} and stack trace {3}. |
Action | none. |
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 | 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 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 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 | 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 | 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 | 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 | 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 | 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 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 | 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 incoming request may be corrupted. This is an application error. |
Action | none. |
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 | The request tried to access a forbidden resource. |
Action | Make sure the requesting entity has the required privileges. |
Explanation | DefaultErrorReport was invoked but no error was found. This is a system error. |
Action | Review application to determine cause of problem. |
Explanation | Error that caused the problem. |
Action | none. |
Explanation | Cannot serve the contents of a JSP file |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | Package name of resource does not match the 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 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 file was not renamed after it was compiled. |
Explanation | none |
Action | none |
Explanation | none |
Action | none |
Explanation | See reported error. |
Action | none. |
Explanation | This is a system error. |
Action | Check the FFDC logs for more details on the error. |
Explanation | This is a system error. |
Action | Check the FFDC logs for more details on the error |
Explanation | This is an application error. |
Action | Supply a leading slash before the path and try again. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | The init() method of the target resource ran successfully and the target has been places into service. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | The reaper thread removes servlets that have been inactive for longer than the reaper inactive limit. |
Action | none. |
Explanation | The reaper thread removes the mappings for jsps and other extensions that have been inactive longer the the reaper inactive limit. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | Exception occurred in the reaper thread processing. This is a system error. |
Action | Reaper processing is just a form of garbage collection. |
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 | 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 | 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 | 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 | 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 | 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 | 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 | none. |
Action | See the Error Page Exception for a description of the problem with the specified error page. |
Explanation | The specified annotation helper has not been defined. This is a system error. |
Action | Check for the definition of the specified annotation helper and add it if necessary. |
Explanation | The specified annotation helper is not 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 | 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 | 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 | This is an application error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | none. |
Explanation | This is an application error. |
Action | Review the logs. |
Explanation | This is an application error. |
Action | Check for mapping clash in webconfig.xml |
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 | 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 | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is an application error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is a system error error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | none. |
Explanation | This is a system error. |
Action | none. |
Explanation | This is a system error. |
Action | none. |
Explanation | System action is required. |
Action | Check the status of the directory, including existence, access privileges and available space. |
Explanation | System action is required. |
Action | Check the status of the directory, including existence, access privileges and available space. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | The desired path is already assigned in a servlet mapping. This is an application error. |
Action | Change or remove the mapping from your application configuration. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | This is a system error. |
Action | Review the logs. |
Explanation | 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 | 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 | 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 | 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 | 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 | An exception occurred. |
Action | Review the logs. |
Explanation | The request path maps to a context root on a non-matching virtual host. |
Action | Check to see if an additional virtual host alias needs to be added. |
Explanation | The request path maps to a context root on a non-matching virtual host. |
Action | Follow the instructions in the 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 | The servlet failed to initialize because an error occurred when a resource was injected. |
Action | Verify that the injected resources exist and are accessible to the servlet. |
Explanation | The filter failed to initialize because an error occurred when a resource was injected. |
Action | Verify that the injected resources exist and are accessible to the filter. |
Explanation | The filter did not load during 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. |