websphere-errors-text.txt

===
[{0}][{1}][Servlet.LOG]:.{2}:.{3}=SRVE0181I: [{0}] [{1}] [Servlet.LOG]: {2}: {3}
[{0}][{1}][Servlet.LOG]:.{2}=SRVE0180I: [{0}] [{1}] [Servlet.LOG]: {2}
[{0}].Destroy.successful=SRVE0253I: [{2}] [{1}] [{0}]: Destroy successful.
[{0}].Initialization.successful=SRVE0242I: [{2}] [{1}] [{0}]: Initialization successful.
{0}.is.not.a.valid.class=SRVE0217E: {0} is not a valid class
[{0}].reported.an.error=SRVE0235E: [{0}] reported an error
Account for the exception in target code.
A character, which is not valid, exists in the query string and has been ignored.
Action	Account for the exception in target code.
Action	Add a @MultipartConfig annotation to this servlet or add a multipart-config element to this servlet in the web.xml.
Action	Add a url pattern or servlet name to the filter mapping.
Action	Add a url pattern to the servlet mapping.
Action	Add the listener via an annotation or via the web.xml to enable the execution of this method.
Action	An exception occurred while creating the listener instance
Action	A user action is not required.
Action	Be sure the class exists and is visible on the application class path.
Action	Be sure the specified file exists and is in the correct format according to java.utils.Properties.
Action	Be sure the specified file existsand is in the correct format according to java.utils.Properties.
Action	Be sure the web group and virtual host is defined and deployed.
Action	Change code to implement the expected interface.
Action	Change or remove the mapping from your application configuration.
Action	Change the application descriptors to 2.5 level if you are using a * mapping.
Action	Change the class being instantiated to a concrete class or remove the definition as a servlet.
Action	Change the value of the attribute to a valid integer value.
Action	Check client header creation.
Action	Check directory specification for errors.
Action	Check for errors earlier in the logs that may have caused initialization to fail.
Action	Check for mapping clash in webconfig.xml
Action	Check for the definition of the specified annotation helper and add it if necessary.
Action	Check if the class has been removed.
Action	Check if the Session Manager is configured correctly.
Action	Check Java 2 Security policy to verify whether this access should be allowed.
Action	Check that the class file was not renamed after it was compiled.
Action	Check that the classname has been defined in the server using the proper case and fully qualified package.
Action	Check that the class resides in the proper package directory.
Action	Check that the class was compiled using the proper case (as defined in the class definition).
Action	Check that the class was transferred to the filesystem using a binary transfer mode.
Action	Check the annotation helper implementation class and fix it.
Action	Check the class specified in the Extension Point.
Action	Check the exception logs for the reason that the annotation helper could not be instantiated.
Action	Check the FFDC logs for more details on the error
Action	Check the FFDC logs for more details on the error.
Action	Check the server logs and exception to determine what might have caused the namespace binding problem.
Action	Check the servlet mappings in webconfig.xml and make appropriate changes
Action	Check the status of the directory, including existence, access privileges and available space.
Action	Check the System.out and System.err logs for more information on the exception generated.
Action	Check the value of the responsebuffersize custom property.
Action	Check the virtual host configuration in the virtualhosts.xml file, or through the administrative console.
Action	Check to make sure the original product class path has not been modified.
Action	Check to see if an additional virtual host alias needs to be added.
Action	Check your server configuration to see what the value is set to.
Action	Check your web.xml has a servlet definition for this servlet mapping.
Action	Collect server logs and contact IBM support.
Action	Configure this property at the web container level.
Action	Configure this property under the Logging Service (see information center for more details on HTTP Access Logger).
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.
Action	Edit your virtual host alias and remove any duplicates.
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
Action	Either change the context root of one of the web applications or move one to a different virtual host.
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.
Action	Either modify the application to use a different cookie name, domain, or path or modify the restricted programmatic session cookie values
Action	Either set the buffer size before writing data or reset the buffer before setting the size.
Action	Enable programmatic session configuration.
Action	Ensure that all of the parameters in the inbound request are valid.
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.
Action	Ensure that the mentioned file is in place.
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.
Action	Examine the exception message, the source code of the servlet, and the server logs to determine the root cause of the problem.
Action	Examine the server logs in order to determine the root cause of the problem. If there are no related messages or they do not help to resolve the problem, contact IBM Support.
Action	Examine the server logs to determine the root cause of the problem.
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.
Action	Follow the instructions in the Information Center to add a new virtual host alias.
Action	Gather logs and contact IBM service.
Action	Gather server logs and contact IBM service.
Action	Gather server logs and contact IBM support.
Action	Gather web container trace and contact IBM support.
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.
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.
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/ .
Action	If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
Action	If this exception occurs, please contact support.
Action	If this is not the desired behavior, update the property com.ibm.ws.webcontainer.donotservebyclassname.
Action	Increase the file size attribute of the multipart configuration for the given servlet.
Action	Increase the request size attribute of the multipart configuration for the given servlet.
Action	Install an application to initialize the web container.
Action	Investigate nested error and perform appropriate action.
Action	Investigate the client to determine why the content-length field does not match the size of the post data. If the client is setting it correctly, investigate where in the network the content-length field becomes invalid.
Action	Investigate the root cause of the exception and determine if application still functions properly despite these failures.
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.
Action	It is recommended to enable the object pool service.
Action	Look in the error log to determine the root cause of this problem.
Action	Make sure all required classes are placed in the folders/jars representing the class path
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.
Action	Make sure that the server configuration depends upon the session feature set.
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.
Action	Make sure the class exists within the web module's class loader.
Action	Make sure the directory exists or that you are requesting the right directory.
Action	Make sure the host name has been specified correctly and that the servlet host has been specified in virtualhosts.xml.
Action	Make sure the requesting entity has the required privileges.
Action	Make sure the servlet class file is available on the application class path.
Action	Make sure your class path reflects all the classes you may be accessing
Action	Modify application code according to error explanation.
Action	Modify the application code to add a listener of the accepted type
Action	Modify the class to add one of the urlPatterns or value attributes
Action	Modify the class to extend the correct super class
Action	Modify the class to only include one of the urlPatterns or value attribute
Action	Modify the class to specify a valid name in the annotation
Action	Modify the failing class to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet
Action	Modify the failing servlet/JSP.
Action	Modify the servlets making previous requests such that the current request is of type multipart/form-data.
Action	Move the code calling the current method into a ServletContainerInitalizer's onStartup or a ServletContextListener's contextInitialized method.
Action	No action necessary. Check for conflicts in the deployment descriptor, annotations, and source code that could dynamically add this servlet configuration.
Action	none
Action	none.
Action	Only write buffers of size of 0 or greater.
Action	Place servlet class on classpath of the application server.
Action	Please check the file serving attributes in your ibm-web-ext.xmi or ibm-web-ext.xml file.
Action	Reaper processing is just a form of garbage collection.
Action	Re-compile the class and try again.
Action	Recompile the servlet using only the classes in the application's runtime class path.
Action	Re-compile the servlet with all required components placed in the class path.
Action	Refer to the information center for more details.
Action	Remove the additional call to dispatch.
Action	Remove the duplicate mapping.
Action	Remove the setBufferSize() call or move it to a position before the response commit.
Action	Review application to determine cause of problem.
Action	Review application to determine if both PrintWriter and OuputStream were obtained. Modify the failing servlet/JSP to only obtain one or the other.
Action	Review logs to determine whether the specified encoding is a valid encoding.
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.
Action	Review the logs.
Action	Review the logs and contact support.
Action	Review the logs to determine the status code of the error.
Action	Review the message and exception to determine if any action is required. Additional information for may be available in the server logs.
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.
Action	Review the message to determine the root cause of the problem.
Action	See root cause.
Action	See the Error Page Exception for a description of the problem with the specified error page.
Action	See the root cause of the exception.
Action	Set com.ibm.ws.webcontainer.disallowserveservletsbyclassname to true to block serving all classes by classname.
Action	Set fileServingEnabled=false in the ibm-web-ext.xmi file which is under WEB-INF folder.
Action	Supply a leading slash before the path and try again.
Action	Supply a value to the mentioned parameter.
Action	=The class mentioned needs to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet
Action	The method restartWebApplication no longer does anything. Use the ApplicationManager MBean to start and restart an 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.
Action	Unexpected isUserInRole exception, returning of isUserInRole false.
Action	Use the migration utilities to migrate your configuration model from the transports to the new channel chains.
Action	Varies by root cause.
Action	Varies depending on reported root cause.
Action	Varies with root cause.
Action	Verify a valid servlet class was provided for the servlet.
Action	Verify that the cell.xml exists and is readable.
Action	Verify that the injected resources exist and are accessible to the filter.
Action	Verify that the injected resources exist and are accessible to the listener. To re-initialize the listener, restart the listener application.
Action	Verify that the injected resources exist and are accessible to the servlet.
Action	Verify that the path is correct and there are no hardware issues.
Action	Verify that the ServletContainerInitializer is configured correctly.
Action	Verify the class exists and has all of its dependencies in the classpath.
Action	Verify the class exists within the application.
Action	Verify the client is sending the full request.
Action	Verify the custom property is correct
Action	Verify the jar file is valid and is not being updated during traversal.
Action	Verify the listener is a valid type and available to the application
Action	Verify the mapping is valid.
Action	Verify there are no code logic or timing issues causing this illegal behavior.
Action	Verify there is a public no argument constructor on the servlet.
Action	Verify the timer manager selected in the web container panel is valid.
Action	Verify the value for the single thread model pool size is a valid integer.
Action	Verify the value for the single thread model servlet maximum idle time is a valid integer.
Action	Verify whether this call is necessary. If the header really needs to be sent, it should be set before committing the response.
Action	Wait and retry operation. Servlet might have been removed from service by server administrator.
Action	You can only modify the session configuration before the application is initialized.
An attempt was made to set the response buffer size after the response was already committed. This is an application error.
An exception occurred.
annotation.helper.cannot.create=SRVE0263E: The annotation helper {0} cannot be instantiated.
annotation.helper.not.defined=SRVE0261E: The annotation helper {0} has not been defined.
annotation.helper.wrong.type=SRVE0262E: The annotation helper {0} is not of type com.ibm.wsspi.webcontainer.AnnotationHelper.
Application.classpath=SRVE0234I: Application class path=[{0}]
Application requested a PrintWriter after the ServletResponse OutputStream had already been obtained. This is an application error.
Application server identifier.
ARD is not enabled correctly. System action is required.
ARD.Not.Enabled=SRVE0306W: ARD is not enabled so so attempts to do asynchronous includes and insertFragment calls will all be synchronous
A required class was not found. This is an application error.
A servlet mapping specified in the webconfig.xml is not valid. System action is required.
A thread is no longer tied to a single connection. System action is required.
Attempting to output a buffer of size less than 0. This is an application error.
A user action is not required.
be.debugged.by.recompiling.the.servlet.using.only.the.classes.in.the.application's.runtime.classpath=SRVE0210I: This problem can be debugged by recompiling the servlet using only the classes in the application's runtime class path
Be sure the specified file exists and is in the correct format according to java.utils.Properties.
Be sure the specified file existsand is in the correct format according to java.utils.Properties.
Be sure the web group and virtual host is defined and deployed.
Cannot serve the contents of a JSP file
Cannot.set.buffer.size.after.data=SRVE0186E: Can't set buffer size after data has been written to stream
cannot.use.error.page=SRVE0260E: The server cannot use the error page specified for your application to handle the Original Exception printed below.
Change code to implement the expected interface.
Change or remove the mapping from your application configuration.
Change the application descriptors to 2.5 level if you are using a * mapping.
Check client header creation.
Check directory specification for errors.
Check for mapping clash in webconfig.xml
Check for the definition of the specified annotation helper and add it if necessary.
Check if the Session Manager is configured correctly.
Check that the class file was not renamed after it was compiled.
Check that the classname has been defined in the server using the proper case and fully qualified package.
Check that the class resides in the proper package directory.
Check that the class was compiled using the proper case (as defined in the class definition).
Check that the class was transferred to the filesystem using a binary transfer mode.
Check the annotation helper implementation class and fix it.
Check the exception logs for the reason that the annotation helper could not be instantiated.
Check the FFDC logs for more details on the error
Check the FFDC logs for more details on the error.
Check the servlet mappings in webconfig.xml and make appropriate changes
Check the status of the directory, including existence, access privileges and available space.
Check the virtual host configuration in the virtualhosts.xml file, or through the administrative console.
Check to make sure the original WAS class path has not been modified.
Check to see if an additional virtual host alias needs to be added.
Check.your.classpath.ensure.all.classes.present=SRVE0187E: Check your class path to ensure that all classes required by the servlet are present.
chown.failed=SRVE0288E: chown failed, tried to run command: [{0}] Exit Code: [{1}]
Class.{0}.does.not.implement.servlet=SRVE0188E: Class {0} does not implement servlet
class.compiled.using.proper.case=SRVE0230E: Check that the class was compiled using the proper case (as defined in the class definition).
classname.defined.in.server.using.proper.case.and.fully.qualified.package=SRVE0228E: Check that the classname has been defined in the server using the proper case and fully qualified package.
class.not.found=SRVE0213E: class not found
class.not.renamed.after.compiled=SRVE0231E: Check that the class file was not renamed after it was compiled.
class.resides.in.proper.package.directory=SRVE0227E: Check that the class resides in the proper package directory.
class.transfered.using.binary.mode=SRVE0229E: Check that the class was transferred to the filesystem using a binary transfer mode.
Configure this property at the webcontainer level.
Configure this property under the Logging Service (see information center for more details on HTTP Access Logger).
context.root.already.in.use=SRVE0164E: Web Application {0} uses the context root {1}, which is already in use by Web Application {2}. Web Application {3} will not be loaded.
Could not bind the specified host name to the specified servlet host.
could.not.create.wrapper.for.servlet=SRVE0299E: Could not create wrapper for servlet [{0}]
Could not destroy specified servlet. This is an application error.
Could not find a web group (web module) or virtual host to handle the request. This is an application error.
Could not initialize the specified servlet. This is an application error.
Could not initialize the web application specified in the message. Check the error log for more details.
Could not load the specified file. System action is required.
Could not obtain a valid Session Context for the WebApp. System action is required.
Date format is not valid.
DefaultErrorReport was invoked but no error was found. This is a system error.
Either change the context root of one of the web applications or move one to a different virtual host.
Either set the buffer size before writing data or reset the buffer before setting the size.
encountered.problems.while.removing.servlet=SRVE0301I: Encountered problems while removing servlet {0}. Details: {1}
Ensure that the mentioned file is in place.
error.adding.channel=SRVE0312E: There was an adding while adding a channel: {0}
error.adding.servlet.mapping.file.handler=SRVE0278E: Error while adding servlet mapping --> {0}.
error.adding.servlet.mapping.for.servlet=SRVE0275E: Error while adding servlet mapping for servlet [{0}] in application [{1}]: {2}
error.initializing.extension.factories=SRVE0264E: Error occured while initializing Extension Factories: {0}
error.initializing.filters=SRVE0267E: Error occured while initializing filters: {0}
Error.Initializing.for.Next.Request=SRVE0070E: Error initializing for next request
error.initializing.servlet=SRVE0276E: Error while initializing Servlet [{0}]: {1}
Error.in.WebContainer.custom.property.value=SRVE0310E: There was an error in a custom property: {1}
error.notifying.listeners.of.WebApp.start=SRVE0265E: Error occured while notifying listeners of WebApp start: {0}
error.obtaining.session.context=SRVE0268E: Error obtaining Session Context for the WebApp: {0}
error.occurred.processing.request=SRVE0185E: An error has occurred while processing request:
Error.occurred.while.finishing.request=SRVE0189E: Error occurred while finishing request
Error.occurred.while.invoking.error.reporter=SRVE0115E: Error occurred while invoking error reporter {0}
error.on.collaborator.started.call=SRVE0237E: Error occurred while invoking initialization collaborator on started() call
error.on.collaborator.starting.call=SRVE0236E: Error occurred while invoking initialization collaborator on starting() call
Error.Parsing.Parameters=SRVE0133E: An error occurred while parsing parameters. {0}
error.processing.global.listeners.for.webapp=SRVE0279E: Error occured while processing global listeners for the application {0}: {1}
Error.Report=SRVE0233E: Error Report
Error that caused the problem.
error.while.adding.servlet.mapping.for.path=SRVE0274W: Error while adding servlet mapping for path-->{0}, wrapper-->{1}, application-->{2}.
error.while.adding.static.file.processor=SRVE0302E: Error while adding static file processor: {0}
error.while.initializing.jsp.as.servlet=SRVE0273E: Error while initializing JSP as servlet [{0}] in application [{1}]: {1}
error.while.initializing.servlets=SRVE0266E: Error occured while initializing servlets: {0}
error.while.setting.WebAppAttributes=SRVE0282E: Error occured while setting WebAppAttribues: {0}
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.
Examine the server logs to determine the root cause of the problem.
exception.caught.destroying.context=SRVE0285E: Exception caught while destroying context: {0}
exception.caught.in.notifyServletContextCreated=SRVE0284E: Exception caught in notifyServletContextCreated: {0}
exception.caught.in.notifyServletContextDestroyed=SRVE0286E: Exception caught in notifyServletContextDestroyed: {0}
exception.occured.while.creating.wrapper.for.servlet=SRVE0298E: Exception occured while creating wrapper for servlet [{0}]: {1}
Exception occurred in the reaper thread processing. This is a system error.
Exception=SRVE0315E: An execption occurred: {0}
Exception that occurred when processing the request.
exception.while.initializing.context=SRVE0283E: Exception caught while initializing context: {0}
Explanation	A character, which is not valid, exists in the query string and has been ignored.
Explanation	A class in the web module could not be initialized so it cannot be scanned for annotations.
Explanation	A filter mapping is incomplete without a url pattern or servlet name to map to.
Explanation	An attempt was made to set the response buffer size after the response was already committed. This is an application error.
Explanation	An error occurred while invoking a call to AsyncContext dispatch.
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.
Explanation	An exception occurred.
Explanation	An exception occurred invoking the async error mechanism.
Explanation	An exception occurred invoking the async listeners.
Explanation	An exception occurred processing reference data. Application will attempt to start anyway.
Explanation	An exception occurred retrieving the peer certificate.
Explanation	An exception occurred while creating the listener instance
Explanation	An exception occurred while trying to add a listener
Explanation	An exception was thrown by one of the service methods of the servlet. This is an application error.
Explanation	An exception was thrown from a filter.
Explanation	An IllegalAccessException occurred calling newInstance on the servlet.
Explanation	An InstantiationException occurs when trying to create a new instance of an interface or abstract class.
Explanation	An internal error caused the reference context that enables injection to not be initialized properly.
Explanation	An internal server error occurred creating the channel object.
Explanation	An internal server error occurred destroying the servlet.
Explanation	An internal server error occurred unloading the servlet.
Explanation	An IOException can occur for any number of reasons related to I/O.
Explanation	An IOException was thrown from WebContainer's handleRequest method.
Explanation	A NumberFormatException occurred when trying to set the single thread model pool size.
Explanation	A NumberFormatException occurred when trying to set the single thread model servlet maximum idle time.
Explanation	An UnavailableException was thrown from the servlet.
Explanation	An unexpected configuration exception occurred.
Explanation	An unexpected configuration exceptoin occurred.
Explanation	An unexpected error occurred starting the web container channel chains.
Explanation	An unexpected error occurred while populating the namespace.
Explanation	An unexpected exception occurred adding the WebContainerService.
Explanation	An unexpected exception occurred and details were provided on the resulting error page. This is a system error.
Explanation	An unexpected exception occurred closing the output stream.
Explanation	An unexpected exception occurred during resource injection.
Explanation	An unexpected exception occurred flushng out the rest of the response data.
Explanation	An unexpected exception occurred handling an extension point.
Explanation	An unexpected exception occurred initializing the login processor.
Explanation	An unexpected exception occurred initializing the logout processor.
Explanation	An unexpected exception occurred initializing the output stream.
Explanation	An unexpected exception occurred initializing the security collaborator.
Explanation	An unexpected exception occurred removing the web module.
Explanation	An unexpected exception occurred when trying to retrieve the session context
Explanation	An unexpected internal error has caused a mismatch between the expected state of the output buffer and the actual state.
Explanation	An unexpected internal server error occurred when initializing the target mappings.
Explanation	An unexpected internal server error occurred while adding a web application collaborator.
Explanation	An unexpected internal server error occurred while adding the static file processor.
Explanation	An unexpected internal server error occurred while registering web module MBean.
Explanation	An unexpected servlet engine exception occurred. This is a system error.
Explanation	An unexpected ServletException occurred adding a servlet dynamically. This can occur, for example, if the MBean names of two servlets collide.
Explanation	Application requested a PrintWriter after the ServletResponse OutputStream had already been obtained. This is an application error.
Explanation	Application server identifier.
Explanation	A problem occurred while initializing the application's ServletContainerInitializers.
Explanation	ARD is not enabled correctly. System action is required.
Explanation	A required class was not found. This is an application error.
Explanation	A security problem was encountered during request processing.
Explanation	A ServletContextListener can not be added from another ServletContextListener
Explanation	A servlet mapping is incomplete without a url pattern to map to.
Explanation	A servlet mapping specified in the webconfig.xml is not valid. System action is required.
Explanation	A servlet with the same name already exists for this application.
Explanation	A session cannot be accessed. The session manager feature set has not been started.
Explanation	A thread is no longer tied to a single connection. System action is required.
Explanation	Attempting to output a buffer of size less than 0. This is an application error.
Explanation	Because creation of the search path involves file system access, IOExceptions may occur.
Explanation	Cannot serve the contents of a JSP file
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).
Explanation	Classpath errors occurred when serving the servlet.
Explanation	Could not bind the specified host name to the specified servlet host.
Explanation	Could not find a web group (web module) or virtual host to handle the request. This is an application error.
Explanation	Could not initialize the specified servlet. This is an application error.
Explanation	Could not initialize the web application specified in the message. Check the error log for more details.
Explanation	Could not instantiate a class for use by the object pool. This is a system error.
Explanation	Could not load the specified file. System action is required.
Explanation	Could not obtain a valid Session Context for the web application. System action is required.
Explanation	Date format is not valid.
Explanation	DefaultErrorReport was invoked but no error was found. This is a system error.
Explanation	Error creating PMI statistics group.
Explanation	Error exception logged for a servlet by use of the ServletContext.
Explanation	Error message and exception logged for a servlet for a servlet by use of the ServletContext..
Explanation	Error occurred while preparing the servlet wrapper for initialization.
Explanation	Error processing has already been invoked by another thread.
Explanation	Error removing PMI statistics instance.
Explanation	Error that caused the problem.
Explanation	Exception occurred in the reaper thread processing. This is a system error.
Explanation	Exception that occurred when processing the request.
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.
Explanation	Filters can only be dynamically added before the ServletContext is initialized.
Explanation	Format found for a request header is not valid.
Explanation	HttpServletResponse.sendError was called with a status code but no explanation.
Explanation	Illegal value for responsebuffersize custom property.
Explanation	Informational message and exception logged for a servlet by use of the ServletContext..
Explanation	Informational message and stack trace logged via ServletContext.log from an application.
Explanation	Informational message logged for a servlet by use of the ServletContext.
Explanation	Informational message logged via ServletContext.log from an application.
Explanation	Internal exception.
Explanation	Internal server error.
Explanation	Internal web container error.
Explanation	IO error encountered.
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.
Explanation	IOExceptions can occur when looking at jar files if the file is changed or closed during traversal.
Explanation	Java 2 Security policy prevented deleting the temporary directory
Explanation	Missing flag value.
Explanation	none
Explanation	none.
Explanation	Once a response is committed, you cannot set more response headers.
Explanation	One of the servlets or filters in the request does not support asynchronous servlets.
Explanation	Package name of resource does not match the compiled class file's package. This is an application error.
Explanation	Problem encountered parsing servlet parameters.
Explanation	Problem encountered rolling back the specified user transaction. This is an application error.
Explanation	Problem invoking postConstruct or preDestroy.
Explanation	Problem releasing a session.
Explanation	Programmatic session configuration has been disabled on this server.
Explanation	Request encoding specified on the request is not valid. This is an application error.
Explanation	Security problem encountered during request processing. This is a system error.
Explanation	See reported error.
Explanation	Servlet could not find a required class needed to service the request. This is an application error.
Explanation	Servlet is being destroyed after wait has timed out.
Explanation	Servlet is still handling the request. Waiting for request to complete before calling destroy.
Explanation	Servlets can only be dynamically added before the ServletContext is initialized.
Explanation	Some annotations can only be applied to classes which extend the correct type.
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.
Explanation	Specified servlet is temporarily unavailable.
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.
Explanation	System action is required.
Explanation	The administrative console should not allow you to pick an invalid timer manager JNDI name.
Explanation	The administrator has disabled changing the cookie configuration for the cookie matching the domain, name, and path
Explanation	The attempted operation cannot be performed in an included servlet/JSP (Refer to the Servlet specification). This is an application error.
Explanation	The class can not specify both urlPatterns and value in the annotation
Explanation	The class must specify a valid name in the annotation
Explanation	The class must specify patterns in the annotation via the urlPatterns or value attribute
Explanation	The class was not found in the class loader when processing the ServletContainerInitializer HandlesTypes annotation.
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.
Explanation	The content length does not match the length of the post data. This is an application error.
Explanation	The context has already been initialized. No updates are allowed to the session configuration.
Explanation	The createStatsInstance() method created an exception when it was called to create the statistics instance. No statistic were collected.
Explanation	The desired path is already assigned in a servlet mapping. This is an application error.
Explanation	The destroy() method of the target resource ran successfully and the target has been removed from service.
Explanation	The file being uploaded via the multipart/form-data request is larger than the maximum configured size.
Explanation	The file serving attribute com.ibm.ws.webcontainer.optimizefileservingsize could not be parsed property.
Explanation	The filter did not load during startup.
Explanation	The filter failed to initialize because an error occurred when a resource was injected.
Explanation	The incoming request may be corrupted. This is an application error.
Explanation	The init() method of the target resource ran successfully and the target has been places into service.
Explanation	The JSP specification level supported by the application server.
Explanation	The listener being programmatically added does not implement a valid listener type
Explanation	The listener failed to initialize because an error occured when a resource was injected.
Explanation	The mentioned file was not found. This is an application error.
Explanation	The method restartWebApplication no longer does anything. Use the ApplicationManager MBean to start and restart an application.
Explanation	The method startAsync cannot be called after a complete per the Servlet specification.
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.
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.
Explanation	The multipart/form-data request is larger than the maximum configured size.
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.
Explanation	The number of parameters contained in the inbound request exceeds the maximum number of parameters that can be included in a inbound request.
Explanation	The object pool service improves the performance of the web container, but it has been disabled. This is a system error.
Explanation	The parameter with the mentioned name has no value. This is a required parameter. This is an application error.
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.
Explanation	The reaper thread removes servlets that have been inactive for longer than the reaper inactive limit.
Explanation	The reaper thread removes the mappings for jsps and other extensions that have been inactive longer the the reaper inactive limit.
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.
Explanation	There is no servlet definition for the servlet mapping.
Explanation	There must be at least one async timer thread.
Explanation	The requested servlet is on the block list provided by the custom property com.ibm.ws.webcontainer.donotservebyclassname. This is an application error.
Explanation	The request must be of type multipart/form-data to be able to handle this method.
Explanation	The request path maps to a context root on a non-matching virtual host.
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.
Explanation	The request tried to access a forbidden resource.
Explanation	There was an error adding a virtual host alias because one already exists with the same pattern.
Explanation	There was an exception uploading the file.
Explanation	There was a problem invoking the specified error reporter.
Explanation	There was a problem retrieving the restricted cookie patterns from the configuration.
Explanation	There was no servlet mapping for the filter so it cannot be added. This is an application error.
Explanation	The same pattern was specified twice for the url patterns to deny for file serving.
Explanation	The servlet chain that has been defined can only handle HTTP requests. This is an application error.
Explanation	The servlet class name is null so the request cannot be handled.
Explanation	The servlet class was found to be corrupted. This is an application error.
Explanation	The ServletContainerInitializer specified by the Extension Point could not be initialized.
Explanation	The servlet destroy() method threw an exception. This is an application error.
Explanation	The servlet does not accept multipart requests.
Explanation	The servlet failed to initialize because an error occurred when a resource was injected.
Explanation	The servlet specification level supported by the application server.
Explanation	The Servlet specification states you can only call dispatch once per call to startAsync
Explanation	The Session registry is NULL possibly because the SessionManager did not start up correctly. Web applications WILL fail.
Explanation	The specified annotation helper could not be instantiated. This is a system error.
Explanation	The specified annotation helper has not been defined. This is a system error.
Explanation	The specified annotation helper is not of the expected type. This is a system error.
Explanation	The specified directory is not valid.
Explanation	The specified path is not a directory.
Explanation	The specified servlet has been unloaded after the destroy method has been called.
Explanation	The specified servlet is being unloaded from service.
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.
Explanation	The target threw an exception during initialization that was not caught by the user code. This is an application error.
Explanation	The variable argument servlet name parameter passed to FilterRegistration.addMappingForServletNames must be non-null and non-empty.
Explanation	The variable argument url-pattern parameter passed to FilterRegistration.addMappingForUrlPatterns must be non-null and non-empty.
Explanation	The variable argument url-pattern parameter passed to ServletRegistration.addMapping must be non-null and non-empty.
Explanation	The virtual host was not found. System action is required.
Explanation	The writer for this response has already been obtained. Use the existing writer. This is an application error.
Explanation	This error occurred when the web container tried to load an internal implementation class. This is a system error.
Explanation	This exception should never occur as the thread pools will queue up the work.
Explanation	This is an application error.
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.
Explanation	This is an internal system error and is probably caused by an earlier failure.
Explanation	This is an internal system error and is probably caused by an earlier failure. This is an application error.
Explanation	This is an unexpected internal error.
Explanation	This is a system error.
Explanation	This is a system error error.
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.
Explanation	Two web applications on the same virtual host share the same context root. This is an application error.
Explanation	Unable to locate Virtual Host defined to handle this request URI. System action is required.
Explanation	Uncaught exception created in servlet service method. This is an application error.
Explanation	Unexpected isUserInRole exception, returning of isUserInRole false.
Explanation	Unknown error related to the web container configuration.
Explanation	WebAppSecurityCollaborator. This is a system error.
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.
Explanation	Web Container is not initialized until an application has been installed. This is a system error.
Explanation	Web module is starting and being made available for service.
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.
Explanation	When scheduling a work item with an asynchronous beans work manager, workRejected may be called if an error happens starting the work item.
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.
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.
ExtensionFactory.[{0}].associated.with.patterns.[{1}]=SRVE0240I: Extension Factory [{0}] has been associated with patterns [{1}].
ExtensionFactory.[{0}].registered.successfully=SRVE0239I: Extension Factory [{0}] was registered successfully.
extension.processor.failed.to.initialize.in.factory=SRVE0280E: Extension processor failed to initialize in factory [{0}]: {1}
failed.to.create.temp.directory=SRVE0289E: Failed to create temp directory: {0}
Failed.to.initialize.webapp.{0}=SRVE0015E: Failure to initialize Web application {0}
failed.to.load.converter.properties=SRVE0156E: Failed to load converter.properties file {0}
failed.to.load.encoding.properties=SRVE0155E: Failed to load encoding.properties file {0}
failed.to.remove.webmodule=SRVE0314E: Failed to remove webmodule {0}: {1}
File.not.found=SRVE0190E: File not found: {0}
Filter.found.but.injection.failure=SRVE0320E: The [{0}] filter was found, but a resource injection failure has occurred.
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.
filtering.by.asterisk=SRVE0308E: Filtering by asterisk is not allowed.
Follow the instructions in the Information Center to add a new virtual host alias.
Forbidden.Web.Security.Exception=SRVE0218E: Forbidden: Web Security Exception
Format found for a request header is not valid.
Gather logs and contact IBM service.
Gather server logs and contact IBM service.
host.has.not.been.defined=SRVE0204E: The host {0} has not been defined
host.on.port.has.not.been.defined=SRVE0205E: The host {0} on port {1} has not been defined.
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.
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/ .
If this is not the desired behavior, update the property com.ibm.ws.webcontainer.donotservebyclassname.
Illegal.Argument:.{0}.is.not.a.directory.=SRVE0031E: Illegal Argument Exception: {0} is not a directory.
Illegal.Argument:.Bootstrap.File.Not.Found=SRVE0041E: Illegal Argument Exception: Bootstrap file not found
Illegal.Argument:.Invalid.Content.Length=SRVE0042E: Illegal Argument Exception: Invalid content length
Illegal.Argument:.Invalid.Date.Format=SRVE0053E: Illegal Argument Exception: Invalid date format
Illegal.Argument:.Invalid.Directory.Specified:.{0}=SRVE0061E: Illegal Argument Exception: Invalid directory specified: {0}
Illegal.Argument:.Invalid.Header.Format=SRVE0016E: Illegal Argument Exception: Invalid header format
Illegal.Argument:.Invalid.ObjectPool.Instantiated.=SRVE0109E: Illegal Argument Exception: Invalid ObjectPool instantiated.
Illegal.Argument:.Missing.flag.value=SRVE0108E: Illegal Argument Exception: Missing flag value
Illegal.Argument:.Missing.Resource.Bootstrap.Properties=SRVE0086E: Illegal Argument Exception: Missing resource bootstrap properties
Illegal.Argument:.ScriptName.must.be.the.first.part.of.the.URI=SRVE0103E: Illegal Argument Exception: ScriptName must be the first part of the URI
Illegal.Argument:.Trying.to.write.<.0.bytes=SRVE0121E: Illegal Argument Exception: Trying to write &lt; 0 bytes
Illegal.Argument.Trying.to.write.chars=SRVE0011E: Illegal Argument Exception: Trying to write < 0 chars
Illegal.Argument:.Unsupported.flag=SRVE0056E: Illegal Argument Exception: Unsupported flag
Illegal.from.included.servlet=SRVE0194E: Illegal from included servlet
illegal.servlet.mapping=SRVE0270E: Illegal servlet mapping encountered for servlet {0}.
Informational message {2} logged via ServletContext.log from application {0} with context root {1}.
Informational message {2} logged via ServletContext.log from application {0} with context root {1} and stack trace {3}.
init.exception.thrown.by.filter.at.startup=SRVE0321E: The [{0}] filter did not load during start up.
Install an application to initialize the webcontainer.
instantiate.collaborator.exception=SRVE0140E: Could not instantiate the security collaborator {0}
Internal exception.
Internal server error.
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.
Internal web container error.
Invalidation.Exception:.{0}.was.created=SRVE0126E: Invalidation Exception: {0} was created
Invalid.Content.Length=SRVE0080E: Invalid content length
invalid.count=SRVE0214E: invalid count
invalid.query.string=SRVE0318W: Invalid character in query string.
IO error encountered.
IO.Error=SRVE0120E: IO Error {0}
It is recommended to enable the object pool service.
jsp.processor.not.defined.skipping=SRVE0272W: JSP Processor not defined. Skipping : {0}
Listener.found.but.injection.failure=SRVE0322E: The [{0}] listener class was found, but a resource injection failure has occurred.
loading.web.module=SRVE0169I: Loading Web Module: {0}.
log.servlet.error.and.message=SRVE0294E: [Servlet Error]-[{0}]: {1}: {2}
log.servlet.error=SRVE0293E: [Servlet Error]-[{0}]: {1}
log.servlet.message=SRVE0292I: Servlet Message - [{0}]:.{1}
log.servlet.message.with.throwable=SRVE0296E: [{0}][{1}][Servlet.LOG]:.{2}:.{3}
Look in the error log to determine the root cause of this problem.
Make sure all required classes are placed in the folders/jars representing the class path
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.
Make sure the directory exists or that you are requesting the right directory.
Make sure the host name has been specified correctly and that the servlet host has been specified in virtualhosts.xml.
Make sure the requesting entity has the required privileges.
Make sure the servlet class file is available on the application class path.
Make sure your class path reflects all the classes you may be accessing
mapping.already.exists=SRVE0300E: Mapping already Exists [{0}][{1}]: {2}
mapping.for.directorybrowsingservlet.already.exists=SRVE0277W: Mapping for DirectoryBrowsingServlet already exists
Missing flag value.
Missing.required.initialization.parameter=SRVE0196E: Missing required initialization parameter: {0}
Modify the failing class to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet
Modify the failing servlet/JSP.
module.[{0}].successfully.bound.to.virtualhost.[{1}]=SRVE0250I: Web Module {0} has been bound to {1}.
need.to.add.a.new.virtual.host.alias=SRVE0317W: You may need to add a new virtual host alias of *:<your port> to the same virtual host that [{0}] is under.
No.Error.to.Report=SRVE0219I: No Error to Report
no.jsp.extension.handler.found=SRVE0269W: No Extension Processor found for handling JSPs
none
none.
non-HTTP.request.or.response=SRVE0215E: non-HTTP request or response
Null.Filter.Mapping=SRVE0307W: null mapping for filter. This may occur if you try to specify a * mapping on a pre-2.5 app.
Object.Pool.Disabled=SRVE0305W: ObjectPoolService is unavailable. SRTConnectionContext pooling disabled.
Only write buffers of size of 0 or greater.
OutputStream.already.obtained=SRVE0199E: OutputStream already obtained
Package name of resource does not match the compiled class file's package. This is an application error.
post.body.contains.less.bytes.than.specified=SRVE0216E: post body contains less bytes than specified by content-length
postInvoke.Security.Exception.=SRVE0138E: postInvoke Security Exception
preInvoke.Security.Exception.=SRVE0139E: Exception in Security preInvoke {0}
Problem encountered parsing servlet parameters.
Problem encountered rolling back the specified user transaction. This is an application error.
Problem invoking the specified error reporter.
Problem releasing a session.
property.configuration.change=SRVE0259W: The {0} property is now configurable only at the WebContainer level.
property.has.changed=SRVE0257W: The semantics for the {0} property on the transport have changed.
property.not.applicable=SRVE0258W: The {0} attribute under the transport no longer applies.
reaper.destroying.servlet.[{0}]=SRVE0246I: Reaper thread destroying servlet: [{0}].
Reaper processing is just a form of garbage collection.
reaper.removing.mapping.[{0}].for.servlet.[{1}]=SRVE0245I: Reaper thread removing mapping: [{0}] for servlet: [{0}].
reaper.thread.error=SRVE0247E: Error during reaper thread execution.
reaper.unloading.servlet.[{0}]=SRVE0244I: Reaper thread unloading servlet: [{0}].
reaper.with.interval.[{0}].limit.[{1}].started=SRVE0243I: Reaper thread interval: [{0}] and inactive limit:[{1}] started.
Re-compile the class and try again.
Recompile the servlet using only the classes in the application's runtime class path.
Re-compile the servlet with all required components placed in the class path.
Refer to the information center for more details.
Remove the duplicate mapping.
Remove the setBufferSize() call or move it to a position before the response commit.
Request encoding specified on the request is not valid. This is an application error.
request.matches.context.root=SRVE0316W: Request matches the context root [{0}] under the virtual host alias of [{1}].
request.processor.already.present.for.mapping=SRVE0281E: Request Processor already present for mapping: {0}
resource.path.has.to.start.with.slash=SRVE0238E: Resource paths should have a leading slash
Review application to determine cause of problem.
Review application to determine if both PrintWriter and OuputStream were obtained. Modify the failing servlet/JSP to only obtain one or the other.
Review logs to determine whether the specified encoding is a valid encoding.
Review the logs.
Review the message to determine the root cause of the problem.
Root.Error=SRVE0225I: Root Error-
Security problem encountered during request processing. This is a system error.
See reported error.
See the Error Page Exception for a description of the problem with the specified error page.
server.root.is.null=SRVE0287E: server.root is null
Serving.JSP.Not.Allowed=SRVE0221E: Serving contents of JSP files is not allowed.
Servlet could not find a required class needed to service the request. This is an application error.
Servlet.Could.not.find.required.servlet.class=SRVE0200E: Servlet [{0}]: Could not find required class - {1}
Servlet.found.but.corrupt=SRVE0202E: Servlet [{0}]: {1} was found, but is corrupted:
Servlet.found.but.injection.failure=SRVE0319E: For the [{0}] servlet, {1} servlet class was found, but a resource injection failure has occurred.
Servlet.has.become.temporarily.unavailable.for.service:.{0}=SRVE0095I: Servlet has become temporarily unavailable for service: {0}
Servlet is being destroyed after wait has timed out.
Servlet is still handling the request. Waiting for request to complete before calling destroy.
Servlet.not.a.servlet.class=SRVE0201E: Servlet [{0}]: not a servlet class
servlet.on.blocked.list.{0}=SRVE0309E: Servlet on the blocked list: {0}
servletrequestwrapper.is.not.an.instance.of.so.wrapped.logic.may.be.bypassed=SRVE0304E: ServletRequestWrapper [{0}] is not an instance of [{1}] so wrapped logic may be bypassed.
Servlet.unloaded:.{0}=SRVE0021I: Servlet unloaded: {0}
Servlet.unload.initiated:.{0}=SRVE0097I: Servlet unload initiated: {0}
Servlet.wait.for.destroy.timeout.has.expired,.destroy.will.be.forced:.{0}=SRVE0055I: Servlet wait for destroy time-out has expired, destroy will be forced: {0}
Servlet.was.found.but.is.missing.another.required.class=SRVE0203E: Servlet [{0}]: {1} was found, but is missing another required class.
Session.releaseSession().threw.an.unexpected.exception=SRVE0105E: An exception occurred in Session.releaseSession()
setbuffer.size.called.after.write=SRVE0157E: setBufferSize() called after first write to Output Stream/Writer
Set com.ibm.ws.webcontainer.disallowserveservletsbyclassname to true to block serving all classes by classname.
Set fileServingEnabled=false in the ibm-web-ext.xmi file which is under WEB-INF folder.
Some data has already been written to the stream, and hence the buffer size can no longer be controlled. This is an application error.
Specified servlet is temporarily unavailable.
SRVE
SRVE0
SRVE0011E: Illegal Argument Exception: Trying to write < 0 chars
SRVE0014E: Uncaught service() exception root cause {0}: {1}
SRVE0015E: Failure to initialize Web application {0}
SRVE0016E: Illegal Argument Exception: Invalid header format
SRVE0021I: Servlet unloaded: {0}
SRVE0031E: Illegal Argument Exception: {0} is not a directory.
SRVE0035E: WebAppSecurityCollaborator
SRVE0041E: Illegal Argument Exception: Bootstrap file not found
SRVE0042E: Illegal Argument Exception: Invalid content length
SRVE0053E: Illegal Argument Exception: Invalid date format
SRVE0055I: Servlet wait for destroy time-out has expired, destroy will be forced: {0}
SRVE0056E: Illegal Argument Exception: Unsupported flag
SRVE0058E: Did not realize destroy() exception created by servlet {0} in application {1}: {2}
SRVE0060E: Unable to bind host name [{0}] to servletHost [{1}]
SRVE0061E: Illegal Argument Exception: Invalid directory specified: {0}
SRVE0066I: Waiting for servlet to finish servicing requests: {0}
SRVE0068E: An exception was thrown by one of the service methods of the servlet [{0}] in application [{1}]. Exception created : [{2}]
SRVE0070E: Error initializing for next request
SRVE0080E: Invalid content length
SRVE0086E: Illegal Argument Exception: Missing resource bootstrap properties
SRVE0095I: Servlet has become temporarily unavailable for service: {0}
SRVE0096E: A session cannot be accessed. The session manager feature set has not been started.
SRVE0097I: Servlet unload initiated: {0}
SRVE0099E: Object Pool Exception: Class [{0}] could not be instantiated.
SRVE0100E: Uncaught init() exception created by servlet {0} in application {1}: {2}
SRVE0103E: Illegal Argument Exception: ScriptName must be the first part of the URI
SRVE0105E: An exception occurred in Session.releaseSession()
SRVE0108E: Illegal Argument Exception: Missing flag value
SRVE0109E: Illegal Argument Exception: Invalid ObjectPool instantiated.
SRVE0115E: Error occurred while invoking error reporter {0}
SRVE0120E: IO Error {0}
SRVE0121E: Illegal Argument Exception: Trying to write &lt; 0 bytes
SRVE0126E: Invalidation Exception: {0} was created
SRVE0133E: An error occurred while parsing parameters. {0}
SRVE0138E: postInvoke Security Exception
SRVE0139E: Exception in Security preInvoke {0}
SRVE0140E: Could not instantiate the security collaborator {0}
SRVE0155E: Failed to load encoding.properties file {0}
SRVE0156E: Failed to load converter.properties file {0}
SRVE0157E: setBufferSize() called after first write to Output Stream/Writer
SRVE0160E: Exception while rolling back UserTransaction: {0}
SRVE0161I: IBM WebSphere Application Server - Web Container. Copyright IBM Corp. 1998-2012
SRVE0162I: Servlet Specification Level: 3.0
SRVE0163I: Supported JSP Specification Level: 2.2
SRVE0164E: Web Application {0} uses the context root {1}, which is already in use by Web Application {2}. Web Application {3} will not be loaded.
SRVE0169I: Loading Web Module: {0}.
SRVE0180I: [{0}] [{1}] [Servlet.LOG]: {2}
SRVE0181I: [{0}] [{1}] [Servlet.LOG]: {2}: {3}
SRVE0185E: An error has occurred while processing request:
SRVE0186E: Can't set buffer size after data has been written to stream
SRVE0187E: Check your class path to ensure that all classes required by the servlet are present.
SRVE0188E: Class {0} does not implement servlet
SRVE0189E: Error occurred while finishing request
SRVE0190E: File not found: {0}
SRVE0194E: Illegal from included servlet
SRVE0196E: Missing required initialization parameter: {0}
SRVE0199E: OutputStream already obtained
SRVE0200E: Servlet [{0}]: Could not find required class - {1}
SRVE0201E: Servlet [{0}]: not a servlet class
SRVE0202E: Servlet [{0}]: {1} was found, but is corrupted:
SRVE0203E: Servlet [{0}]: {1} was found, but is missing another required class.
SRVE0204E: The host {0} has not been defined
SRVE0205E: The host {0} on port {1} has not been defined.
SRVE0206E: This error typically implies that the servlet was originally compiled with classes which cannot be located by the server.
SRVE0207E: Uncaught initialization exception created by servlet
SRVE0208E: Unsupported conversion
SRVE0209E: Writer already obtained
SRVE0210I: This problem can be debugged by recompiling the servlet using only the classes in the application's runtime class path
SRVE0211E: The class {0} could not be instantiated
SRVE0212E: class {0} not accessible
SRVE0213E: class not found
SRVE0214E: invalid count
SRVE0215E: non-HTTP request or response
SRVE0216E: post body contains less bytes than specified by content-length
SRVE0217E: {0} is not a valid class
SRVE0218E: Forbidden: Web Security Exception
SRVE0219I: No Error to Report
SRVE0220I: Wrapped Error-
SRVE0221E: Serving contents of JSP files is not allowed.
SRVE0223I: StackTrace:
SRVE0224I: Target Servlet:
SRVE0225I: Root Error-
SRVE0227E: Check that the class resides in the proper package directory.
SRVE0228E: Check that the classname has been defined in the server using the proper case and fully qualified package.
SRVE0229E: Check that the class was transferred to the filesystem using a binary transfer mode.
SRVE0230E: Check that the class was compiled using the proper case (as defined in the class definition).
SRVE0231E: Check that the class file was not renamed after it was compiled.
SRVE0232E: Internal Server Error. <br> Exception Message: [{0}]
SRVE0233E: Error Report
SRVE0234I: Application class path=[{0}]
SRVE0235E: [{0}] reported an error
SRVE0236E: Error occurred while invoking initialization collaborator on starting() call
SRVE0237E: Error occurred while invoking initialization collaborator on started() call
SRVE0238E: Resource paths should have a leading slash
SRVE0239I: Extension Factory [{0}] was registered successfully.
SRVE0240I: Extension Factory [{0}] has been associated with patterns [{1}].
SRVE0241I: Using [{0}] as the server root in getTempDirectory().
SRVE0242I: [{2}] [{1}] [{0}]: Initialization successful.
SRVE0243I: Reaper thread interval: [{0}] and inactive limit:[{1}] started.
SRVE0244I: Reaper thread unloading servlet: [{0}].
SRVE0245I: Reaper thread removing mapping: [{0}] for servlet: [{0}].
SRVE0246I: Reaper thread destroying servlet: [{0}].
SRVE0247E: Error during reaper thread execution.
SRVE0248I: Requests are currently being processed. Waiting up to 60 seconds before forcing filter destroy.
SRVE0249W: Application {0} has requested SyncToOSThread, but the server is not enabled for SyncToOSThread
SRVE0250I: Web Module {0} has been bound to {1}.
SRVE0251W: The thread pool configured under the web container is not being used.
SRVE0252W: Transports and Chains have been detected! The transports have been changed to use a new model. Use the migration utilities to migrate the transports to the new model. The thread pool configuration under the web container will not be used with these transports.
SRVE0253I: [{2}] [{1}] [{0}]: Destroy successful.
SRVE0254E: Failed to set request character encoding: [{0}].
SRVE0255E: A WebGroup/Virtual Host to handle {0} has not been defined.
SRVE0256E: Web Container has not been initialized.
SRVE0257W: The semantics for the {0} property on the transport have changed.
SRVE0258W: The {0} attribute under the transport no longer applies.
SRVE0259W: The {0} property is now configurable only at the web container level.
SRVE0260E: The server cannot use the error page specified for your application to handle the Original Exception printed below.
SRVE0261E: The annotation helper {0} has not been defined.
SRVE0262E: The annotation helper {0} is not of type com.ibm.wsspi.webcontainer.AnnotationHelper.
SRVE0263E: The annotation helper {0} cannot be instantiated.
SRVE0264E: Error occured while initializing Extension Factories: {0}
SRVE0265E: Error occured while notifying listeners of web application start: {0}
SRVE0266E: Error occured while initializing servlets: {0}
SRVE0267E: Error occured while initializing filters: {0}
SRVE0268E: Error obtaining Session Context for the web application: {0}
SRVE0269W: No Extension Processor found for handling JSPs
SRVE0270E: Illegal servlet mapping encountered for servlet {0}.
SRVE0271E: Uncaught init() exception created by servlet [{0}] in application [{1}]: {2}
SRVE0272W: JSP Processor not defined. Skipping : {0}
SRVE0273E: Error while initializing JSP as servlet [{0}] in application [{1}]: {1}
SRVE0274W: Error while adding servlet mapping for path-->{0}, wrapper-->{1}, application-->{2}.
SRVE0275E: Error while adding servlet mapping for servlet [{0}] in application [{1}]: {2}
SRVE0276E: Error while initializing Servlet [{0}]: {1}
SRVE0277W: Mapping for DirectoryBrowsingServlet already exists
SRVE0278E: Error while adding servlet mapping --> {0}.
SRVE0279E: Error occured while processing global listeners for the application {0}: {1}
SRVE0280E: Extension processor failed to initialize in factory [{0}]: {1}
SRVE0281E: Request Processor already present for mapping: {0}
SRVE0282E: Error occured while setting web application attribues: {0}
SRVE0283E: Exception caught while initializing context: {0}
SRVE0284E: Exception caught in notifyServletContextCreated: {0}
SRVE0285E: Exception caught while destroying context: {0}
SRVE0286E: Exception caught in notifyServletContextDestroyed: {0}
SRVE0287E: server.root is null
SRVE0288E: chown failed, tried to run command: [{0}] Exit Code: [{1}]
SRVE0289E: Failed to create temp directory: {0}
SRVE0290E: Unable to use specified temp directory: {0} read:{1} write:{2}
SRVE0291E: Unable to use default temp directory: {0} read:{1} write:{2}
SRVE0292I: Servlet Message - [{0}]:.{1}
SRVE0293E: [Servlet Error]-[{0}]: {1}
SRVE0294E: [Servlet Error]-[{0}]: {1}: {2}
SRVE0295E: Error reported: {0}
SRVE0296E: [{0}][{1}][Servlet.LOG]:.{2}:.{3}
SRVE0297E: Web Application {0} destroy encountered errors: {1}
SRVE0298E: Exception occured while creating wrapper for servlet [{0}]: {1}
SRVE0299E: Could not create wrapper for servlet [{0}]
SRVE0300E: Mapping already Exists [{0}][{1}]: {2}
SRVE0301I: Encountered problems while removing servlet {0}. Details: {1}
SRVE0302E: Error while adding static file processor: {0}
SRVE0303E: Servlet name for the servlet mapping {0} could not be found.
SRVE0304E: ServletRequestWrapper [{0}] is not an instance of [{1}] so wrapped logic may be bypassed.
SRVE0305W: ObjectPoolService is unavailable. SRTConnectionContext pooling disabled.
SRVE0306W: ARD is not enabled so an asynchronous include or insertFragment call will be synchronous.
SRVE0307W: null mapping for filter. This may occur if you try to specify a * mapping on a pre-2.5 app.
SRVE0308E: Filtering by asterisk is not allowed.
SRVE0309E: Servlet on the blocked list: {0}
SRVE0310E: There was an error in a custom property: {1}
SRVE0311E: There was an error in the transport: {0}
SRVE0312E: There was an adding while adding a channel: {0}
SRVE0313E: Error occured while migrating transport at port {0} to the corresponding chain: {1}
SRVE0314E: Failed to remove web module {0}: {1}
SRVE0315E: An execption occurred: {0}
SRVE0316W: Request matches the context root [{0}] under the virtual host alias of [{1}].
SRVE0317W: You may need to add a new virtual host alias of *:<your port> to the same virtual host that [{0}] is under.
SRVE0318W: Invalid character in query string.
SRVE0319E: For the [{0}] servlet, {1} servlet class was found, but a resource injection failure has occurred.
SRVE0320E: The [{0}] filter was found, but a resource injection failure has occurred.
SRVE0321E: The [{0}] filter did not load during start up.
SRVE0322E: The [{0}] listener class was found, but a resource injection failure has occurred.
SRVE0323I: The Asynchronous Request Dispatcher is not enabled. Requests sent through either the HttpQueueInboundDefault or the HttpQueueInboundDefaultSecure chain might not be properly handled.
SRVE0324W: Asynchronous Request Dispatcher is not enabled. Therefore, the HttpQueueInboundDefault and HttpQueueInboundDefaultSecure chains might not handle your requests properly .
SRVE0325E: Exceeding maximum parameters allowed per request {0} ,current {1} , cannot add more.
SRVE0326E: The maximum number of parameter key hashcode collisions allowed per request {0} has been exceeded.
SRVE8000W: Skipped class that failed to initialize for annotation scanning.
SRVE8001E: Attempted to add servlet dynamically after ServletContext initialization.
SRVE8002E: Attempted to add filter dynamically after ServletContext initialization.
SRVE8003E: Attempted to add a servlet mapping with the variable argument url pattern parameter set to null.
SRVE8004E: Attempted to add a servlet mapping with an empty variable argument url pattern parameter.
SRVE8005E: Attempted to add a filter mapping with the variable argument url pattern parameter set to null.
SRVE8006E: Attempted to add a filter mapping with an empty variable argument url pattern parameter.
SRVE8007E: Attempted to add a filter mapping with the variable argument servlet name parameter set to null.
SRVE8008E: Attempted to add a filter mapping with an empty variable argument servlet name parameter.
SRVE8009E: An unexpected internal server error occurred when initializing the target mappings.
SRVE8010E: The current request does not support asynchronous servlet processing.
SRVE8011E: This operation cannot be executed from a programmatically added listener. (Operation: {0} | Listener: {1} | Application: {2})
SRVE8012E: Error adding ServletContextListener
SRVE8013E: Not a valid listener to add programmatically
SRVE8014E: An exception occurred while creating the listener instance
SRVE8015E: An exception occurred while trying to add a listener of type {0}
SRVE8016E: The {0} annotation can not be applied to the class, {1}, because it extends the wrong super class
SRVE8017E: The class, {0}, can not specify both urlPatterns and value in the annotation
SRVE8018E: The class, {0}, did not have any patterns specified in the annotation
SRVE8019E: Class, {0}, with annotation did not have a valid name
SRVE8020E: Servlet does not accept multipart requests
SRVE8021E: The file being uploaded is too large.
SRVE8022E: The request is too large.
SRVE8023E: There was an exception uploading the file.
SRVE8024E: The request is not of type multipart/form-data.
SRVE8025E: An error or timeout occured while doing async servlet processing.
SRVE8026E: An exception occurred scheduling work related to async servlet processing.
SRVE8027E: An I/O related error has occurred during the processing of the given AsyncEvent.
SRVE8028W: An exception occured adding a mapping target for the default extension processor.
SRVE8029E: An IOException occured creating the Extended Document Root search path.
SRVE8030E: A ServletException occurred adding a servlet dynamically.
SRVE8031W: A problem finding class, {0}, during the scan for ServletContainerInitializer HandlesTypes for {1}.
SRVE8032W: A problem finding a HandlesTypes class during the scan of the ServletContainerInitializer, {0}, for {1}.
SRVE8033W: A problem occurred while initializing the application's ServletContainerInitializers.
SRVE8034E: Servlet [{0}]: {1} could not be loaded due to an IOException.
SRVE8035E: Servlet [{0}]: {1} could not be loaded due to an IllegalAccessException.
SRVE8036E: Servlet [{0}]: {1} could not be loaded due to an InstantiationException.
SRVE8037E: Exception processing reference data.
SRVE8038E: Trying to do startAsync after a complete.
SRVE8039E: The method startAsync was not called from within the context of a dispatch for this request
SRVE8040E: Cannot call startAsync multiple times within same dispatch.
SRVE8041E: trying to call dispatch twice for the same async operation
SRVE8042E: An internal error caused the reference context that enables injection to not be initialized properly.
SRVE8043E: An IOException occured searching jarFile [{1}] for fileName [{2}] {0}
SRVE8044E: The context has already been initialized. No updates are allowed to the session configuration.
SRVE8045E: Programmatic session configuration has been disabled on this server.
SRVE8046E: An error occurred while invoking a call to AsyncContext dispatch.
SRVE8047E: NumberFormatException for file size at which you switch to optimized file serving.
SRVE8048E: A mapping clash occurred when adding the url pattern [{0}]
SRVE8049E: An internal server error occurred destroying the servlet.
SRVE8050E: Place servlet class on classpath of the application server {0}, {1}: {2}.
SRVE8051E: An internal server error occurred unloading the servlet.
SRVE8052E: Logging ClassNotFoundException
SRVE8053E: A NumberFormatException occurred when trying to set the single thread model pool size.
SRVE8054E: A NumberFormatException occurred when trying to set the single thread model servlet maximum idle time.
SRVE8055E: An unexpected exception occurred flushng out the rest of the response data.
SRVE8056E: An unexpected exception occurred closing the output stream.
SRVE8057E: An unexpected exception occurred initializing the output stream.
SRVE8058E: Did not have access to delete the temporary directory
SRVE8059E: An unexpected exception occurred when trying to retrieve the session context
SRVE8060E: An unexpected exception occurred during resource injection.
SRVE8061E: Unable to invoke method --> [{0}] on class --> [{1}].
SRVE8062E: An unexpected exception occurred initializing the security collaborator.
SRVE8063E: An unexpected exception occurred initializing the login processor.
SRVE8064E: An unexpected exception occurred initializing the logout processor.
SRVE8065E: Unknown error related to the web container configuration.
SRVE8066E: An unexpected exception occurred adding the WebContainerService.
SRVE8067E: An unexpected exception occurred handling an extension point.
SRVE8068E: Could not remove the web module [{0}]
SRVE8069E: The Session registry is NULL.
SRVE8070E: An unexpected error occurred starting the web container channel chains.
SRVE8071E: Null web container config object.
SRVE8072E: Null virtual host config object.
SRVE8073E: Null web application configuration object.
SRVE8074E: Null web application object.
SRVE8075E: Null cache servlet object.
SRVE8076E: Null AsyncRequestDispatcherConfigImpl object.
SRVE8077E: Null web application config object.
SRVE8078E: Null servlet config object.
SRVE8079E: Null filter config object.
SRVE8080E: Unexpected isUserInRole exception, returning of isUserInRole false.
SRVE8081E: An unexpected internal server error occurred while adding a web application collaborator.
SRVE8082E: An unexpected internal server error occurred while adding the static file processor.
SRVE8083E: An unexpected internal server error occurred while registering web module MBean.
SRVE8084E: An unexpected internal server error occurred while populating the namespace. Application name: {0}, Exception : {1}.
SRVE8085E: An IOException was thrown from WebContainer's handleRequest method.
SRVE8086E: Invalid peer certificate.
SRVE8087E: Error creating PMI statistics instance.
SRVE8088E: Error removing PMI statistics instance.
SRVE8089E: Error creating PMI statistics group.
SRVE8090E: Error occurred while preparing the servlet wrapper for initialization.
SRVE8091W: Servlet {0} is currently unavailable: {1}
SRVE8092W: An exception occurred invoking the async error mechanism.
SRVE8093W: The servlet class name is null for the servlet named [{0}] so the request cannot be handled.
SRVE8094W: WARNING: Cannot set header. Response already committed.
SRVE8095W: workRejected was called for the runnable [{0}].
SRVE8096W: An exception occurred scheduling the runnable [{0}].
SRVE8097W: No url pattern or servlet name for filter mapping for filter named [{0}].
SRVE8098W: Unable to insert mapping for servlet named [{0}]. URL pattern is null.
SRVE8099W: The method restartWebApplication no longer does anything. Use the ApplicationManager MBean to start and restart an application.
SRVE8100W: VirtualHost alias already exists for this VirtualHost -->[{0}].
SRVE8101E: Response buffer corruption detected. Expected remaining={0}, actual={1}.
SRVE8102E: Illegal value for responsebuffersize custom property [{0}].
SRVE8103E: An internal server error occurred creating the channel object.
SRVE8104E: Internal Server Error. Exception Message: [{0}]
SRVE8105W: An error occurred retrieving the timer manager to kick of async servlet timeouts. Using default single-threaded timer.
SRVE8106W: An exception occurred invoking the async listeners.
SRVE8107W: The AsyncContext tried to schedule a timeout thread without cancelling the previous timeout.
SRVE8108W: Trying to set number of async timer threads to less than one.
SRVE8109W: Uncaught exception thrown by filter {0}: {1}
SRVE8110E: Could not initialize ServletContainerInitializer: Classname: [{0}].
SRVE8111E: The application, {0}, is trying to modify a cookie which matches a pattern in the restricted programmatic session cookies list [domain={1}, name={2}, path={3}].
SRVE8112W: There was a problem retrieving the restricted cookie patterns. No restrictions have been placed on the programmatic session configuration.
SRVE8113W: Unable to obtain a lock. Error processing has already been invoked by another thread.
SRVE8500W: A servlet named {0} can not be dynamically added because a servlet configuration with the same name already exists.
StackTrace=SRVE0223I: StackTrace:
Supply a leading slash before the path and try again.
Supply a value to the mentioned parameter.
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.
sync.tothread.not.set.for.server.[{0}]=SRVE0249W: Application {0} has requested SyncToOSThread, but the server is not enabled for SyncToOSThread
System action is required.
Target.Servlet=SRVE0224I: Target Servlet:
The {0} property can no longer be configured at the transport level and must be configured at the webcontainer level. System action is required.
The attempted operation cannot be performed in an included servlet/JSP (Refer to the Servlet specification). This is an application error.
=The class mentioned needs to implement javax.servlet.Servlet or extend one of javax.servlet.GenericServlet or javax.servlet.http.HttpServlet
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.
The desired path is already assigned in a servlet mapping. This is an application error.
The destroy() method of the target resource ran successfully and the target has been removed from service.
The filter did not load during startup.
The filter failed to initialize because an error occurred when a resource was injected.
The incoming request may be corrupted. This is an application error.
The init() method of the target resource ran successfully and the target has been places into service.
The JSP specification level supported by the application server.
The listener failed to initialize because an error occured when a resource was injected.
The mentioned file was not found. This is an application error.
The object pool service improves the performance of the webcontainer, but it has been disabled. This is a system error.
The parameter with the mentioned name has no value. This is a required parameter. This is an application error.
The reaper thread removes servlets that have been inactive for longer than the reaper inactive limit.
The reaper thread removes the mappings for jsps and other extensions that have been inactive longer the the reaper inactive limit.
There exists a ThreadPool configuration under the webcontainer. Any changes made to this configuration item will not result in changes in the system.
The requested servlet is on the block list provided by the custom property com.ibm.ws.webcontainer.donotservebyclassname. This is an application error.
The request path maps to a context root on a non-matching virtual host.
The request tried to access a forbidden resource.
There was no servlet mapping for the filter so it cannot be added. This is an application error.
The servlet chain that has been defined can only handle HTTP requests. This is an application error.
The servlet class was found to be corrupted. This is an application error.
The servlet failed to initialize because an error occurred when a resource was injected.
The servlet specification level supported by the application server.
The specified annotation helper could not be instantiated. This is a system error.
The specified annotation helper has not been defined. This is a system error.
The specified annotation helper is not of the expected type. This is a system error.
The specified directory is not valid.
The specified path is not a directory.
The specified servlet has been unloaded after the destroy method has been called.
The specified servlet is being unloaded from service.
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.
The target threw an exception during initialization that was not caught by the user code. This is an application error.
The virtual host was not found. System action is required.
The writer for this response has already been obtained. Use the existing writer. This is an application error.
This.error.implies.servlet.was.originally.compiled.with.classes.which.cannot.be.located.by.server=SRVE0206E: This error typically implies that the servlet was originally compiled with classes which cannot be located by the server.
This error occurred when the webcontainer tried to load an internal implementation class. This is a system error.
This is an application error.
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.
This is an internal system error and is probably caused by an earlier failure.
This is an internal system error and is probably caused by an earlier failure. This is an application error.
This is a system error.
This is a system error error.
threadpool.not.used=SRVE0251W: The threadpool configured under the webcontainer is not being used.
transport.error=SRVE0311E: There was an error in the transport: {0}
transport.migration.error=SRVE0313E: Error occured while migrating transport at port {0} to the corresponding chain: {1}
transports.detected=SRVE0252W: Transports and Chains have been detected! The transports have been changed to use a new model. Use the migration utilities to migrate the transports to the new model. The threadpool configuration under the webcontainer will not be used with these transports.
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.
Two web applications on the same virtual host share the same context root. This is an application error.
Unable.to.bind.hostname.[{0}].to.servletHost.[{1}]=SRVE0060E: Unable to bind host name [{0}] to servletHost [{1}]
Unable to locate Virtual Host defined to handle this request URI. System action is required.
unable.to.use.default.temp.directory=SRVE0291E: Unable to use default temp directory: {0} read:{1} write:{2}
unable.to.use.specified.temp.directory=SRVE0290E: Unable to use specified temp directory: {0} read:{1} write:{2}
Uncaught.destroy().exception.thrown.by.servlet.{0}:.{2}=SRVE0058E: Did not realize destroy() exception created by servlet {0} in application {1}: {2}
Uncaught exception created in one of the service methods of the servlet. This is an application error.
Uncaught exception created in servlet service method. This is an application error.
Uncaught.init().exception.thrown.by.servlet.{0}:.{2}=SRVE0100E: Uncaught init() exception created by servlet {0} in application {1}: {2}
uncaught.init.exception.thrown.by.servlet=SRVE0271E: Uncaught init() exception created by servlet [{0}] in application [{1}]: {2}
Uncaught.initialization.exception.thrown.by.servlet=SRVE0207E: Uncaught initialization exception created by servlet
Uncaught.service().exception.root.cause.{0}:.{1}=SRVE0014E: Uncaught service() exception root cause {0}: {1}
Uncaught.service().exception.thrown.by.servlet.{0}:.{2}=SRVE0068E: Uncaught exception created in one of the service methods of the servlet {0} in application {1}. Exception created : {2}
Unsupported.conversion=SRVE0208E: Unsupported conversion
unsupported.request.encoding.[{0}]=SRVE0254E: Failed to set request character encoding: [{0}].
usertransaction.rollback.exception=SRVE0160E: Exception while rolling back UserTransaction: {0}
Use the migration utilities to migrate your configuration model from the transports to the new channel chains.
Using.[{0}].as.server.root=SRVE0241I: Using [{0}] as the server root in getTempDirectory().
Varies by root cause.
Varies depending on reported root cause.
Varies with root cause.
Verify that the injected resources exist and are accessible to the filter.
Verify that the injected resources exist and are accessible to the listener. To re-initialize the listener, restart the listener application.
Verify that the injected resources exist and are accessible to the servlet.
Verify the class exists within the application.
Verify the client is sending the full request.
Verify the custom property is correct
Verify the mapping is valid.
Wait and retry operation. Servlet might have been removed from service by server administrator.
Waiting.servlet.to.finish.servicing.requests:.{0}=SRVE0066I: Waiting for servlet to finish servicing requests: {0}
waiting.to.destroy.filter.[{0}]=SRVE0248I: Requests are currently being processed. Waiting up to 60 seconds before forcing filter destroy.
WebApp.destroy.encountered.errors=SRVE0297E: WebApp {0} destroy encountered errors: {1}
WebAppSecurityCollaborator=SRVE0035E: WebAppSecurityCollaborator
WebAppSecurityCollaborator. This is a system error.
web.container.copyright=SRVE0161I: IBM WebSphere Application Server - Web Container. Copyright IBM Corp. 1998-2008
WebContainer expects a wrapped request object to be an instance of a class of which it is not. This is an application error.
WebContainer is not initialized until an application has been installed. This is a system error.
web.container.jsp.spec.level=SRVE0163I: Supported JSP Specification Level: 2.1
webcontainer.not.initialized=SRVE0256E: WebContainer has not been initialized.
web.container.servlet.spec.level=SRVE0162I: Servlet Specification Level: 2.5
Web.Group.VHost.Not.Found=SRVE0255E: A WebGroup/Virtual Host to handle {0} has not been defined.
WebModule is starting and being made available for service.
Wrapped.Error=SRVE0220I: Wrapped Error-
Writer.already.obtained=SRVE0209E: Writer already obtained