You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2021/09/14 19:08:22 UTC
[Bug 65571] New: ClientAbortException in Tomcat 9.0.50 and 9.0.52
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
Bug ID: 65571
Summary: ClientAbortException in Tomcat 9.0.50 and 9.0.52
Product: Tomcat 9
Version: 9.0.50
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Util
Assignee: dev@tomcat.apache.org
Reporter: sutharvismay@gmail.com
Target Milestone: -----
Hi, I am getting below exception when I upgrade to 9.0.50 or 9.0.52.
I have looked at this bug https://bz.apache.org/bugzilla/show_bug.cgi?id=65368
I wonder if the fix is also needed on the server side too.
Also, If I revert back to 9.0.48 then I'm not seeing this exception.
Caused by: java.io.IOException: Unable to wrap data, invalid status [CLOSED]
at org.apache.tomcat.util.net.SecureNioChannel.write(SecureNioChannel.java:819)
~[tomcat-coyote.jar:9.0.50]
at
org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioEndpoint.java:1364)
~[tomcat-coyote.jar:9.0.50]
at
org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapperBase.java:766)
~[tomcat-coyote.jar:9.0.50]
at
org.apache.tomcat.util.net.SocketWrapperBase.flushBlocking(SocketWrapperBase.java:719)
~[tomcat-coyote.jar:9.0.50]
at
org.apache.tomcat.util.net.SocketWrapperBase.flush(SocketWrapperBase.java:709)
~[tomcat-coyote.jar:9.0.50]
at
org.apache.coyote.http11.Http11OutputBuffer$SocketOutputBuffer.flush(Http11OutputBuffer.java:573)
~[tomcat-coyote.jar:9.0.50]
at
org.apache.coyote.http11.filters.IdentityOutputFilter.flush(IdentityOutputFilter.java:117)
~[tomcat-coyote.jar:9.0.50]
at
org.apache.coyote.http11.Http11OutputBuffer.flush(Http11OutputBuffer.java:221)
~[tomcat-coyote.jar:9.0.50]
at org.apache.coyote.http11.Http11Processor.flush(Http11Processor.java:1205)
~[tomcat-coyote.jar:9.0.50]
at org.apache.coyote.AbstractProcessor.action(AbstractProcessor.java:402)
~[tomcat-coyote.jar:9.0.50]
at org.apache.coyote.Response.action(Response.java:209)
~[tomcat-coyote.jar:9.0.50]
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:306)
~[catalina.jar:9.0.50]
Regards,
Vismay
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65571] ClientAbortException in Tomcat 9.0.50 and 9.0.52
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
--- Comment #2 from sutharvismay@gmail.com ---
I'm working on reproducing this behavior. I have a following question.
https://github.com/apache/tomcat/blob/main/java/org/apache/tomcat/util/net/SecureNioChannel.java#L794
This line check for whether line is closed or not. Shouldn't we receive
IOException for closing string and not wrap fail string. As per the stack trace
we had status is CLOSED.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65571] ClientAbortException in Tomcat 9.0.50 and 9.0.52
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
(In reply to sutharvismay from comment #2)
> Shouldn't we receive
> IOException for closing string and not wrap fail string. As per the stack
> trace we had status is CLOSED.
No. The closing and closed flags track the status of a normal, server initiated
close. You are seeing the result of what looks like an unexpected - possibly
client initiated - close.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65571] ClientAbortException in Tomcat 9.0.50 and 9.0.52
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
--- Comment #6 from Mark Thomas <ma...@apache.org> ---
It has now been six months since this report was opened and none of the
information requested in comment #1 has been provided. Therefore, I intend to
resolve this issue as WONTFIX when I next review the open bugs prior to a
release.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65571] ClientAbortException in Tomcat 9.0.50 and 9.0.52
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
--- Comment #4 from Mark Thomas <ma...@apache.org> ---
Ping. We still need the information listed in comment #1
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65571] ClientAbortException in Tomcat 9.0.50 and 9.0.52
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
There is not enough information provided in this report for the Tomcat
community to investigate.
As a minimum we need:
- the full stack trace
- a description of what triggered the issue
- the steps to reproduce this issue from a clean install of the latest 9.0.x
release (9.0.53 as I write this).
Without the above information this issue will eventually be resolved as
WONTFIX.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65571] ClientAbortException in Tomcat 9.0.50 and 9.0.52
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |WONTFIX
--- Comment #7 from Mark Thomas <ma...@apache.org> ---
Resolving as WONTFIX as per my previous comment.
Please feel free to re-open this issue once you have the steps to reproduce it
from a clean install of the latest version of a supported Tomcat branch.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 65571] ClientAbortException in Tomcat 9.0.50 and 9.0.52
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
--- Comment #5 from sutharvismay@gmail.com ---
I'm still working on reproducing this error. It's very important for us to
reproduce and report it to you.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org