https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
Mark Thomas changed:
What|Removed |Added
OS||All
Version|9.0.52
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
patrickzeitz changed:
What|Removed |Added
Version|9.0.50 |9.0.52
OS|All
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
Thomas Hoffmann changed:
What|Removed |Added
CC||Thomas.Hoffmann@speed4trade
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #29 from Roman ---
Thanks for the explanation and the fix!
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #27 from Roman ---
It would also be interesting what makes this environment so special that the
issue is so hard to reproduce.
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #26 from Roman ---
With v9.0.51-171a2cd, I can no longer reproduce the problem (with NIO+APR).
Very well done, thank you!
Out of curiosity, what was the fix? Is there a git commit that would show the
necessary changes?
Again, thank
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #25 from Mark Thomas ---
I think this is fixed. Please test v9.0.51-171a2cd and report back. Debug
logging has been removed. You can removed any additional debug log settings
from logging.properties.
--
You are receiving this mail
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #24 from Roman ---
Sounds great!
I have attached of the second run. This time, it blocked the very first time.
The second time, it worked normally.
Unfortunatelly, we are using our own log manager and thus I am not sure whether
we c
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #23 from Roman ---
Created attachment 37956
--> https://bz.apache.org/bugzilla/attachment.cgi?id=37956&action=edit
Logs of v2, with screenshot of cURL/Log-Tail when it blocked
--
You are receiving this mail because:
You are the
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #22 from Mark Thomas ---
I have been able to recreate something locally that may well be the same issue
you are seeing. The v2 logs should confirm it. I'm working on a fix.
--
You are receiving this mail because:
You are the assig
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #21 from Mark Thomas ---
Thanks for running the test. It is likely that the issue was harder to
reproduce due to the additional logging.
You appear to be using a non-default log format. It would be helpful if the
Thread name could
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #20 from Roman ---
I have attached the full logs of the test run with v1.
It took quite some tries to actually reproduce it, but I made a screenshot at
the time it happened so that you can correlate the blocking with timestamps in
t
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #19 from Roman ---
Created attachment 37955
--> https://bz.apache.org/bugzilla/attachment.cgi?id=37955&action=edit
Logs of v1, with screenshot of cURL/Log-Tail when it blocked
--
You are receiving this mail because:
You are the
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #18 from Roman ---
One more thing: I did a threaddump of the server while the download was
blocking and did not see any Thread that was out of the ordinary. So, I would
assume that the writing to the socket may have already finished
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #17 from Roman ---
Ok, I will do this tomorrow.
Thanks for your help!
In the meantime, this is the Java version we use:
Specification: Java Virtual Machine Specification 11 (Oracle Corporation)
Virtual Machine: OpenJDK 64-Bit Serv
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #16 from Mark Thomas ---
I haven't been able to recreate this issue locally. Also, the debug logs didn't
have much information on writes - which is where the problem appears to be.
Therefore, I think it is time to move to the custo
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #15 from Mark Thomas ---
Debug log aren't very helpful. If I am unable to recreate this, we may need to
start down the custom Tomcat build route.
Which version of Java are you using?
--
You are receiving this mail because:
You ar
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #14 from Roman ---
> That is an HTTP connector. ARe you sure you tested with HTTPS?
Yes, I just took the first exec thread name that I found in the threaddump.
Sorry for the confusion.
--
You are receiving this mail because:
You
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #13 from Mark Thomas ---
(In reply to Roman from comment #10)
> I tested with 9.0.46 and was not able to reproduce the problem.
> (Thread names: http-nio-8080-exec-*, APR on, NIO)
That is an HTTP connector. ARe you sure you tested
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #12 from Roman ---
For the latest tests, I have reduced the connection timeout to 30s (which might
be good to know when reading the log file).
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #11 from Roman ---
Created attachment 37953
--> https://bz.apache.org/bugzilla/attachment.cgi?id=37953&action=edit
Tomcat FINE log while the downloading was blocked
--
You are receiving this mail because:
You are the assignee fo
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #10 from Roman ---
I tested with 9.0.46 and was not able to reproduce the problem.
(Thread names: http-nio-8080-exec-*, APR on, NIO)
I will attach the log file containing the requested FINE output. The file only
contains log lines
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #9 from Mark Thomas ---
Thanks for all the information.
That you still see the issue with 9.0.48 means that the response buffer
flushing changes in 9.0.49 are not the root cause of this issue.
That the observation of the issue is
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #8 from Roman ---
And here are the answers for the other questions:
3. APR disabled (org.apache.catalina.core.AprLifecycleListener commented out)
Threads: https-jsse-nio-8443-exec-*
Not reproducible
4. APR enabled, NIO2 (replaced
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #7 from Roman ---
Update on question 1:
Yes, I can reproduce the problem with Tomcat 9.0.48.
To downgrade the server, I replaced
* lib/*
* bin/bootstrap.jar
* bin/commons-daemon.jar
* bin/tomcat9*.exe
* bin/tcnative-1.dll
--
You
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #6 from Roman ---
I will hopefully be able to answer your questions later today. This is
happening on a customer site and working remotely is quite...painful.
What I can answer at the moment:
1, 3, 4, 5. Will have to check later.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #5 from Mark Thomas ---
A few questions (there will be more depending on the answers to these):
1. Does this happen with Tomcat 9.0.48?
2. How often does the problem occur? 1 request in 5? 1 in 10? 1 in 20?
3. Does the problem st
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #4 from Roman ---
One other thing: how would the code be influenced by the connection timeout of
the server?
It's not that the client opens a new connection or something... it's just that
the server pauses sending the response. I wo
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #3 from Roman ---
Yes, absolutely. We even pulled the code out to a separate app to check it
individually.
My main point is that it works when using HTTP. And it is really a small code
and I would consider it to be ok.
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
--- Comment #2 from Michael Osipov ---
If the DefaultServlet is working via HTTPS then the error is in your code. Did
you check that?
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bz.apache.org/bugzilla/show_bug.cgi?id=65448
Roman changed:
What|Removed |Added
OS||All
--- Comment #1 from Roman ---
Important t
32 matches
Mail list logo
