Bug report for Tomcat 7 [2018/09/02]

2018-09-02 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 9 [2018/09/02]

2018-09-02 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat 8 [2018/09/02]

2018-09-02 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Connectors [2018/09/02]

2018-09-02 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Modules [2018/09/02]

2018-09-02 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Tomcat Native [2018/09/02]

2018-09-02 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for Taglibs [2018/09/02]

2018-09-02 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 62670] driverManagerProtection in JreMemoryLeakPreventionListener results in java.sql.SQLException: No suitable driver found

2018-09-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62670 --- Comment #1 from Michael Osipov <1983-01...@gmx.net> --- A JDBC driver should never be placed in WEB-INF/lib/. So in this case it would be an invalid issue. The other one might be misuse. -- You are receiving this mail because: You are the

[Bug 62670] driverManagerProtection in JreMemoryLeakPreventionListener results in java.sql.SQLException: No suitable driver found

2018-09-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62670 --- Comment #3 from Michael Osipov <1983-01...@gmx.net> --- (In reply to Mark Thomas from comment #2) > (In reply to Michael Osipov from comment #1) > > A JDBC driver should never be placed in WEB-INF/lib/. > > Of course it can. Such use is

[Bug 62670] driverManagerProtection in JreMemoryLeakPreventionListener results in java.sql.SQLException: No suitable driver found

2018-09-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62670 --- Comment #2 from Mark Thomas --- (In reply to Michael Osipov from comment #1) > A JDBC driver should never be placed in WEB-INF/lib/. Of course it can. Such use is perfectly valid. -- You are receiving this mail because: You are the

[Bug 62670] driverManagerProtection in JreMemoryLeakPreventionListener results in java.sql.SQLException: No suitable driver found

2018-09-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62670 --- Comment #6 from Mark Thomas --- It is a class loader issue. When the service loader executes it uses the bootstrap class loader which does not include $CATALINA_HOME/lib I'm not sure if this is something that has changed in the JRE or a

[Bug 62670] driverManagerProtection in JreMemoryLeakPreventionListener results in java.sql.SQLException: No suitable driver found

2018-09-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62670 --- Comment #4 from Mark Thomas --- This is getting rather off-topic for this bug. I don't see anything in that guidance that needs changing. If you have suggested edits, I suggest you take them to the dev@ for the community to discuss them.

svn commit: r1839887 - in /tomcat/jk/trunk/xdocs: index.xml news/20180301.xml

2018-09-02 Thread markt
Author: markt Date: Sun Sep 2 17:03:14 2018 New Revision: 1839887 URL: http://svn.apache.org/viewvc?rev=1839887=rev Log: Update news for 1.2.44 release Modified: tomcat/jk/trunk/xdocs/index.xml tomcat/jk/trunk/xdocs/news/20180301.xml Modified: tomcat/jk/trunk/xdocs/index.xml URL:

svn commit: r1839888 - in /tomcat/site/trunk: docs/connectors-doc/ docs/connectors-doc/common_howto/ docs/connectors-doc/common_howto/printer/ docs/connectors-doc/miscellaneous/ docs/connectors-doc/mi

2018-09-02 Thread markt
Author: markt Date: Sun Sep 2 17:04:51 2018 New Revision: 1839888 URL: http://svn.apache.org/viewvc?rev=1839888=rev Log: UPdate site for JK 1.2.44 release Modified: tomcat/site/trunk/docs/connectors-doc/common_howto/loadbalancers.html

svn commit: r1839889 - in /tomcat/site/trunk/docs: download-connectors.html index.html oldnews.html

2018-09-02 Thread markt
Author: markt Date: Sun Sep 2 17:10:46 2018 New Revision: 1839889 URL: http://svn.apache.org/viewvc?rev=1839889=rev Log: Missed changes Modified: tomcat/site/trunk/docs/download-connectors.html tomcat/site/trunk/docs/index.html tomcat/site/trunk/docs/oldnews.html Modified:

[ANN] Apache Tomcat Connectors 1.2.44 released

2018-09-02 Thread Mark Thomas
The Apache Tomcat Project is proud to announce the release of version 1.2.44 of the Apache Tomcat Connectors. This version fixes a number of bugs found in previous releases. Full details of these changes and new features, are available in the Apache Tomcat Connectors changelog:

svn commit: r29094 - in /release/tomcat/tomcat-connectors/jk: ./ binaries/windows/ binaries/windows/symbols/

2018-09-02 Thread markt
Author: markt Date: Sun Sep 2 17:13:13 2018 New Revision: 29094 Log: Drop JK 1.2.43 from mirrors Removed: release/tomcat/tomcat-connectors/jk/binaries/windows/symbols/tomcat-connectors-1.2.43-windows-i386-symbols.zip

[Bug 62670] driverManagerProtection in JreMemoryLeakPreventionListener results in java.sql.SQLException: No suitable driver found

2018-09-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62670 --- Comment #5 from Mark Thomas --- Getting back to the original bug report... The behaviour described is expected when a JDBC driver is packaged in WEB-INF/lib. The behaviour (and explanation for it) is documented here: