[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690 --- Comment #8 from Boris Petrov --- Hi, thanks for the detailed answer. There is no intermediate HTTP/2 proxy. Before I open an issue somewhere, could you please explain me something. I'm not sure I fully understand what's going on but how can a JavaScript library manage the HTTP/2 frames at all? As I said above, we're using "jQuery File Upload" (https://github.com/blueimp/jQuery-File-Upload) which splits the file in 1 MB chunks. Then, I guess, they do the POST request. Isn't then splitting that request with its body a Chrome/Firefox responsibility? If by "client" you mean Chrome/Firefox... is it possible that both of them are so inefficient/not-clever? If you mean a JavaScript library - then I probably am missing something. Some insight would be appreciated. Thanks! -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
buildbot success in on tomcat-trunk
The Buildbot has detected a restored build on builder tomcat-trunk while building tomcat. Full details are available at: https://ci.apache.org/builders/tomcat-trunk/builds/4567 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: asf946_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' triggered this build Build Source Stamp: [branch master] 8f86f9264e13d296bc89fa82c41cdcfef259215a Blamelist: remm Build succeeded! Sincerely, -The Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch master updated: Fix typo (missing a on via)
This is an automated email from the ASF dual-hosted git repository. fschumacher pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/master by this push: new 6b125eb Fix typo (missing a on via) 6b125eb is described below commit 6b125eb8df2074bad094d0a8f090a59f0d6a692b Author: Felix Schumacher AuthorDate: Tue Aug 27 11:58:30 2019 +0200 Fix typo (missing a on via) --- webapps/docs/changelog.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index 976852c..64cf807 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -373,7 +373,7 @@ compatibility. (remm) -Fix typo in UTF-32LE charset name. Patch by zhanhb vi Github. +Fix typo in UTF-32LE charset name. Patch by zhanhb via Github. (fschumacher) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch master updated: Update to 9.0.24
This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/master by this push: new 8f86f92 Update to 9.0.24 8f86f92 is described below commit 8f86f9264e13d296bc89fa82c41cdcfef259215a Author: remm AuthorDate: Tue Aug 27 09:46:50 2019 +0200 Update to 9.0.24 --- res/tomcat-maven/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/res/tomcat-maven/pom.xml b/res/tomcat-maven/pom.xml index 158642c..0631adc 100644 --- a/res/tomcat-maven/pom.xml +++ b/res/tomcat-maven/pom.xml @@ -29,7 +29,7 @@ UTF-8 org.apache.catalina.startup.Tomcat -9.0.22 +9.0.24 - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63701] New: SSL initialize hangs with OpenSSL 1.1.1
https://bz.apache.org/bugzilla/show_bug.cgi?id=63701 Bug ID: 63701 Summary: SSL initialize hangs with OpenSSL 1.1.1 Product: Tomcat Native Version: 1.2.21 Hardware: PC Status: NEW Severity: major Priority: P2 Component: Library Assignee: dev@tomcat.apache.org Reporter: mt...@apache.org Target Milestone: --- Created attachment 36739 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36739=edit Patch using a new OpenSSL init API OpenSSL >= 1.1.0 uses new initialization concept by replacing all those initialization calls with single OPENSSL_init_ssl call. Tomcat native using OpenSSL 1.1.1 hangs inside initialize on Windows platforms. Using new API it works -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56021] SSL connector using windows-my keystore
https://bz.apache.org/bugzilla/show_bug.cgi?id=56021 --- Comment #5 from Martin Stenderup --- (In reply to Martin Stenderup from comment #4) It seems to be called "keystorePass" some versions of Tomcat 8. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] 02/02: Fix JSSE_OPTS quoting in catalina.bat
This is an automated email from the ASF dual-hosted git repository. fschumacher pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 07a2804b43eb1ed5c5e09e3fbf54b28aaa11ff58 Author: Felix Schumacher AuthorDate: Tue Aug 27 11:55:14 2019 +0200 Fix JSSE_OPTS quoting in catalina.bat Contributed by Peter Uhnak. Closes #196 on github --- webapps/docs/changelog.xml | 4 1 file changed, 4 insertions(+) diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index f3431f4..976852c 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -76,6 +76,10 @@ 62140: Additional usage documentation in comments for catalina.[bat|sh]. (markt) + +Fix JSSE_OPTS quoting in catalina.bat. +Contributed by Peter Uhnak. (fschumacher) + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GitHub] [tomcat] asfgit closed pull request #196: fix JSSE_OPTS quoting
asfgit closed pull request #196: fix JSSE_OPTS quoting URL: https://github.com/apache/tomcat/pull/196 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch master updated (8f86f92 -> 07a2804)
This is an automated email from the ASF dual-hosted git repository. fschumacher pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git. from 8f86f92 Update to 9.0.24 new 162dd79 fix JSSE_OPTS quoting new 07a2804 Fix JSSE_OPTS quoting in catalina.bat The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: bin/catalina.bat | 2 +- webapps/docs/changelog.xml | 4 2 files changed, 5 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] 01/02: fix JSSE_OPTS quoting
This is an automated email from the ASF dual-hosted git repository. fschumacher pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 162dd79f16daaafd49ea68231525cbb650216169 Author: Peter Uhnak AuthorDate: Mon Aug 26 11:31:43 2019 +0200 fix JSSE_OPTS quoting Part of #196 on github --- bin/catalina.bat | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/catalina.bat b/bin/catalina.bat index 982b23f..eaced8d 100755 --- a/bin/catalina.bat +++ b/bin/catalina.bat @@ -206,7 +206,7 @@ set "CLASSPATH=%CLASSPATH%;%CATALINA_HOME%\bin\tomcat-juli.jar" :juliClasspathDone if not "%JSSE_OPTS%" == "" goto gotJsseOpts -set JSSE_OPTS="-Djdk.tls.ephemeralDHKeySize=2048" +set "JSSE_OPTS=-Djdk.tls.ephemeralDHKeySize=2048" :gotJsseOpts set "JAVA_OPTS=%JAVA_OPTS% %JSSE_OPTS%" - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690 --- Comment #7 from Mark Thomas --- Take a look at the following lines in the log: Connection [1], Stream [7], Frame type [DATA], Flags [0], Payload size [...] It looks like there is some buffering going on. The first 6 data frames are 5x2852 bytes and 1x2124 bytes for a total of exactly 16k. The first 24 packets are 20x2852, 3x2124 and 1x2123 for a total of 64k-1. The 25th packet is 1 byte giving a total of 64k. A similar (but not completely identical pattern) follows for the rest of the upload. It looks like the library you are using has various internal buffers and what you are seeing (in terms of data packet size) is the result of interactions between those buffers (I'm assuming there is no HTTP/2 proxy between the client and Tomcat else things will get more complicated). Small HTTP/2 packets are inefficient. Lots of them are considered to be abusive and in some servers (not Tomcat) result in a DoS. Tomcat has expanded its overhead protection to protect against such abusive traffic. The default settings considers any non-final DATA frame of less than 1024 bytes abusive. The smaller the DATA frame, the more abusive it is considered. I'd recommend opening an issue against the library you are using as it could be argued it should be sending fewer, larger HTTP/2 frames. It could also be argued that Tomcat should use a lower overheadDataThreadhold. However, the counter argument is that a lower threshold is only required for inefficient clients. Where inefficient becomes abusive is an interesting question and the answer will vary from server to server. As I said, in Tomcat's case it is never abusive, only inefficient, but we want to encourage clients to be efficient. I'm leaning towards leaving the default as is for now but is is definitely something we should keep an eye on as more users pick up the latest 9.0.x and 8.5.x releases. If we see a lot of issues like this then we may need to review the default. I'll leave this open for now but I am leaning towards resolving it as some form of "not a Tomcat issue". -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
buildbot failure in on tomcat-trunk
The Buildbot has detected a new failure on builder tomcat-trunk while building tomcat. Full details are available at: https://ci.apache.org/builders/tomcat-trunk/builds/4568 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: asf946_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' triggered this build Build Source Stamp: [branch master] 6b125eb8df2074bad094d0a8f090a59f0d6a692b Blamelist: Felix Schumacher ,Peter Uhnak BUILD FAILED: failed compile_1 Sincerely, -The Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63625] Unable to start Tomcat 7.0.96 (stop by 0xc0000005)
https://bz.apache.org/bugzilla/show_bug.cgi?id=63625 --- Comment #16 from Manuel Conde --- Hi all. Not exactly the same bug, but related: Win XP 32 bit Java 6 32 bit Tomcat 7.0.96.exe Error on install when trying to create Tomcat7 service. If I try 7.0.94, all works fine. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GitHub] [tomcat] KangZhiDong opened a new pull request #197: Remove unuse catch exception
KangZhiDong opened a new pull request #197: Remove unuse catch exception URL: https://github.com/apache/tomcat/pull/197 Remove unuse catch exception This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690
--- Comment #9 from Christopher Schultz ---
(In reply to Mark Thomas from comment #7)
> Small HTTP/2 packets are inefficient. Lots of them are considered to be
> abusive and in some servers (not Tomcat) result in a DoS. Tomcat has
> expanded its overhead protection to protect against such abusive traffic.
> The default settings considers any non-final DATA frame of less than 1024
> bytes abusive. The smaller the DATA frame, the more abusive it is considered.
1024 might be too high for a default, but the good news is that the "abusive"
threshold can be changed (right?).
Imagine an endpoint that is supposed to receive messages from a smart phone
tracking a user's geographical location. Let's think about the kinds of packets
you'd maybe expect to get. Let's assume JSON for a moment and that there isn't
a huge amount of other BS in the application: it's just doing what you'd
expect. An update message might look like this:
{
"MessageType" : "LOC-Update",
"Timestamp" : "2019-08-27T23:02:00Z",
"Latitude" : 51.508107,
"Longitude" : -0.075938
}
Including the trailing newline, that message is a mere 128 bytes. Imagine
sending one of those messages per second per client (which is pretty chatty,
but hey there are lots of crappy mobile apps out there, aren't there). If I
were designing such a service, I would even arrange to have the messages be
even smaller. There's no need to have such verbose JSON. Property names could
be changed, or, if the data format is relatively simple and/or fixed, a JSON
object could be converted into a JSON array and the property names are removed
entirely. The message could be as short as:
["2019-08-27T23:02:00Z",51.508107,-0.075938]
That's a scant 44 bytes.
Not every application will be sending large documents around.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat-native] Tomcat native hangs in SSL.initialize with OpenSSL 1.1.1 (Windows)
OpenSSL >= 1.1.0 uses new initialization concept by replacing all those initialization calls with single OPENSSL_init_ssl call. I found out that calling OPENSSL_malloc_init() as first function with OpenSSL 1.1.1 causes hang in any further call to OpenSSL. Anyone observed the similar issue? I plan to change the initialize function for OpenSSL 1.1+ (cleanup as well) so it uses new API instead deprecated calls. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
