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 #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 #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
Pingvin235 opened a new pull request #434:
URL: https://github.com/apache/tomcat/pull/434
Greetings to All,
the proposed fix makes optional taking requests parameters for internal
requests.
Which produced when using JSTL directives `
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
markt-asf commented on pull request #434:
URL: https://github.com/apache/tomcat/pull/434#issuecomment-879789821
Such an option would be in direct violation of the Servlet specification.
That makes me very hesitant to agree to such a change. The Servlet
specification already states that the
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 #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 #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 #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 #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 #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 #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
Pingvin235 commented on pull request #434:
URL: https://github.com/apache/tomcat/pull/434#issuecomment-880041227
Could you please point me the place in the specification, describing that
behavior? For 4.0 could found only section 9.3 regarding includes, but didn't
notice anything about par
Pingvin235 commented on pull request #434:
URL: https://github.com/apache/tomcat/pull/434#issuecomment-880042757
> Regarding the implementation, I am -1 on the proposed implementation as it
is based on an environment variable. If it were implemented, It would need to
be a per context confi
markt-asf commented on pull request #434:
URL: https://github.com/apache/tomcat/pull/434#issuecomment-880066207
You want the last paragraph of section 9.1.1. A RequestDispatcher is what
performs the include or forward.
--
This is an automated message from the Apache Git Service.
To respo
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 #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
Pingvin235 commented on pull request #434:
URL: https://github.com/apache/tomcat/pull/434#issuecomment-880204596
Thanks for pointing. Assuming this is the conflicting part:
"Parameters specified in the query string used to create the
RequestDispatcher take precedence over other param
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 #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
21 matches
Mail list logo
