| Explanation | An exception was thrown from a ServletContainerInitializer while invoking the onStartup method. |
| Action | Review the Exception to determine the cause of the error. |
| Explanation | The servlet name is used in filter mapping, but its definition has not been defined. |
| Action | Define the servlet which is used in the servlet name filter mapping. |
| Explanation | A cookie name cannot be configured for multiple SameSite attribute values. The attribute is not added for the cookie. |
| Action | Check the deployment descriptor configuration to make sure the cookie name is configured for only one of the following SameSite attribute values: 'SameSiteCookies_Lax', 'SameSiteCookies_None', or 'SameSiteCookies_Strict'. |
| Explanation | A cookie name cannot be configured for multiple SameSite attribute values. This cookie name has already been identified as a duplicate. |
| Action | Check the deployment descriptor configuration to make sure the cookie name is configured for only one of the following SameSite attribute values: 'SameSiteCookies_Lax', 'SameSiteCookies_None', or 'SameSiteCookies_Strict'. |
| Explanation | The request URI has invalid path parameters, invalid dot segments, or improperly encoded characters. |
| Action | Verify that the request URI does not contain an invalid dot or path parameter combination or any improperly encoded characters. |
| Explanation | The number of files that are uploaded by the multipart/form-data request exceeded the set limit. |
| Action | Increase the maximum number of files that can be uploaded per request by setting the maxFileCount webContainer custom property in the server.xml file. The default value is 5000. For unlimited file upload, set the value to -1. |
| Explanation | When a response is committed, it cannot send a redirect. |
| Action | Verify the sendRedirect logic to make sure that the response is not committed, either manually or automatically, before the sendRedirect is called. |
| Explanation | The redirect location URL needs to be a relative or an absolute URL. |
| Action | Update the redirect location by specifying a URL value that is not empty. The URL can be either relative or absolute. |
| Explanation | The application tried to parse a null HTTP request query string or a null HTTP POST request body. |
| Action | The client must send a non-null HTTP request query string or a non-null HTTP POST request body. |
| Explanation | The variable argument ByteBuffer instance that is passed to the read or write API must not be null. |
| Action | Modify the application code to create a non-null ByteBuffer instance to pass to the InputStream or OutputStream operation. |
| Explanation | If the isReady API returns false, you cannot call a read or write method. |
| Action | Modify the application logic to make sure that the stream is ready for an InputStream or OutputStream operation. |
| Explanation | This is an application error. The name is null in either context getAttribute(), setAttribute(), getInitParameter(), or setInitParameter(). |
| Action | Update the attribute name, or initial parameter name, with a non-null value. |
| Explanation | Response encoding specified on the response is not valid. This is an application error. |
| Action | Review logs to determine whether the specified encoding is a valid encoding. |
| Explanation | The response has already been committed. |
| Action | Ensure that the response has not been committed before trailers are set. |
| Explanation | HTTP Trailers are only supported in HTTP 1.1 or higher. |
| Action | Ensure that HTTP 1.1 or higher is being used. |
| Explanation | Trailers are only supported if the Transfer-Encoding header value is "chunked". |
| Action | Ensure that the Transfer-Encoding header contains the "chunked" value. |