[Bug 63767] install windows service, tomcat9 start crash.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63767 --- Comment #8 from 王化亮 <6900...@qq.com> --- thank you very much! -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail:

[tomcat] branch master updated: fix comment

2019-09-25 Thread kfujino
This is an automated email from the ASF dual-hosted git repository. kfujino 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 dd2faec fix comment dd2faec is described

[Bug 63771] A way to strip 'Secure' From the cookie

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63771 Mark Thomas changed: What|Removed |Added Resolution|--- |INVALID Status|NEW

[Bug 63771] New: A way to strip 'Secure' From the cookie

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63771 Bug ID: 63771 Summary: A way to strip 'Secure' From the cookie Product: Tomcat 8 Version: 8.5.46 Hardware: PC OS: Linux Status: NEW Severity:

[Bug 63767] install windows service, tomcat9 start crash.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63767 --- Comment #5 from Mark Thomas --- Installed Windows Update Agent 7.8.9200.16924 - no change. Installed 2019-09 Preview of Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4516069) - problem resolved. This does indeed

[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690 --- Comment #20 from Mark Thomas --- 9.0.26 fixed a typo in the attribute name. You want overheadDataThreshold in 9.0.26 onwards. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 63767] install windows service, tomcat9 start crash.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63767 --- Comment #4 from Mark Thomas --- I have been able to re-create this. Here are a few more details for the record en_windows_server_2012_vl_x64_dvd_917758.iso - via My Visual Studio - Standard install with GUI - UK locale - All other

[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690 --- Comment #19 from Boris Petrov --- Mark, I'm observing a similar behavior on 9.0.26. The socket is closed even when the `overheadDataThreadhold="0"` setting is set. Browser is Chromium 77.0.3865.90. I had to revert to 9.0.24 with that

Performance bottleneck in WebappClassLoaderBase

2019-09-25 Thread Gunnar Brand
Hello. Recently we received complaints from a customer about slow response times (45 seconds) every morning. Every morning starting a fresh session in the browser would require a long wait time for the first user, but once this hurdle had been taken everything seemed to work fine. We could

[Bug 63767] install windows service, tomcat9 start crash.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63767 --- Comment #6 from Mark Thomas --- Found it. A good demonstration of my lack of C coding skills. I failed to initialise a variable so it was non-NULL when I expected it to be NULL causing Commons Daemon to try and call a function that didn't

[Bug 63767] install windows service, tomcat9 start crash.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63767 --- Comment #7 from Mark Thomas --- Already reported against Commons Daemon as https://issues.apache.org/jira/browse/DAEMON-408 -- You are receiving this mail because: You are the assignee for the bug.

Re: Performance bottleneck in WebappClassLoaderBase

2019-09-25 Thread Mark Thomas
This is a question, to start with at least, for the users mailing list. Mark On 25/09/2019 11:46, Gunnar Brand wrote: > Hello. > >   > > Recently we received complaints from a customer about slow response > times (45 seconds) every morning. Every morning starting a fresh session > in the

[tomcat] branch master updated: Refacfor to (hopefully) aid fixing crash on shutdown

2019-09-25 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt 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 17890c3 Refacfor to (hopefully) aid fixing

buildbot failure in on tomcat-trunk

2019-09-25 Thread buildbot
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/4629 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: asf946_ubuntu Build Reason: The AnyBranchScheduler

Re: [Bug 61441] daemon.sh's auto-detection fails on linux system's where java is installed via an RPM

2019-09-25 Thread Felix Schumacher
Am 19.09.19 um 10:02 schrieb Mark Thomas: > On 19/09/2019 08:07, Felix Schumacher wrote: >> That is obviously spam. > When discussing spam please don't quote the material - particularly any > links - as getting the links published as many times as possible is the > aim of the spam. Will try to

[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690 --- Comment #21 from Boris Petrov --- Thanks for the tip, Mark. I'll try that tomorrow. But... is this setting still needed? I thought that Tomcat 9.0.26 would remove the need for custom configuration and would work out-of-the-box with Chrome

[tomcat] branch 7.0.x updated: Fix test failures with APR/native.

2019-09-25 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 7.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/7.0.x by this push: new 3ad2262 Fix test failures with APR/native.

[tomcat] branch master updated: Fix test failures with APR/native.

2019-09-25 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt 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 bfff085 Fix test failures with APR/native.

[tomcat] branch 8.5.x updated: Fix test failures with APR/native.

2019-09-25 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/8.5.x by this push: new 3aba970 Fix test failures with APR/native.

Re: [tomcat] branch master updated: Fix test failures with APR/native.

2019-09-25 Thread Mark Thomas
On 25/09/2019 21:39, ma...@apache.org wrote: > This is an automated email from the ASF dual-hosted git repository. > > markt 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

buildbot success in on tomcat-trunk

2019-09-25 Thread buildbot
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/4630 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: asf946_ubuntu Build Reason: The

[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690 --- Comment #22 from Mark Thomas --- 9.0.26 will handle the behaviour in the original trace. That doesn't mean there isn't more "unusual" behaviour that will trigger the issue. -- You are receiving this mail because: You are the assignee for

[Bug 63690] [HTTP/2] The socket [*] associated with this connection has been closed.

2019-09-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63690 --- Comment #23 from Boris Petrov --- Well, I'm not sure what exactly you mean, but if you need more stacktraces, here you go: ``` javax.ws.rs.ProcessingException: Failed to buffer the message content input stream. at