Explanation | Attempting to output a buffer of size less than 0. |
Action | Only write buffers of size of 0 or greater. |
Explanation | Uncaught exception thrown in servlet service method. |
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 | Invalid format found for a request header. |
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. |
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, please 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, please 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, please contact IBM Support. |
Explanation | Invalid date format. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please 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, please contact IBM Support. |
Explanation | Could not destroy specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please 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 invalid. |
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 thrown in one of the service methods of the servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Internal web container error. |
Action | Gather server 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 | The specified servlet is being unloaded from service. |
Action | none. |
Explanation | Could not initialize the specified servlet. |
Action | Make sure the servlet class file is available on the application classpath. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please 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, please 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, please 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, please 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, please contact IBM Support. |
Explanation | IO error encountered. |
Action | Varies depending on reported root cause. |
Explanation | Attempting to output a buffer of size less than 0. |
Action | Only write buffers of size of 0 or greater. |
Explanation | 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, please contact IBM Support. |
Explanation | Problem encountered parsing servlet parameters. |
Action | Check parameter definitions in the web.xml file. |
Explanation | Security problem encountered during request processing. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Security problem encountered during request processing. |
Action | Varies with root cause. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Could not load the specified file. |
Action | Be sure the specified file exists. |
Explanation | Could not load the specified file. |
Action | Be sure the specified file exists. |
Explanation | An attempt was made to set the response buffer size after the response was already committed. |
Action | Remove the setBufferSize() call or move it to a position before the response commit. |
Explanation | Problem encountered rolling back the specified user transaction. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please 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. |
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 |
Action | Either set the buffer size before writing data or reset the buffer before setting the size. |
Explanation | A required class was not found |
Action | Make sure your classpath reflects all the classes you may be accessing |
Explanation | The class mentioned needs to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet |
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 affect the processing of the request. |
Action | none. |
Explanation | The mentioned file was not found. |
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) |
Action | none. |
Explanation | The parameter with the mentioned name has no value. This is a required parameter. |
Action | Please supply a value to the mentioned parameter. |
Explanation | Application requested a PrintWriter after the ServletResponse OutputStream had already been obtained. |
Action | Review application to determine if both PrintWriter and OuputStream were obtained. |
Explanation | Servlet could not find a required class needed to service the request. |
Action | none. |
Explanation | The class mentioned needs to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet |
Action | The class mentioned needs 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 |
Action | Please re-compile the class and try again. |
Explanation | A required class was not found |
Action | Make sure all required classes are placed in the folders/Jars representing the classpath |
Explanation | The virtual host was not found |
Action | Please check the virtual host configuration in the virtualhosts.xml file, or through the admin console |
Explanation | Unable to locate Virtual Host defined to handle this request URI. |
Action | none. |
Explanation | none. |
Action | Please recompile 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. |
Action | Please 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 |
Action | none. |
Explanation | The writer for this response has already been obtained. Please use the existing writer |
Action | Review application to determine if both PrintWriter and OuputStream were obtained. |
Explanation | none. |
Action | none. |
Explanation | Internal exception. |
Action | Contact WebSphere Support for further assistance. |
Explanation | Internal exception. |
Action | Contact WebSphere Support for further assistance. |
Explanation | The servlet chain that has been defined can only handle HTTP requests. |
Action | none. |
Explanation | The incoming request may be corrupted. |
Action | none. |
Explanation | This error occurred when the webcontainer tried to load an internal implementation class. |
Action | Check to make sure the original WAS classpath has not been modified. |
Explanation | The request tried to access a forbidden resource. |
Action | Please make sure the requesting entity has the required privileges. |
Explanation | DefaultErrorReport was invoked but no error was found. |
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. |
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 | See reported error. |
Action | none. |
Explanation | Check the FFDC logs for more details on the error |
Action | Check the FFDC logs for more details on the error |
Explanation | Check the FFDC logs for more details on the error |
Action | Check the FFDC logs for more details on the error |
Explanation | none. |
Action | Please 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 executed 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. |
Action | Reaper processing is just a form of garbage collection. |
Explanation | none. |
Action | none. |
Explanation | SyncToOSThread synchronizes the J2EE role identity to the OS thread, meaning that the OS thread identity is made equal to the J2EE 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. |
Action | If SyncToOSThread capabilities are desired for the server in question, please refer to the InfoCenter 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. Please refer to the Infocenter 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 executed successfully and the target has been removed from service. |
Action | none. |
Explanation | Invalid request encoding specified on the request.. |
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. |
Action | Be sure the web group and virtual host is defined and deployed. |
Explanation | WebContainer is not initialized until an application has been installed. |
Action | none. |