Using log4j under a security manager
All, See this SO thread: http://stackoverflow.com/questions/18147885/use-log4j-in-a-tomcat-with-security-manager ...and refer to the Tomcat 7 log4j instructions: http://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j ...for context. It looks like (the original) bin/tomcat-juli.jar is not given permissions in conf/catalina.policy to read bin/log4j.properties. So, if one follows the instructions for Tomcat/log4j from the link above, and runs under a security manager, the logging system will throw a SecurityException. Should we modify catalina.policy to allow bin/tomcat-juli.jar to read lib/log4j.properties (and possibly newer config files such as lib/log4j.xml), or should we add an instruction in the documentation for doing that? On the one hand, it might be nice if it "just worked" with fewer steps to follow. On the other hand, running such that read-access to conf/log4j.properties|xml when not needed could be considered a (very minor) security risk. Separately, in Tomcat's logging instructions, item #4 says that if you want to use log4j globally, you should put the new tomcat-juli.jar into the conf/ directory instead of bin/. There is no commentary about what to do with the original bin/tomcat-juli.jar... if I were following the instructions, I would leave the original in place, but that does not really sound appropriate to me. What is the proper technique to use log4j for both Tomcat and webapp logging? Thanks, -chris signature.asc Description: OpenPGP digital signature
[Bug 55442] New: EL Constructor throws exception
https://issues.apache.org/bugzilla/show_bug.cgi?id=55442
Bug ID: 55442
Summary: EL Constructor throws exception
Product: Tomcat 8
Version: trunk
Hardware: PC
OS: Mac OS X 10.4
Status: NEW
Severity: normal
Priority: P2
Component: EL
Assignee: dev@tomcat.apache.org
Reporter: dmik...@gopivotal.com
In the EL 3.0 Spec, section 1.22.3 "Constructor Reference" states "A class
name reference, followed by arguments in parenthesis, such as "Boolean(true)"
denotes the invocation of the constructor of the class with the supplied
arguments."
This leads me to believe that the following test should work:
@Test
public void testImport03() {
ELProcessor processor = new ELProcessor();
Object result =
processor.getValue("Integer('1000')",
Integer.class);
Assert.assertEquals(Integer.valueOf(1000), result);
}
Unfortunately, this fails with the following error.
javax.el.ELException: Function ':Integer' not found
at org.apache.el.parser.AstFunction.getValue(AstFunction.java:136)
at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:188)
at javax.el.ELProcessor.getValue(ELProcessor.java:45)
at
org.apache.el.parser.TestAstIdentifier.testImport03(TestAstIdentifier.java:53)
…
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
Re: Using log4j under a security manager
On Aug 17, 2013, at 7:36 AM, Christopher Schultz wrote: > All, > > See this SO thread: > http://stackoverflow.com/questions/18147885/use-log4j-in-a-tomcat-with-security-manager > > ...and refer to the Tomcat 7 log4j instructions: > > http://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j > > ...for context. > > It looks like (the original) bin/tomcat-juli.jar is not given > permissions in conf/catalina.policy to read bin/log4j.properties. So, if > one follows the instructions for Tomcat/log4j from the link above, and > runs under a security manager, the logging system will throw a > SecurityException. > > Should we modify catalina.policy to allow bin/tomcat-juli.jar to read > lib/log4j.properties (and possibly newer config files such as > lib/log4j.xml), or should we add an instruction in the documentation for > doing that? And log4j2.xml. That's the new one. However, I actually think documentation is what's needed here. I favor just doing that over adding a default allowance. > On the one hand, it might be nice if it "just worked" with fewer steps > to follow. On the other hand, running such that read-access to > conf/log4j.properties|xml when not needed could be considered a (very > minor) security risk. > > Separately, in Tomcat's logging instructions, item #4 says that if you > want to use log4j globally, you should put the new tomcat-juli.jar into > the conf/ directory instead of bin/. There is no commentary about what > to do with the original bin/tomcat-juli.jar... if I were following the > instructions, I would leave the original in place, but that does not > really sound appropriate to me. What is the proper technique to use > log4j for both Tomcat and webapp logging? > > Thanks, > -chris > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump]: Project jakarta-tomcat-jasper_tc5 (in module jakarta-tomcat-jasper_tc5) failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project jakarta-tomcat-jasper_tc5 has an issue affecting its community
integration.
This issue affects 3 projects,
and has been outstanding for 25 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-catalina : Servlet 2.4 Reference Implementation
- jakarta-tomcat-jasper_tc5 : JavaServer Pages JSP 2.0 implementation (for
Tomcat 5.x)
- jakarta-tomcat-jk : Connectors to various web servers
Full details are available at:
http://vmgump.apache.org/gump/public/jakarta-tomcat-jasper_tc5/jakarta-tomcat-jasper_tc5/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Dependency on ant exists, no need to add for property ant.jar.
-INFO- Failed with reason build failed
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-jasper_tc5/jakarta-tomcat-jasper_tc5/gump_work/build_jakarta-tomcat-jasper_tc5_jakarta-tomcat-jasper_tc5.html
Work Name: build_jakarta-tomcat-jasper_tc5_jakarta-tomcat-jasper_tc5 (Type:
Build)
Work ended in a state of : Failed
Elapsed: 7 secs
Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true
-Dbuild.sysclasspath=only
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
-Djsp-api.jar=/srv/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar
-Dcommons-el.jar=/srv/gump/public/workspace/apache-commons/el/dist/commons-el.jar
-Djasper-compiler-jdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar
-Dant.jar=/srv/gump/public/workspace/ant/dist/lib/ant.jar
-Dservlet-api.jar=/srv/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar
-Dcompile.source=1.4 dist
[Working Directory: /srv/gump/public/workspace/jakarta-tomcat-jasper_tc5]
CLASSPATH:
/usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-20130818.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-20130818.jar:/srv/gump/public/workspace/apache-commons/el/dist/commons-el.jar:/srv/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/srv/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar:/srv/gump/packages/
eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar
-
Buildfile: /srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build.xml
build-prepare:
[mkdir] Created dir:
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build
[mkdir] Created dir:
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/bin
[mkdir] Created dir:
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/common/classes
[mkdir] Created dir:
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/common/lib
[mkdir] Created dir:
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/shared/classes
[mkdir] Created dir:
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/shared/lib
copy-launcher.jars:
build-static:
[copy] Copying 4 files to
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/bin
build-only:
[javac] Compiling 97 source files to
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/shared/classes
[javac]
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/src/share/org/apache/jasper/compiler/JDTCompiler.java:86:
error: CompilationUnit is not abstract and does not override abstract method
ignoreOptionalProblems() in ICompilationUnit
[javac] class CompilationUnit implements ICompilationUnit {
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 1 error
BUILD FAILED
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build.xml:150: Compile
faile
[GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-validate has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 19 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-validate : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-validate.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-validate (Type: Build) Work ended in a state of : Failed Elapsed: 17 secs Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.7-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-5.7-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-20130818.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/tar get/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-20130818.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-20130818.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-20130818.jar:/srv/gump/public/workspace/google-guava/guava/target/guava-15.0-SNAPSHOT.jar - Buildfile: /srv/gump/public/workspace/tomcat-7.0.x/build.xml build-prepare: [delete] Deleting directory /srv/gump/public/workspace/tomcat-7.0.x/output/build/temp [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/build/temp compile-prepare: download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-5.7-SNAPSHOT.jar downloadzip: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/DefaultTestCase.java:22:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestAsyncQueue.java:24:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestSizePreservation.java:22:1: Import from illegal package - junit.framework.TestCase. BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:451: Got 3 errors and 0 warnings. Total time: 17 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/rss.xml - Atom: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 2013081803, vmgump.apache.org:vmgump:2013081803 Gump E-mail Identifier (unique within run) #6. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[Bug 55383] Improve markup and design of Tomcat's HTML pages
https://issues.apache.org/bugzilla/show_bug.cgi?id=55383 Konstantin Preißer changed: What|Removed |Added Attachment #30735|0 |1 is obsolete|| --- Comment #6 from Konstantin Preißer --- Created attachment 30739 --> https://issues.apache.org/bugzilla/attachment.cgi?id=30739&action=edit Updated patch for improving HTML markup & style in Tomcat docs I updated the patch with minor improvements (e.g. replace tabs with spaces, added AL2 to the new CSS file, further improvements of XSLT contents). I also changed the JavaScript for the Comments section to annotate XSLT-generated strings to the
[Bug 55383] Improve markup and design of Tomcat's HTML pages
https://issues.apache.org/bugzilla/show_bug.cgi?id=55383 --- Comment #7 from Konstantin Preißer --- Created attachment 30740 --> https://issues.apache.org/bugzilla/attachment.cgi?id=30740&action=edit New Tomcat image to be placed in "trunk/webapps/docs/images/" folder -- 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 55383] Improve markup and design of Tomcat's HTML pages
https://issues.apache.org/bugzilla/show_bug.cgi?id=55383 Konstantin Preißer changed: What|Removed |Added Attachment #30739|0 |1 is obsolete|| --- Comment #8 from Konstantin Preißer --- Created attachment 30741 --> https://issues.apache.org/bugzilla/attachment.cgi?id=30741&action=edit Updated patch for improving HTML markup & style in Tomcat docs Sorry - the previous patch contained the wrong CSS file. -- 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
[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-trunk-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 10 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-test : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on junit exists, no need to add for property hamcrest.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-trunk exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.html Work Name: build_tomcat-trunk_tomcat-trunk-test (Type: Build) Work ended in a state of : Failed Elapsed: 44 mins 59 secs Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-20130818.jar -Dobjenesis.jar=/srv/gump/public/workspace/objenesis/main/target/objenesis-1.5-SNAPSHOT.jar -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-20130818-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-20130818.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-20130818-native-src.tar.gz -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/apache-commons/pool -Dcommons-dbcp.home=/ srv/gump/public/workspace/apache-commons/dbcp -Deasymock.jar=/srv/gump/public/workspace/easymock/easymock/target/easymock-3.2.jar -Dhamcrest.jar=/srv/gump/public/workspace/junit/dist/junit-20130818.jar -Dcglib.jar=/srv/gump/packages/cglib/cglib-nodep-2.2.jar test [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servle t-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/websocket-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-storeconfig.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-jni.jar:/srv/gump/public/workspace/tomcat -trunk/output/build/lib/tomcat-spdy.jar:/
[GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module tomcat-7.0.x) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 24 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-test : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on junit exists, no need to add for property hamcrest.jar. -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-7.0.x/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-test.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-test (Type: Build) Work ended in a state of : Failed Elapsed: 31 mins 18 secs Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-20130818.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-20130818-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-20130818-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-20130818.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/s rv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-20130818.jar -Dhamcrest.jar=/srv/gump/public/workspace/junit/dist/junit-20130818.jar test [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-7.0.x/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/servle t-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-util.jar:/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-20130818.jar:/srv/gump/pub
[Bug 55444] New: Support JDBC Drivers outside of tomcat/lib/
https://issues.apache.org/bugzilla/show_bug.cgi?id=55444 Bug ID: 55444 Summary: Support JDBC Drivers outside of tomcat/lib/ Product: Tomcat 7 Version: trunk Hardware: PC OS: Mac OS X 10.4 Status: NEW Severity: normal Priority: P2 Component: Catalina Assignee: dev@tomcat.apache.org Reporter: david.blev...@gmail.com Created attachment 30742 --> https://issues.apache.org/bugzilla/attachment.cgi?id=30742&action=edit Patch for loading from Thread context classloader We use the Tomcat jdbc pooling code in TomEE by default and would like to allow users to put drivers in alternate locations than the server lib/ directory. Motivation is some users have reported need to support different versions of the same driver class to be able to connect to different versions of the same database . The attached patch uses the same classloading logic first, if that fails it tries again using the Thread context classloader. -- 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
Loading drivers from outside server lib/
Hi All! Whipped up a short little patch to allow for JDBC drivers and interceptors to be loaded from the thread context class loader as well as the traditional way using effectively the server/lib/ based classloader. - https://issues.apache.org/bugzilla/show_bug.cgi?id=55444 We were using Commons DBCP which did allow for the driver classloader to be set explicitly. I was tempted to add similar setDriverClassLoader(ClassLoader) and getDriverClassLoader() methods to the PoolConfiguration interface, but it looked like the values there have been intentionally kept to primitive types. Wasn't sure that would be a welcome change. Happy to redo this in whichever way might be best. -David - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
