Explanation | The incoming request might be badly formed or corrupted as a result of a client side application or network error. |
Action | Review the client side application or network to determine why the request was truncated. |
Explanation | The requested blocking write cannot be completed because nonblocking I/O has already started. |
Action | Review the application to determine where the blocking write was performed. For example this could be from a servlet after registering the WriteListener, or from a WriteListener which does a second write after calling the isReady() API. Once the blocking write is determined, change the application to ensure it is performed as part of the WriteListener and/or after calling isReady(). |
Explanation | An exception occurred during the application WriteListener onError() API. |
Action | Review the logs to determine the exception thrown from the application implementation of onError() API and how to address the problem. Note that if an I/O exception occurred, then the onError() API cannot write output. |
Explanation | Failed to create the HttpUpgradeHandler. |
Action | Check the FFDC logs for more details on the error. |
Explanation | The servlet-3.1 feature is not in use. It is possible that an earlier version of servlet is already in use. |
Action | Add the servlet-3.1 feature to your server.xml file. |
Explanation | You cannot start certain operations from a programmatically added listener because there is no configuration option to restrict their launch when they are defined in a Tag Library Descriptor (TLD). |
Action | Add the listener using an annotation or in the web.xml file to enable starting this method. |
Explanation | The variable argument passed to the setReadListener API must be a valid readListener object. |
Action | Modify the application code according to the error explanation. |
Explanation | The variable argument passed to the WriteListener API must be a valid writeListener object. |
Action | Modify the application code according to the error explanation. |
Explanation | You can set the ReadListener on the request only if async is started or the init method of an UpgradeHandler is called. |
Action | Modify the application code according to the error explanation. |
Explanation | You can set the WriteListener only on the request if async is started or the init method of an UpgradeHandler is called. |
Action | Modify the application code according to the error explanation. |
Explanation | The ReadListener cannot be set more than once. |
Action | Modify the application code according to the error explanation. |
Explanation | The WriteListener cannot be set more than once. |
Action | Modify the application code according to the error explanation. |
Explanation | If isReady returns false it is illegal to call a read method. |
Action | Modify the application code according to the error explanation. |
Explanation | The variable argument byte[] passed to the read or write API must not be null. |
Action | Modify the application code according to the error explanation. |
Explanation | Either variable arguments offset was negative, the length was negative, or the length was greater than byte[].length - offset. |
Action | Modify the application code and verify that the offset value that is provided to read or write API is not negative. Ensure that the length value provided to read API is not negative. Also ensure that the length value provided is greater than byte[] length minus offset value that is provided. |
Explanation | While setting the ReadListener, the listener attempts to read, which failed. |
Action | Review the JVM logs for the exception. |
Explanation | To change the session ID for a request, first ensure that the request being used has a session associated with it. |
Action | Modify the application code according to the error explanation. |
Explanation | From Servlet 3.1 AsyncContext.getRequest() and AsyncContext.getResponse() must throw an IllegalStateException if complete() or any of the dispatch() methods have been called in the asynchronous cycle. |
Action | Modify the application code according to the error explanation. |
Explanation | The write API on the OutputStream object and read API on the InputStream object state that an IOException might be thrown if the stream has been closed. |
Action | Modify the application code according to the error explanation. |