[Bug 63612] PooledConnection#connectUsingDriver, Thread.currentThread().getContextClassLoader() may be null

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63612 --- Comment #7 from clemens...@mysign.ch --- Thx Konstatin >I think that you can avoid this error if you put the >database driver into the same classloader where >tomcat-jdbc.jar was loaded from mariadb-connector.jar is indeed not in the same

[GitHub] [tomcat] michael-o opened a new pull request #186: BZ 63636: Context#findRoleMapping() never called in RealmBase#hasRole()

2019-08-06 Thread GitBox
michael-o opened a new pull request #186: BZ 63636: Context#findRoleMapping() never called in RealmBase#hasRole() URL: https://github.com/apache/tomcat/pull/186 Please have also an eye on the test. It passes as expected and it fails when I modify it, but I am not certain whether I have bui

[Bug 63612] PooledConnection#connectUsingDriver, Thread.currentThread().getContextClassLoader() may be null

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63612 --- Comment #8 from clemens...@mysign.ch --- looking into the logs of the "affected site" I guess to have made up a "common denominator" for the "the null TCCL in that thread". All callstacks "originate" from a parallelStream execution (java.ut

[Bug 63612] PooledConnection#connectUsingDriver, Thread.currentThread().getContextClassLoader() may be null

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63612 --- Comment #9 from Mark Thomas --- That is likely because of the fix to this memory leak: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8172726 The Fork/Join framework in the JRE does not play nicely with the per web application cl

[Bug 63641] New: Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 Bug ID: 63641 Summary: Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribu

[Bug 63641] Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.Sock

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 Michael Osipov changed: What|Removed |Added OS||All --- Comment #1 from Michael Osipo

[Bug 63641] Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.Sock

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 --- Comment #2 from William Fraser --- I'll test that this evening. This was just to highlight that Bug 62918 does not appear to be resolved in 8.5.40. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 63641] Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.Sock

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 --- Comment #3 from Mark Thomas --- Reference to previous bug? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubsc

[Bug 63641] Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.Sock

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 --- Comment #4 from William Fraser --- Yes, reference to previous bug with the same issue but was marked as resolved as of 8.5.36. -- You are receiving this mail because: You are the assignee for the bug. -

[Bug 63641] Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.Sock

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 --- Comment #5 from Mark Thomas --- And the previous bug number is ...? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: de

[Bug 63641] Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.Sock

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 --- Comment #6 from William Fraser --- Apologies, it is in the comment dated 2019-08-06 09:45:43 UTC Bug 62918 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 63641] Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.Sock

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 --- Comment #7 from Mark Thomas --- Thanks. I missed that. I'll take a look at this before the next release unless someone beats me to it. -- You are receiving this mail because: You are the assignee for the bug. -

[Bug 63641] Tomcat Manager Server Status Errors After updating from 8.5.19 to 8.5.40. javax.management.AttributeNotFoundException: Cannot find attribute maxThreads for org.apache.tomcat.util.net.Sock

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63641 --- Comment #8 from William Fraser --- Perfect, thank you very much. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-u

[Bug 63645] New: Why its so hard for Linux distro to use Tomcat server from IntelliJ?

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63645 Bug ID: 63645 Summary: Why its so hard for Linux distro to use Tomcat server from IntelliJ? Product: Tomcat 9 Version: 9.0.16 Hardware: PC OS: Linux

[Bug 63645] Why its so hard for Linux distro to use Tomcat server from IntelliJ?

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63645 --- Comment #1 from Pranav --- Created attachment 36708 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36708&action=edit Another problem -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 63645] Why its so hard for Linux distro to use Tomcat server from IntelliJ?

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63645 --- Comment #2 from Pranav --- Created attachment 36709 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36709&action=edit Tomcat is pointless -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 63645] Why its so hard for Linux distro to use Tomcat server from IntelliJ?

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63645 Pranav changed: What|Removed |Added Attachment #36709|Tomcat is pointless |corrupted photo upload. description|

[Bug 63645] Why its so hard for Linux distro to use Tomcat server from IntelliJ?

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63645 --- Comment #3 from Pranav --- Created attachment 36710 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36710&action=edit Tomcat is issue -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 63645] Why its so hard for Linux distro to use Tomcat server from IntelliJ?

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63645 Coty Sutherland changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 63645] Why its so hard for Linux distro to use Tomcat server from IntelliJ?

2019-08-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63645 --- Comment #5 from Emmanuel Bourg --- The Tomcat package in Debian/Ubuntu is tailored for production use, the files are owned by a dedicated user and by default the daemon has limited read/write access to the system. If you want to use Tomcat

[tomcat] branch BZ-63636/tomcat-8.5.x created (now 08e169e)

2019-08-06 Thread michaelo
This is an automated email from the ASF dual-hosted git repository. michaelo pushed a change to branch BZ-63636/tomcat-8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git. at 08e169e BZ 63636: Context#findRoleMapping() never called in RealmBase#hasRole() This branch inclu

[tomcat] 01/01: BZ 63636: Context#findRoleMapping() never called in RealmBase#hasRole()

2019-08-06 Thread michaelo
This is an automated email from the ASF dual-hosted git repository. michaelo pushed a commit to branch BZ-63636/tomcat-8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 08e169e304ae9b010b69846b077344467b3b0457 Author: Michael Osipov AuthorDate: Mon Aug 5 21:32:58 2019 +02

Proposal: use Files.move instead of File.renameTo in FarmWarDeployer

2019-08-06 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, Someone recently had a problem where the FarmWarDeployer wouldn't work on a secondary node because File.renameTo was failing -- likely due to the underlying Java/OS refusing to re-name a file across filesystems. I propose that we switch to usi