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 | None. |
Action | None. |
Explanation | The specified transport name is not valid. |
Action | Define a transport conforming to the transport definition rules. |
Explanation | Failed to add the web group specified in the message to the web container. |
Action | Check the definitions for the web group (web module) in web.xml. |
Explanation | Error in the JNDI service. |
Action | Be sure that you have defined a JNDI service and that its port is not in use by another application. |
Explanation | Connection queue has overflowed. |
Action | Increase the size of the connection queue. |
Explanation | iiopredirector XML contains invalid XML syntax |
Action | Examine the iiopredirector xml for syntax conformance. |
Explanation | None. |
Action | None. |
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 | Initialization parameter name not found. |
Action | Specify a parameter name in the web.xml file. |
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 determin the root cause of this problem. |
Explanation | Invalid format found for a request header. |
Action | Check client header creation. |
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 | 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 | None. |
Action | None. |
Explanation | An error was encountered in the specified servlet. |
Action | Varies by reported cause. |
Explanation | None. |
Action | None. |
Explanation | Could not find a definition for the specified virtual host. |
Action | Make sure the virtual host is defined in the virtualhosts.xml file. |
Explanation | Could not set an attribute. |
Action | Make sure the attribute conforms to attribute guidelines. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An error was encountered in the specified servlet. |
Action | Varies by reported cause. |
Explanation | Class specified to object pool is not accessible. |
Action | Be sure the class is on the object pool's classpath. |
Explanation | Error encountered reading plug-in configuration. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Could not shutdown server. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | None. |
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 | None. |
Action | None. |
Explanation | Error encountered stopping a transport. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | None. |
Action | None. |
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 | A remote object is not serializable. |
Action | Be sure your remote objects implement the Serializable interface. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Problem invoking the specified servlet. |
Action | Be sure the servlet is defined and accessible. |
Explanation | Total read equals zero. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | Internal error encountered. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Could not find the specified resource for a servlet. |
Action | Be sure the resource exists and has been defined. |
Explanation | JarFileClassProvider is invalid. File has been updated. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | An error occurred during a servlet destroy. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The specified servlet is being loaded for service. |
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 | Internal engine error. |
Action | Gather server logs and contact IBM service. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | 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 | 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 | Input class is not poolable. |
Action | Implement the IPoolable interface in the input class. |
Explanation | Could not destroy specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | Could not bind the specified host name to the specified serlvet host. |
Action | Make sure the host name has been specified correctly and that the servlet host has been specified in virtualhosts.xml. |
Explanation | The specified directory is invalid. |
Action | Check directory specification for errors. |
Explanation | Using first server specification found. |
Action | None. |
Explanation | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | Unable to restart a web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | AdminListener. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | None. |
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 invoke service method for the specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | None. |
Action | None. |
Explanation | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | Exception received in http transport. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Internal web container error. |
Action | Gather server logs and contact IBM service. |
Explanation | The specified attribute is not supported. |
Action | Remove the attribute from any XML file that contains it. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Could not load the specified Web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | A request or response serviced by a servlet is not of type HTTP. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | No servlet host found. |
Action | Make sure virtual hosts have been defined in virtualhosts.xml. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | None. |
Action | None. |
Explanation | Could not find the specified resource. |
Action | Be sure the resource exists. |
Explanation | Failure to restart WebGroup. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | Could not initialize the default server. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Could not remove an attribute. |
Action | The attribute might not have been present. Be sure attribute exists and retry. |
Explanation | None. |
Action | None. |
Explanation | Could not get the specified remote attribute. |
Action | Could be caused by connectivity problems. Wait and try again. |
Explanation | The specified servlet could not be found. |
Action | Make sure the servlet exists and is defined properly in the web.xml file. |
Explanation | None. |
Action | None. |
Explanation | None. |
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 | 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 | Specified servlet is temporarily unavailable. |
Action | Wait and retry operation. Servlet might have been removed from service by server administrator. |
Explanation | Could not start the transport for the administration service. |
Action | Gather logs and contact IBM support. |
Explanation | None. |
Action | None. |
Explanation | None. |
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 | Two initialization parameters have the same xml id. |
Action | Make sure all initialization parameters have unique id's. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Problem releasing a session. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Unable to remove the specified remote attribute. |
Action | Potentially a network problem. Wait and try again. |
Explanation | Servlet is no longer available for service. |
Action | Restart the web application containing the servlet. |
Explanation | Missing flag value. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | Failure to create distributed attribute list. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Internal server error. |
Action | Gather logs and contact IBM service. |
Explanation | Could not find a virtual host for the web application. |
Action | Be sure the web application is bound to a valid virtual host. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | 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 | 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 Integer 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 | IO error encountered. |
Action | Varies depending on reported root cause. |
Explanation | Attempting to output a buffer of size less than 0. |
Action | Only write buffers of size of 0 or greater. |
Explanation | The specified servlet host could not be found. |
Action | Be sure the virtual host specifications in virtualhosts.xml are valid. |
Explanation | A servlet encountered the specified error. |
Action | Varies by root cause. |
Explanation | Problem encountered while shutting down the server. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The specified initialization parameter is missing a value. |
Action | Be sure the definition for the parameter in the web.xml file is complete. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Internal server error. |
Action | Gather server logs and contact IBM Service. |
Explanation | Problem encountered invoking the specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The server connection was reset. |
Action | Retry any previously failing operations. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | Invalid content length. |
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 | 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 | None. |
Action | None. |
Explanation | Problem encountered disabling the specified servlet. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Security problem encountered during request processing. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | Servlet mapping defined with the specified servlet, but servlet was not defined. |
Action | Make sure the servlet is defined in the web.xml file. |
Explanation | Could not find the bindings for the web application. |
Action | Be sure that the ibm-web-bnd.xmi file exists for the application. |
Explanation | Number format problem in the specified environment entry. |
Action | Correct the environment entry. |
Explanation | Invalid type encountered in java:comp binding. |
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 | Failure starting a server transport. |
Action | Be sure that the defined transport port is not in use by another application. |
Explanation | A virtual host has not been bound to the specified web module. |
Action | Specify a virtual host in the web application's ibm-web-bnd.xmi file. |
Explanation | Unable to load the specified WAR file. Most likely a definition problem. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Could not find the definition for the specified web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Problem encountered reading the web module definition for the web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | A resource defined in the web application is empty. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Problem encountered reading the web module definition for the web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Problem encountered removing the specified web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | Could not load the specified file. |
Action | Be sure the specified file exists. |
Explanation | Could not load the specified file. |
Action | Be sure the specified file exists. |
Explanation | An attempt was made to set the response buffer size after the response was already commited. |
Action | Remove the setBufferSize() call or move it to a position before the response commit. |
Explanation | Could not determine the context path for a web application. |
Action | Be sure a context path has been defined for the web application in the application.xml file. |
Explanation | Could not load the specified session context. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Problem encountered rolling back the specified user transaction. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, 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 | Could not restart the specified web application. |
Action | Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | No virtual host has been bound to the web application. Using default. |
Action | If a different virtual host is desired, specify one in the web application bindings. |
Explanation | None. |
Action | None. |
Explanation | Session manager has not been configured for the web container. |
Action | Define the session manager properties in the server.xml file. |
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 | A JSP file that is deployed in web.xml and is indicated to load-on-startup failed to translate or compile. |
Action | Examine the server logs in order to determine the root cause of the failure. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | LocalTransaction rolled-back due to setRollbackOnly action by the application |
Action | Examine the server logs in order to determine the root cause of the failure. Also check your application for setRollBackOnly calls. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | A JSP page that uses server-side Javascript via the BSF engine was detected. |
Action | Replace server-side Javascript with other mechanisms, such as JSP 2.0 Expression Language in WAS 6.0 |
Explanation | |
Action |
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 happenned 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 supplied argument was not of an accepted type. |
Action | Please suuply a valid argument |
Explanation | The supplied argument was not a valid date format. |
Action | Please supply a valid argument |
Explanation | The supplied argument was not a valid header format. |
Action | Please supply a valid argument |
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 | The present configuration does not allow directory browsing for the web application. |
Action | You can enable this feature by setting 'directoryBrowsingEnabled=true' in the ibm-web-ext.xmi file in the WEB-INF directory. |
Explanation | None |
Action | None |
Explanation | None |
Action | None. |
Explanation | None. |
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 throught the admin console |
Explanation | |
Action |
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 poassible |
Action | None |
Explanation | The writer for this response has already been obtained. Please use the existing writer |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | Internal exception. |
Action | None |
Explanation | Internal exception. |
Action | None. |
Explanation | The servlet chain that has been defined can only handle HTTP requests. |
Action |
Explanation | The incoming request may be corrupted. |
Action | None. |
Explanation | This error occured 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 | None |
Action | None |
Explanation | None |
Action | None |
Explanation | Cannot serve the contents of a JSP file |
Action | None |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
Explanation | |
Action |
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 proccessing. |
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 |
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 | none. |
Action | none. |
Explanation | The default servlet has already been mapped to the file serving uri pattern specified in ibm-web-ext.xmi which is by default /*. |
Action | Please set fileServingEnabled=false in the ibm-web-ext.xmi file which is under WEB-INF folder. |
Explanation | The keystore or truststore type specified is invalid. |
Action | Modify the SSL configuration so that the keystore or truststore type is a valid type. You can check the keystore and truststore types by loading them in WebSphere's IKeyMan tool. |