https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #31 from neeraj...@gmail.com ---
(In reply to Aurélien from comment #29)
> I have encountered a very similar issue on Tomcat 9.0.0.M1:
> - first "CoyoteAdapter.checkRecycled Encountered a non-recycled request and
> recycled it
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #30 from Mark Thomas ---
Yes, the original bug is fixed in all 8.5.x and 9.0.x releases. It doesn't
appear in the changelog because it was fixed before development of those
branches started.
--
You are receiving
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #29 from Aurélien ---
I have encountered a very similar issue on Tomcat 9.0.0.M1:
- first "CoyoteAdapter.checkRecycled Encountered a non-recycled request and
recycled it forcedly",
- then a lof of 400
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #28 from Mark Thomas ---
Fix back-ported to 7.0.x for 7.0.69 onwards and to 6.0.x for 6.0.46 onwards.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Alexander Malyshev changed:
What|Removed |Added
Status|NEEDINFO|NEW
---
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #25 from Alexander Malyshev ---
I will try to remember the whole stack trace of the first call to find out the
actual call path - as there are a lot of possible call paths to cancelledKey()
method.
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #24 from Alexander Malyshev ---
I got some new info here.
1) This issue is hardly reproducible with the logs because logging for each
request highly slows down my server and request rate drops. I removed logs
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #23 from Mark Thomas ---
Something to try (that would address the Upgrade + IOE issue above and any
similar issues) is to add this:
connections.remove(socket.getSocket());
to the start of:
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #22 from Alexander Malyshev ---
Oops.
Some incorrect info in last comment. It turns out I used both comet(implemented
using async servlets) and websocket. So call path with "if (state ==
SocketState.UPGRADING)
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #21 from Alexander Malyshev ---
Ok, I added some additional logs and here is what we have:
Feb 15, 2016 MSK 05:34:24.157 PM http-nio-135.60.87.68-443-exec-34
org.apache.coyote.http11.Http11NioProtocol
INFO:
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #20 from miro-ch ---
Hi everybody, we have exactly the same problem. We get every few hours "Error
parsing HTTP request header" and then we must restart tomcat. Does anyone have
a solution for this problem?
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Iztok changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #18
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Alexander Malyshev changed:
What|Removed |Added
Status|NEEDINFO|NEW
---
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #15 from Alexander Malyshev ---
Ok, finally I was able to reproduce it with logs.
I associated ID with each request object and I added logging to
AbstractHttp11Processor class to process() and recycle()
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #13 from Julie ---
(In reply to Alexander Malyshev from comment #12)
> Yes, I agree. For some reason I can easily reproduce it with clean tomcat
> 8.0.29, but once I add logging to it to investigate further - it
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #14 from Julie ---
I am seeing similar errors in my log under traffic. I am using tomcat 8.0.15
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #12 from Alexander Malyshev ---
Yes, I agree. For some reason I can easily reproduce it with clean tomcat
8.0.29, but once I add logging to it to investigate further - it disappears..
I'll be running more
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #8 from Mark Thomas ---
(In reply to Alexander Malyshev from comment #6)
> I don't think it's application bug.
All the evidence so far points to an application bug being more likely than a
Tomcat bug.
> The only
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #9 from Alexander Malyshev ---
Well, I don't see how NullPointer in Tomcat code can possibly be an application
bug.
I forgot about these two valves, but, again, they never store request/response
objects so they
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #10 from Christopher Schultz ---
(In reply to Alexander Malyshev from comment #9)
> Well, I don't see how NullPointer in Tomcat code can possibly be an
> application bug.
package com.your.code;
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #7 from Alexander Malyshev ---
Ok, It seems like the issue happens even with
org.apache.catalina.connector.RECYCLE_FACADES=true.
Following are the exceptions I got:
Nov 25, 2015 CST 06:10:52.115 PM
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #6 from Alexander Malyshev ---
I don't think it's application bug. During traffic testing only the following
requests are sent:
1) Requests to get static content. Fully processed by tomcat - only filters
apply.
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Mark Thomas changed:
What|Removed |Added
Summary|NullPointerException in |NullPointerException
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #5 from Mark Thomas ---
I've added the stack trace to the log message.
Initial impressions of this issue are an application bug along the lines of
retaining a reference to the response.
--
You are receiving
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #1 from Alexander Malyshev ---
After some more testing it turns out it's not related to async-supported tag.
It's just intermittent. Also, sometimes this one happens before below
exceptions:
Nov 24, 2015 CST
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #3 from Konstantin Kolinko ---
1)
> Nov 23, 2015 CST 08:34:58.115 PM org.apache.coyote.http11.Http11NioProcessor
> INFO: Error parsing HTTP request header
> Note: further occurrences of HTTP header parsing
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
--- Comment #2 from Alexander Malyshev ---
Note also that the amount of regular HTTP request during testing is not huge -
nearly 10-12 requests/second. Amount of websocket traffic is huge, but it does
not seem to affect
https://bz.apache.org/bugzilla/show_bug.cgi?id=58646
Alexander Malyshev changed:
What|Removed |Added
Priority|P2 |P3
--
You
32 matches
Mail list logo