https://bz.apache.org/bugzilla/show_bug.cgi?id=63691
Bug ID: 63691
Summary: Add a no-op JarScanner
Product: Tomcat 9
Version: unspecified
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Hi Mark,
*JDK 13 is now in the Release Candidate Phase
*
Per the JDK 13 schedule [1], we are now in the Release Candidate phase.
The stabilization repository, jdk/jdk13, is open for P1 bug fixes per
the JDK Release Process (JEP 3) [2].
All changes require approval via the Fix-Request Process
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690
--- Comment #5 from Mark Thomas ---
Correct. Tx.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail:
https://bz.apache.org/bugzilla/show_bug.cgi?id=48392
--- Comment #10 from sophia ---
(In reply to gfernandes from comment #1)
> jdbc-pool version is: 1.0.7.1
You can correct that with another strategy to solve this problem. Our developer
team was facing the problem when they work on
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690
--- Comment #4 from Boris Petrov ---
Thank you for the support, Mark.
As I said, this happens with both the latest Chrome and Firefox, as well as
Firefox 47 (these are the three browsers I tested with). Only when using
HTTP/2. The client side
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690
--- Comment #3 from Mark Thomas ---
The request has triggered the overhead protection because it looks abusive
(small non-final DATA frame). Setting overheadDataThreadhold to zero will
disable the specific protection triggered.
A debug trace
