[EMAIL PROTECTED]: Project commons-digester (in module jakarta-commons) 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 [EMAIL PROTECTED] Project commons-digester has an issue affecting its community integration. This issue affects 49 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - authx-example : Apache Authentication and Authorization Framework - commons-betwixt : Commons Betwixt Package - commons-chain : GoF Chain of Responsibility pattern - commons-configuration : Jakarta commons - commons-digester : XML to Java Object Configuration - commons-digester-rss : Digester RSS Example - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-quartz : Commons Jelly - commons-messenger : A web based JMS framework - commons-modeler : Modeler MBeans - commons-services : Basic Services Architecture - commons-validator : Validation Framework - db-ddlutils : Easy-to-use component for working with Database Definition (... - eyebrowse : Web-based mail archive browsing - fulcrum-cache : Services Framework - fulcrum-configuration-impl : Services Framework - fulcrum-intake : Services Framework - fulcrum-parser : Services Framework - fulcrum-quartz : Services Framework - fulcrum-security-memory : Services Framework - fulcrum-security-nt : Services Framework - fulcrum-template : Services Framework - invicta : Open-source build management tool. - jakarta-lucene : Java Based Search Engine - jakarta-taglibs-jmstags : JMS Taglib - jakarta-tomcat : Servlet 2.2 and JSP 1.1 Reference Implementation - jakarta-tomcat-4.0 : Servlet 2.3 and JSP 1.2 Reference Implementation - jakarta-tomcat-catalina : Servlet 2.4 Reference Implementation - jakarta-tomcat-coyote : Connectors to various web servers - jakarta-tomcat-coyote-tomcat3 : Connectors to various web servers - jakarta-tomcat-coyote-tomcat4 : Connectors to various web servers - jakarta-tomcat-http11 : Connectors to various web servers - jakarta-tomcat-jk : Connectors to various web servers - jakarta-turbine-jcs : Cache - lucene-java : Java Based Search Engine - maven : Project Management Tools - maven-bootstrap : Project Management Tools - myfaces : JavaServer(tm) Faces implementation - naming-config : Apache Directory Naming Component - portals-bridges-frameworks : Support for JSR168 compliant Portlet development - portals-bridges-jsf : Support for JSR168 compliant Portlet development - portals-bridges-struts : Support for JSR168 compliant Portlet development - portals-bridges-velocity : Support for JSR168 compliant Portlet development - quartz : Job Scheduler - struts-sslext : The Struts SSL Extension for HTTP/HTTPS switching - tapestry : Component-based web application framework organized around i... - tomcat-catalina : Servlet 2.3 and JSP 1.2 Reference Implementation - velocity-tools : VelocityTools project Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-digester/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-digester.jar] identifier set to project name -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-commons/commons-digester/gump_work/build_jakarta-commons_commons-digester.html Work Name: build_jakarta-commons_commons-digester (Type: Build) Work ended in a state of : Failed Elapsed: 6 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -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 -Dbuild.sysclasspath=only dist [Working Directory: /srv/gump/public/workspace/jakarta-commons/digester] CLASSPATH:
[EMAIL PROTECTED]: Project commons-digester (in module jakarta-commons) 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 [EMAIL PROTECTED] Project commons-digester has an issue affecting its community integration. This issue affects 49 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - authx-example : Apache Authentication and Authorization Framework - commons-betwixt : Commons Betwixt Package - commons-chain : GoF Chain of Responsibility pattern - commons-configuration : Jakarta commons - commons-digester : XML to Java Object Configuration - commons-digester-rss : Digester RSS Example - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-quartz : Commons Jelly - commons-messenger : A web based JMS framework - commons-modeler : Modeler MBeans - commons-services : Basic Services Architecture - commons-validator : Validation Framework - db-ddlutils : Easy-to-use component for working with Database Definition (... - eyebrowse : Web-based mail archive browsing - fulcrum-cache : Services Framework - fulcrum-configuration-impl : Services Framework - fulcrum-intake : Services Framework - fulcrum-parser : Services Framework - fulcrum-quartz : Services Framework - fulcrum-security-memory : Services Framework - fulcrum-security-nt : Services Framework - fulcrum-template : Services Framework - invicta : Open-source build management tool. - jakarta-lucene : Java Based Search Engine - jakarta-taglibs-jmstags : JMS Taglib - jakarta-tomcat : Servlet 2.2 and JSP 1.1 Reference Implementation - jakarta-tomcat-4.0 : Servlet 2.3 and JSP 1.2 Reference Implementation - jakarta-tomcat-catalina : Servlet 2.4 Reference Implementation - jakarta-tomcat-coyote : Connectors to various web servers - jakarta-tomcat-coyote-tomcat3 : Connectors to various web servers - jakarta-tomcat-coyote-tomcat4 : Connectors to various web servers - jakarta-tomcat-http11 : Connectors to various web servers - jakarta-tomcat-jk : Connectors to various web servers - jakarta-turbine-jcs : Cache - lucene-java : Java Based Search Engine - maven : Project Management Tools - maven-bootstrap : Project Management Tools - myfaces : JavaServer(tm) Faces implementation - naming-config : Apache Directory Naming Component - portals-bridges-frameworks : Support for JSR168 compliant Portlet development - portals-bridges-jsf : Support for JSR168 compliant Portlet development - portals-bridges-struts : Support for JSR168 compliant Portlet development - portals-bridges-velocity : Support for JSR168 compliant Portlet development - quartz : Job Scheduler - struts-sslext : The Struts SSL Extension for HTTP/HTTPS switching - tapestry : Component-based web application framework organized around i... - tomcat-catalina : Servlet 2.3 and JSP 1.2 Reference Implementation - velocity-tools : VelocityTools project Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-digester/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-digester.jar] identifier set to project name -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-commons/commons-digester/gump_work/build_jakarta-commons_commons-digester.html Work Name: build_jakarta-commons_commons-digester (Type: Build) Work ended in a state of : Failed Elapsed: 6 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -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 -Dbuild.sysclasspath=only dist [Working Directory: /srv/gump/public/workspace/jakarta-commons/digester] CLASSPATH:
[EMAIL PROTECTED]: Project commons-id (in module jakarta-commons-sandbox) 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 [EMAIL PROTECTED] Project commons-id has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 9 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-id : Commons Identifier Package Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-id-21072007.jar] identifier set to project name -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/jakarta-commons-sandbox/id/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/jakarta-commons-sandbox/id/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/jakarta-commons-sandbox/id/project.properties -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/gump_work/build_jakarta-commons-sandbox_commons-id.html Work Name: build_jakarta-commons-sandbox_commons-id (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/jakarta-commons-sandbox/id] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.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-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-21072007.jar:/srv/gump/public/workspace/junit/dist/junit-21072007.jar:/srv/gump/packages/maven-cobertura-plugin/maven-cobertura-plugin-1.1.jar:/srv/gump/packages/maven-xdoc-plugin/maven-xdoc-plugin-1.9.2.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 The build cannot continue because of the following unsatisfied dependencies: dom4j-1.4.jar commons-jelly-1.0-RC1.jar commons-jelly-tags-jsl-1.0.jar commons-jelly-tags-log-1.0.jar commons-jelly-tags-velocity-1.0.jar commons-jelly-tags-xml-1.1.jar (try downloading from http://jakarta.apache.org/commons/jelly/libs/xml/) maven-1.0.2.jar maven-model-3.0.0.jar velocity-1.4.jar commons-jelly-tags-fmt-1.0.jar Total time: 2 seconds Finished at: Sat Jul 21 01:46:51 GMT-08:00 2007 - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 0521072007, vmgump:vmgump-public:0521072007 Gump E-mail Identifier (unique within run) #42. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-id (in module jakarta-commons-sandbox) 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 [EMAIL PROTECTED] Project commons-id has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 9 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-id : Commons Identifier Package Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-id-21072007.jar] identifier set to project name -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/jakarta-commons-sandbox/id/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/jakarta-commons-sandbox/id/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/jakarta-commons-sandbox/id/project.properties -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/gump_work/build_jakarta-commons-sandbox_commons-id.html Work Name: build_jakarta-commons-sandbox_commons-id (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/jakarta-commons-sandbox/id] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.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-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-21072007.jar:/srv/gump/public/workspace/junit/dist/junit-21072007.jar:/srv/gump/packages/maven-cobertura-plugin/maven-cobertura-plugin-1.1.jar:/srv/gump/packages/maven-xdoc-plugin/maven-xdoc-plugin-1.9.2.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 The build cannot continue because of the following unsatisfied dependencies: dom4j-1.4.jar commons-jelly-1.0-RC1.jar commons-jelly-tags-jsl-1.0.jar commons-jelly-tags-log-1.0.jar commons-jelly-tags-velocity-1.0.jar commons-jelly-tags-xml-1.1.jar (try downloading from http://jakarta.apache.org/commons/jelly/libs/xml/) maven-1.0.2.jar maven-model-3.0.0.jar velocity-1.4.jar commons-jelly-tags-fmt-1.0.jar Total time: 2 seconds Finished at: Sat Jul 21 01:46:51 GMT-08:00 2007 - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 0521072007, vmgump:vmgump-public:0521072007 Gump E-mail Identifier (unique within run) #42. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-util (in module commons-jelly) 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 [EMAIL PROTECTED] Project commons-jelly-tags-util has an issue affecting its community integration. This issue affects 7 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-fmt-test : Commons Jelly - commons-jelly-tags-html : Commons Jelly - commons-jelly-tags-jsl : Commons Jelly - commons-jelly-tags-jsl-test : Commons Jelly - commons-jelly-tags-util : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-util-21072007.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/util/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-jelly/jelly-tags/util/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/util/project.properties -INFO- Project Reports in: /srv/gump/public/workspace/commons-jelly/jelly-tags/util/target/test-reports -WARNING- No directory [/srv/gump/public/workspace/commons-jelly/jelly-tags/util/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/gump_work/build_commons-jelly_commons-jelly-tags-util.html Work Name: build_commons-jelly_commons-jelly-tags-util (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/util] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-21072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-21072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21072007.jar:/srv/gump/public/workspace/jakarta-commons/lang/commons-lang-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-21072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-21072007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 The build cannot continue because of the following unsatisfied dependency: commons-beanutils-bean-collections-1.7.0.jar (try downloading from http://jakarta.apache.org/commons/beanutils/) Total time: 2 seconds Finished at: Sat Jul 21 01:47:14 GMT-08:00 2007 - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 0521072007, vmgump:vmgump-public:0521072007 Gump E-mail Identifier (unique within run) #43. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-util (in module commons-jelly) 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 [EMAIL PROTECTED] Project commons-jelly-tags-util has an issue affecting its community integration. This issue affects 7 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-fmt-test : Commons Jelly - commons-jelly-tags-html : Commons Jelly - commons-jelly-tags-jsl : Commons Jelly - commons-jelly-tags-jsl-test : Commons Jelly - commons-jelly-tags-util : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-util-21072007.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/util/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-jelly/jelly-tags/util/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/util/project.properties -INFO- Project Reports in: /srv/gump/public/workspace/commons-jelly/jelly-tags/util/target/test-reports -WARNING- No directory [/srv/gump/public/workspace/commons-jelly/jelly-tags/util/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/gump_work/build_commons-jelly_commons-jelly-tags-util.html Work Name: build_commons-jelly_commons-jelly-tags-util (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/util] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-21072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-21072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21072007.jar:/srv/gump/public/workspace/jakarta-commons/lang/commons-lang-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-21072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-21072007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 The build cannot continue because of the following unsatisfied dependency: commons-beanutils-bean-collections-1.7.0.jar (try downloading from http://jakarta.apache.org/commons/beanutils/) Total time: 2 seconds Finished at: Sat Jul 21 01:47:14 GMT-08:00 2007 - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-util/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 0521072007, vmgump:vmgump-public:0521072007 Gump E-mail Identifier (unique within run) #43. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) 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 [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jaxme : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-jaxme-21072007.jar] identifier set to project name -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-js. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-xs. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-api. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.properties -INFO- Project Reports in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/target/test-reports -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/gump_work/build_commons-jelly_commons-jelly-tags-jaxme.html Work Name: build_commons-jelly_commons-jelly-tags-jaxme (Type: Build) Work ended in a state of : Failed Elapsed: 9 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-21072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-21072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-21072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-21072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-21072007.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxme2-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmeapi-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmejs-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmexs-0.5.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xmlunit/build/lib/xmlunit-21072007.jar - [javac] symbol : variable super [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] super.characters(pChars, pOffset, pLen); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:305: cannot find symbol [javac] symbol : variable super [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] super.init(pData); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:315: cannot find symbol [javac] symbol : method getData() [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] __handler_Name.init(getData()); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressHandler.java:22: cannot find symbol [javac] symbol : method getData() [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressHandler
[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) 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 [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jaxme : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-jaxme-21072007.jar] identifier set to project name -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-js. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-xs. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-api. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.properties -INFO- Project Reports in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/target/test-reports -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/gump_work/build_commons-jelly_commons-jelly-tags-jaxme.html Work Name: build_commons-jelly_commons-jelly-tags-jaxme (Type: Build) Work ended in a state of : Failed Elapsed: 9 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-21072007.jar:/srv/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21072007.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-21072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21072007.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-21072007.jar:/srv/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-21072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-21072007.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-21072007.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxme2-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmeapi-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmejs-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmexs-0.5.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xmlunit/build/lib/xmlunit-21072007.jar - [javac] symbol : variable super [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] super.characters(pChars, pOffset, pLen); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:305: cannot find symbol [javac] symbol : variable super [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] super.init(pData); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:315: cannot find symbol [javac] symbol : method getData() [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] __handler_Name.init(getData()); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressHandler.java:22: cannot find symbol [javac] symbol : method getData() [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressHandler
[jira] Created: (JXPATH-97) Incomplete handling of undefined namespaces
Incomplete handling of undefined namespaces --- Key: JXPATH-97 URL: https://issues.apache.org/jira/browse/JXPATH-97 Project: Commons JXPath Issue Type: Bug Affects Versions: 1.2 Final, Nightly Builds Reporter: Sergey Vladimirov Fix For: 1.3 Mcduffey, Joe [EMAIL PROTECTED] Can someone tell me how to register namespaces so that attributes with namespaces does not cause the exception org.apache.common.ri.model.dom.DOMNodePointer.createAttribute unknown namespace prefix: xsi For example the following ElementA A:myAttr=Mytype B:ElementBMY VALUE/B:ElementB /ElementA Would result in the following exception: org.apache.common.ri.model.dom.DOMNodePointer.createAttribute unknown namespace prefix: A FYI: In this example there was a namespace decaration in the file and I also manually called the registerNamespace(A,/http...); registerNamespace(B,/http...); There was no problem encountered for elements. Only attributes. Can someone help? Thanks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JXPATH-97) Incomplete handling of undefined namespaces
[ https://issues.apache.org/jira/browse/JXPATH-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Vladimirov updated JXPATH-97: Attachment: patch.txt Incomplete handling of undefined namespaces --- Key: JXPATH-97 URL: https://issues.apache.org/jira/browse/JXPATH-97 Project: Commons JXPath Issue Type: Bug Affects Versions: Nightly Builds, 1.2 Final Reporter: Sergey Vladimirov Fix For: 1.3 Attachments: NamespacesTest.java, patch.txt Mcduffey, Joe [EMAIL PROTECTED] Can someone tell me how to register namespaces so that attributes with namespaces does not cause the exception org.apache.common.ri.model.dom.DOMNodePointer.createAttribute unknown namespace prefix: xsi For example the following ElementA A:myAttr=Mytype B:ElementBMY VALUE/B:ElementB /ElementA Would result in the following exception: org.apache.common.ri.model.dom.DOMNodePointer.createAttribute unknown namespace prefix: A FYI: In this example there was a namespace decaration in the file and I also manually called the registerNamespace(A,/http...); registerNamespace(B,/http...); There was no problem encountered for elements. Only attributes. Can someone help? Thanks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JXPATH-97) Incomplete handling of undefined namespaces
[ https://issues.apache.org/jira/browse/JXPATH-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Vladimirov updated JXPATH-97: Attachment: NamespacesTest.java Incomplete handling of undefined namespaces --- Key: JXPATH-97 URL: https://issues.apache.org/jira/browse/JXPATH-97 Project: Commons JXPath Issue Type: Bug Affects Versions: Nightly Builds, 1.2 Final Reporter: Sergey Vladimirov Fix For: 1.3 Attachments: NamespacesTest.java, patch.txt Mcduffey, Joe [EMAIL PROTECTED] Can someone tell me how to register namespaces so that attributes with namespaces does not cause the exception org.apache.common.ri.model.dom.DOMNodePointer.createAttribute unknown namespace prefix: xsi For example the following ElementA A:myAttr=Mytype B:ElementBMY VALUE/B:ElementB /ElementA Would result in the following exception: org.apache.common.ri.model.dom.DOMNodePointer.createAttribute unknown namespace prefix: A FYI: In this example there was a namespace decaration in the file and I also manually called the registerNamespace(A,/http...); registerNamespace(B,/http...); There was no problem encountered for elements. Only attributes. Can someone help? Thanks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONFIGURATION-284) ability to read OS environment variables
[
https://issues.apache.org/jira/browse/CONFIGURATION-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514415
]
Oliver Heger commented on CONFIGURATION-284:
Vasily, many thanks for your contribution.
For the reasons outlined above I am still reluctant to add this feature to the
code base. If you don't mind I would bring this topic again to the commons
developer list and ask whether the opinion to support environment variables in
one of the core libraries has changed in the mean time.
What we could do in any case is adding your code to the WIKI in our examples
section:
http://wiki.apache.org/jakarta-commons/Configuration
ability to read OS environment variables
Key: CONFIGURATION-284
URL: https://issues.apache.org/jira/browse/CONFIGURATION-284
Project: Commons Configuration
Issue Type: New Feature
Components: Interpolation
Reporter: Aksel Schmidt
Priority: Minor
Attachments: EnvironmentConfiguration.java
suggestion:
interpolation with system environment, i.e.
${sys:user.name} reads from systemproperties (as of today)
${sysenv:TEMP} reads from OS environment
these can be parsed from a supported set of OS's - windows read from a set in
a cmd /c, unix/linux from an env etc. (just once on demand)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (CONFIGURATION-285) configuration fileName=local-configuration.xml config-optional=true / does not report parsing errors in local-configuration.xml
[ https://issues.apache.org/jira/browse/CONFIGURATION-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Heger updated CONFIGURATION-285: --- Fix Version/s: 1.5 Assignee: Oliver Heger configuration fileName=local-configuration.xml config-optional=true / does not report parsing errors in local-configuration.xml - Key: CONFIGURATION-285 URL: https://issues.apache.org/jira/browse/CONFIGURATION-285 Project: Commons Configuration Issue Type: Bug Affects Versions: 1.4 Reporter: Thorbjørn Ravn Andersen Assignee: Oliver Heger Fix For: 1.5 I'm trying to build a configuration system to be shared between our Java applications. I therefore want to have optional configurations included from the main configuration file read by DefaultConfigurationBuilder configuration fileName=local-configuration.xml config-optional=true / I have found that if the sub-configuration file is invalid the error is silently ignored. The same without config-options=true results in a ConfigurationException to be thrown (which wraps a ConfigurationRuntimeException which wraps the ConfigurationException which wraps the SAXException). I believe that the behaviour is incorrect. The sub-configuration file should be skipped if not found, but any errors found when parsing the existing file should be logged. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558330 - in /jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration: ConfigurationErrorListenerImpl.java TestDatabaseConfiguration.java TestFileConfiguration
Author: oheger
Date: Sat Jul 21 08:26:19 2007
New Revision: 558330
URL: http://svn.apache.org/viewvc?view=revrev=558330
Log:
Minor refactoring of the unit tests that check error listeners: a generic mock
event listener class was extracted.
Added:
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/ConfigurationErrorListenerImpl.java
(with props)
Modified:
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/TestDatabaseConfiguration.java
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/TestFileConfiguration.java
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/TestJNDIConfiguration.java
Added:
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/ConfigurationErrorListenerImpl.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/ConfigurationErrorListenerImpl.java?view=autorev=558330
==
---
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/ConfigurationErrorListenerImpl.java
(added)
+++
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/ConfigurationErrorListenerImpl.java
Sat Jul 21 08:26:19 2007
@@ -0,0 +1,101 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the License); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.commons.configuration;
+
+import junit.framework.Assert;
+
+import org.apache.commons.configuration.event.ConfigurationErrorEvent;
+import org.apache.commons.configuration.event.ConfigurationErrorListener;
+
+/**
+ * An implementation of the codeConfigurationErrorListener/code interface
+ * that can be used in unit tests. This implementation just records received
+ * events and allows to test whether expected errors occurred.
+ *
+ * @author Oliver Heger
+ * @version $Id$
+ */
+public class ConfigurationErrorListenerImpl implements
+ConfigurationErrorListener
+{
+/** Stores the last received error event. */
+private ConfigurationErrorEvent event;
+
+/** Stores the number of calls to configurationError(). */
+private int errorCount;
+
+/**
+ * An error event is received. Updates the internal counter and stores the
+ * event.
+ *
+ * @param event the error event
+ */
+public void configurationError(ConfigurationErrorEvent event)
+{
+this.event = event;
+errorCount++;
+}
+
+/**
+ * Returns the last received error event.
+ *
+ * @return the last error event (may be bnull/b)
+ */
+public ConfigurationErrorEvent getLastEvent()
+{
+return event;
+}
+
+/**
+ * Returns the number of received error events.
+ *
+ * @return the number of error events
+ */
+public int getErrorCount()
+{
+return errorCount;
+}
+
+/**
+ * Checks whether no error event was received.
+ */
+public void verify()
+{
+Assert.assertEquals(Error events received, 0, errorCount);
+}
+
+/**
+ * Checks whether an expected error event was received. This is a
+ * convenience method for checking whether exactly one event of a certain
+ * type was received.
+ *
+ * @param type the type of the event
+ * @param propName the name of the property
+ * @param propValue the value of the property
+ */
+public void verify(int type, String propName, Object propValue)
+{
+Assert.assertEquals(Wrong number of error events, 1, errorCount);
+Assert.assertEquals(Wrong event type, type, event.getType());
+Assert.assertTrue(Wrong property name, (propName == null) ? event
+.getPropertyName() == null : propName.equals(event
+.getPropertyName()));
+Assert.assertTrue(Wrong property value, (propValue == null) ? event
+.getPropertyValue() == null : propValue.equals(event
+.getPropertyValue()));
+}
+}
Propchange:
svn commit: r558331 - /jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
Author: psteitz
Date: Sat Jul 21 08:44:03 2007
New Revision: 558331
URL: http://svn.apache.org/viewvc?view=revrev=558331
Log:
Fixed typo in comment.
Modified:
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
Modified:
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java?view=diffrev=558331r1=558330r2=558331
==
---
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
(original)
+++
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
Sat Jul 21 08:44:03 2007
@@ -211,7 +211,7 @@
public void close() throws SQLException {
// close can be called multiple times, but PoolableConnection
improperly
// throws an exception when a connection is closed twice, so before
calling
-// close we aren't alreayd closed
+// close we aren't already closed
if (!isClosed()) {
try {
_conn.close();
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558332 - in /jakarta/commons/proper/dbcp/trunk/src: java/org/apache/commons/dbcp/ test/org/apache/commons/dbcp/ test/org/apache/commons/dbcp/datasources/ test/org/apache/commons/dbcp/mana
Author: psteitz
Date: Sat Jul 21 08:48:19 2007
New Revision: 558332
URL: http://svn.apache.org/viewvc?view=revrev=558332
Log:
Modified PoolingDataSource, PoolingDriver and DelegatingStatement to assure
that all all returned Statements, PreparedStatements, CallableStatements and
ResultSets are wrapped with a delegating object, which already properly handle
the back pointers for Connection and Statement. Also added tests to to assure
that the *same* object used to create the statement or result set is returned
from either getConnection() or getStatement().
JIRA: DBCP-11
Patch provided by Dain Sundstrom
Modified:
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingStatement.java
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDriver.java
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TestConnectionPool.java
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TesterConnection.java
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TesterPreparedStatement.java
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TesterStatement.java
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestSharedPoolDataSource.java
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/managed/TestManagedDataSourceInTx.java
Modified:
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingStatement.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingStatement.java?view=diffrev=558332r1=558331r2=558332
==
---
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingStatement.java
(original)
+++
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingStatement.java
Sat Jul 21 08:48:19 2007
@@ -314,8 +314,15 @@
public boolean getMoreResults(int current) throws SQLException
{ checkOpen(); try { return _stmt.getMoreResults(current); } catch
(SQLException e) { handleException(e); return false; } }
-public ResultSet getGeneratedKeys() throws SQLException
-{ checkOpen(); try { return _stmt.getGeneratedKeys(); } catch
(SQLException e) { handleException(e); return null; } }
+public ResultSet getGeneratedKeys() throws SQLException {
+checkOpen();
+try {
+return DelegatingResultSet.wrapResultSet(this,
_stmt.getGeneratedKeys());
+} catch (SQLException e) {
+handleException(e);
+return null;
+}
+}
public int executeUpdate(String sql, int autoGeneratedKeys) throws
SQLException
{ checkOpen(); try { return _stmt.executeUpdate(sql, autoGeneratedKeys); }
catch (SQLException e) { handleException(e); return 0; } }
Modified:
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java?view=diffrev=558332r1=558331r2=558332
==
---
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java
(original)
+++
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolingDataSource.java
Sat Jul 21 08:48:19 2007
@@ -203,12 +203,12 @@
public Statement createStatement() throws SQLException {
checkOpen();
-return delegate.createStatement();
+return new DelegatingStatement(this, delegate.createStatement());
}
public Statement createStatement(int resultSetType, int
resultSetConcurrency) throws SQLException {
checkOpen();
-return delegate.createStatement(resultSetType,
resultSetConcurrency);
+return new DelegatingStatement(this,
delegate.createStatement(resultSetType, resultSetConcurrency));
}
public boolean innermostDelegateEquals(Connection c) {
@@ -290,22 +290,22 @@
public CallableStatement prepareCall(String sql) throws SQLException {
checkOpen();
-return delegate.prepareCall(sql);
+return new DelegatingCallableStatement(this,
delegate.prepareCall(sql));
}
public CallableStatement prepareCall(String sql, int resultSetType,
int resultSetConcurrency) throws SQLException {
checkOpen();
-return delegate.prepareCall(sql, resultSetType,
resultSetConcurrency);
+return new DelegatingCallableStatement(this,
delegate.prepareCall(sql, resultSetType,
[jira] Resolved: (DBCP-11) [dbcp] stmt.getConnection() != Connection used to create the statement
[ https://issues.apache.org/jira/browse/DBCP-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-11. - Resolution: Fixed Patch applied. Thanks. [dbcp] stmt.getConnection() != Connection used to create the statement -- Key: DBCP-11 URL: https://issues.apache.org/jira/browse/DBCP-11 Project: Commons Dbcp Issue Type: Bug Affects Versions: 1.2 Environment: Operating System: other Platform: All Reporter: Alexander Rupsch Fix For: 1.3 Attachments: back-pointers.patch Hi, I'm not an expert in implementing connection pools or jdbc itself. But shouldn't the following code work? Connection con = pool.getConnection() PreparedStatement ps = con.prepareStatement() con.equals(ps.getConnection) // returns false! Ok, I don't need it to be equal, but the following also does not work: ps.getConnection().close() con.isClosed() // is false!!! That means, if I have a Statment and want to close its connection, I have to remember the conncetion. Is that the requested behavior? Because of this my pool is running over. The java.sql API says that Statment.getConnection() has to be the connection which created the statement. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558334 - /jakarta/commons/proper/dbcp/trunk/xdocs/changes.xml
Author: psteitz Date: Sat Jul 21 08:52:02 2007 New Revision: 558334 URL: http://svn.apache.org/viewvc?view=revrev=558334 Log: Document change in r558332. Modified: jakarta/commons/proper/dbcp/trunk/xdocs/changes.xml Modified: jakarta/commons/proper/dbcp/trunk/xdocs/changes.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/xdocs/changes.xml?view=diffrev=558334r1=558333r2=558334 == --- jakarta/commons/proper/dbcp/trunk/xdocs/changes.xml (original) +++ jakarta/commons/proper/dbcp/trunk/xdocs/changes.xml Sat Jul 21 08:52:02 2007 @@ -69,6 +69,15 @@ updated any tests that incorrectly assert that a resource can not be closed more then once. Fixes DBCP-3, DBCP-5, DBCP-23 and DBCP-134. /action + action dev=psteitz type=fix issue=DBCP-11 due-to=Dain Sundstrom +Modified PoolingDataSource, PoolingDriver and DelegatingStatement to +assure that all all returned Statements, PreparedStatements, +CallableStatements and ResultSets are wrapped with a delegating object, +which already properly handle the back pointers for Connection and +Statement. Also added tests to to assure that the *same* object used +to create the statement or result set is returned from either +getConnection() or getStatement(). + /action /release release version=1.2.2 date=2007-04-04 description=This is a maintenance release containing bug fixes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558343 - /jakarta/commons/proper/codec/trunk/xdocs/issue-tracking.xml
Author: tobrien Date: Sat Jul 21 09:40:50 2007 New Revision: 558343 URL: http://svn.apache.org/viewvc?view=revrev=558343 Log: updated issue tracker documentation to point to JIRA, was pointing to bugzilla Modified: jakarta/commons/proper/codec/trunk/xdocs/issue-tracking.xml Modified: jakarta/commons/proper/codec/trunk/xdocs/issue-tracking.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/codec/trunk/xdocs/issue-tracking.xml?view=diffrev=558343r1=558342r2=558343 == --- jakarta/commons/proper/codec/trunk/xdocs/issue-tracking.xml (original) +++ jakarta/commons/proper/codec/trunk/xdocs/issue-tracking.xml Sat Jul 21 09:40:50 2007 @@ -24,18 +24,18 @@ !-- == -- section name=Issue tracking p - Commons Codec uses a href=http://issues.apache.org/bugzilla/;ASF Bugzilla/a for tracking issues. - To use Bugzilla you may need to a href=http://issues.apache.org/bugzilla/createaccount.cgi;create an account/a. + Commons Codec uses the ASF installation of a href=http://issues.apache.org/jira/browse/CODEC;JIRA/a for tracking requests for enhancement, bugs, and patches. + To create an issue in Jira you may need to a href=https://issues.apache.org/jira/secure/Signup!default.jspa;create an account/a. /p p If you would like to report a bug, or raise an enhancement request with Commons Codec please do the following: ol - lia href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=NEEDINFOamp;product=Commonsamp;component=Codec;Search existing open bugs/a. +lia href=http://issues.apache.org/jira/browse/CODEC;Search existing open bugs/a. If you find your issue listed then please add a comment with your details./li lia href=http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/;Search the mailing list archive/a. You may find your issue or idea has already been discussed./li - lia href=http://issues.apache.org/bugzilla/enter_bug.cgi?product=Commonsamp;component=Codecamp;version=1.3%20Finalamp;short_desc=%5Bcodec%5D%20%22Your%20subject%20heading%20here%22amp;comment=Please%20provide%20details%20here.%20Its%20best%20to%20submit%20patches%20that%20alter%0D%0Aexisting%20file%20content%20in%20%22unified%20diff%22%20format.%20%0D%0A%0D%0ASubmissions%20that%20provide%20new%20files%20can%20be%20supplied%20as%20direct%20file%0D%0Aattachments%20or%20archives%20in%20zip%20or%20tar.gz%20format.%20please%20be%20kind%20%0D%0Aenough%20to%20identify%20the%20format%20of%20the%20attached%20archive%20as%20bugzilla%0D%0Atends%20to%20strip%20these%20characterstics%20by%20removing%20the%20files%20extension.;Submit a bug report or enhancement request/a. +lia href=http://issues.apache.org/jira/browse/CODEC;Submit a bug report or enhancement request/a. Please prefix all new issues with [codec] in the summary line. /li /ol @@ -51,10 +51,10 @@ p You may also find these links useful: ul - lia href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=NEEDINFOamp;product=Commonsamp;component=Codec;All Open Codec bugs/a/li - lia href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVEDamp;bug_status=VERIFIEDamp;bug_status=CLOSEDamp;product=Commonsamp;component=Codec;All Closed Codec bugs/a/li - lia href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=NEEDINFOamp;bug_status=RESOLVEDamp;bug_status=VERIFIEDamp;bug_status=CLOSEDamp;product=Commonsamp;component=Codec;All Codec bugs/a/li - /ul +lia href=http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=trueamp;pid=12310464amp;status=1;All Open Codec Issues/a/li +lia href=http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=trueamp;mode=hideamp;pid=12310464amp;status=5amp;status=6amp;updated:previous=-1wamp;sorter/field=updatedamp;sorter/order=DESC;Recently Resolved Issues/a/li +lia href=http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=trueamp;mode=hideamp;pid=12310464amp;updated:previous=-1wamp;sorter/field=updatedamp;sorter/order=DESC;Recently Updated Issues/a/li +/ul /p /section !-- == -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558348 - /jakarta/commons/proper/codec/trunk/xdocs/index.xml
Author: tobrien Date: Sat Jul 21 09:59:34 2007 New Revision: 558348 URL: http://svn.apache.org/viewvc?view=revrev=558348 Log: The Codec index page was referencing Bugzilla, modified to reference JIRA Modified: jakarta/commons/proper/codec/trunk/xdocs/index.xml Modified: jakarta/commons/proper/codec/trunk/xdocs/index.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/codec/trunk/xdocs/index.xml?view=diffrev=558348r1=558347r2=558348 == --- jakarta/commons/proper/codec/trunk/xdocs/index.xml (original) +++ jakarta/commons/proper/codec/trunk/xdocs/index.xml Sat Jul 21 09:59:34 2007 @@ -101,9 +101,7 @@ so prefix your email by [codec]. /p p -Issues may be reported via a href=issue-tracking.htmlASF Bugzilla/a. -Please remember that Bugzilla is shared between all commons components, -so prefix your issue by [codec]. +Issues may be reported via a href=issue-tracking.htmlASF JIRA/a. /p /section !-- == -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r557176 - in /jakarta/commons/proper/dbcp/trunk: src/java/org/apache/commons/dbcp/ src/java/org/apache/commons/dbcp/cpdsadapter/ src/test/org/apache/commons/dbcp/ src/test/org/apache/c
On 7/19/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 7/19/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
I think passivate() is called automatically when the connection is
put back in the pool (due to the _conn.close() call). I think there
are tests that check that the statements were closed when the
connection is closed.
OK, I will look at the tests and verify. The removed passivate is on
the DelegatingConnection itself. The statement constructors add the
created DelegatingStatements to the AbandonedTrace of the
DelegatingConnection and its passivate walks the statements and closes
them. _con.close() is on the delegate. You are probably right that
the only resources that really matter get cleaned up in any case and
if the tests show that, then this is no problem.
This is OK. PoolableConnectionFactory.passivateObject invokes
passivate on the DelegatingConnection.
Phil
Anyway, I don't think it is a big deal to call passivate twice. It
used to cause a SQLException because the delegating statements would
throw an exception on the second close.
-dain
On Jul 19, 2007, at 10:33 PM, Phil Steitz wrote:
Sorry I missed this in initial review. I am not sure we want to
remove the passivate() below, since that closes statements traced by
this connection. Am I missing something here?
Phil
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/
DelegatingConnection.java
Tue Jul 17 23:46:16 2007
@@ -208,10 +208,17 @@
* Closes the underlying connection, and close
* any Statements that were not explicitly closed.
*/
-public void close() throws SQLException
-{
-passivate();
-_conn.close();
+public void close() throws SQLException {
+// close can be called multiple times, but
PoolableConnection improperly
+// throws an exception when a connection is closed twice,
so before calling
+// close we aren't alreayd closed
+if (!isClosed()) {
+try {
+_conn.close();
+} finally {
+_closed = true;
+}
+}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Commons Logging 1.1.1 - when?
On Thu, 2007-07-19 at 20:32 +0100, Niall Pemberton wrote: On 7/19/07, Henri Yandell [EMAIL PROTECTED] wrote: On 7/19/07, Sullivan, Sean [EMAIL PROTECTED] wrote: Are there plans to release Commons Logging 1.1.1? I am eager to see Commons Logging 1.1.1 because JCL 1.1 throws exceptions when running in a Java applet sandbox. (This bug is already fixed: https://issues.apache.org/jira/browse/LOGGING-106) The roadmap shows 4 issues that are resolved in Commons Logging 1.1.1: Plus I seem to recall that when I was digging through it for work, I found a significant bugfix that wasn't in JIRA. https://issues.apache.org/jira/browse/LOGGING?report=com.atlassian.jira. plugin.system.project:roadmap-panel Is anybody working on JCL 1.1.1? Not afaik. I put some effort in a bit back, but the release process was too confusing for the time I wanted to put in. Is it worth pinging Simon or Robert (last 2 release managers) directly for help - this may be going under their radar. i consider myself pinged - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DBCP] close issues
On Jul 20, 2007, at 10:15 PM, Phil Steitz wrote: On 7/20/07, Dain Sundstrom [EMAIL PROTECTED] wrote: On Jul 20, 2007, at 11:26 AM, Dain Sundstrom wrote: I think this will require a patch to pooling (documented in DBCP-221). What are the plans for pooling? This is a tiny change so we could do a pool 1.3.1 or 1.4 release. Alternatively, we could wait until DBCP 1.4 (and the next pool release) to address this issue. I am fine waiting to DBCP 1.4, since unless we are talking about different things, this really amounts to a significant change to both dbcp and pool. If what we want is to *always* track open connections and have the lingering close apply to the active (i.e. checked out) as well as idle connections, we need to follow through on what looks like it was the original plan of moving AbandonedObjectPool to pool and use this _all the time_ in place of GenericObjectPool, which is really just an idle object pool (maintains no references to borrowed objects). I think there are two features here also. The first is a lingering close where we close the data source along with all idle connection. Then as the checked out connections are returned to the pool, we destroy them instead of putting them in a closed pool. The second feature is a force close which as you pointed out requires tracking of active connection. After looking at the pooling code, I think that will take a lot of work to implement with the current code. In any case, we need to get a pool release out ASAP since pool 1.3 introduced some bugs that are causing problems (see for example POOL-97) since dbcp started using this version. Synchronization was increased in pool 1.3 as well. The hang here is lack of volunteer time and difficulty getting into the codebase. I have only recently started working on the pool code base. The compositepool package includes an alternative impl that we have been thinking about as a pool 2.0. The plan that I proposed a while back (http://www.mail-archive.com/commons-dev@jakarta.apache.org/ msg94027.html) was to push out a pool 1.3.1 patch release fixing POOL-97 (when reviewing the patch there, remember that dbcp statement pooling can create quite a few pools) and other bugs fixed since 1.3 and have DBCP 1.3 depend on that, both fully backward compatible with current versions. I still think we should do that. I can handle the RM duty for both of these and close a couple more of the pool bugs, but what we need to speed things up is more eyeballs validating and testing and contributing - and applying - patches. I'll try to review the patch. If we do do a 1.3.1, I think we should change GOP and GKOP to destroy objects returned to the pool after the pool is closed. Otherwise you end up with stuck objects in a closed pool. -dain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DBCP] DBCP-44 Deadlock
On Jul 20, 2007, at 5:26 PM, Phil Steitz wrote: On 7/20/07, Dain Sundstrom [EMAIL PROTECTED] wrote: On Jul 20, 2007, at 11:26 AM, Dain Sundstrom wrote: On Jul 19, 2007, at 11:19 PM, Phil Steitz wrote: I would love to have a fix for DBCP-44; but that could wait on pool 1.4 if necessary (and Ipersonally see no way to fix it just within dbcp. It would be great if I was wrong on that). I think the makeObject method is over synchronized. Actually, the class doesn't look it's synchronized properly at all. I'll take a shot at fixing this. I attached a patch that fixes the synchronization in PoolableConnectionFactory, but the deadlock still persists. The problem is GenericObjectPool.borrowObject() is synchronized so when it needs to makeObject that method is called while the synchronized block is held. I think this would take major surgery to make GenericObjectPool not perform this way. Thats what I feared. Thanks for looking in any case. I think the way to solve this is to write a new pool implementation that is much more async. This easier with the Java5 concurrent packages, but still quite tricky. Yes, and at least for dbcp 1.3, I would prefer not to hop all the way to 1.5 required JDK level. I agree. I also wouldn't want to switch dbcp to a pool that hasn't been heavily tested first. I'll attempt to put together one in a few days. Regardless, I don't think this is something we should target for this release. Before writing another one, have a look at the compositepool package in pool head. Well, I got this email after hacking on one for about 6 hours. I the kind of person that needs to finish things I start, so I'm going to keep hacking on it. I will take a look at composite pool in 2.0 and assuming my version doesn't suck. I'll see if I can merge any of my good features into that code. In the end I may just end up wasting a lot of my time, but at least I'll learn how hard it is to write a good pool:) -dain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558368 - in /jakarta/commons/proper/configuration/trunk: src/java/org/apache/commons/configuration/DefaultConfigurationBuilder.java src/test/org/apache/commons/configuration/TestDefaultCo
Author: oheger
Date: Sat Jul 21 12:00:51 2007
New Revision: 558368
URL: http://svn.apache.org/viewvc?view=revrev=558368
Log:
CONFIGURATION-285: DefaultConfigurationBuilder now fires an error event when an
optional configuration source could not be loaded.
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/DefaultConfigurationBuilder.java
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/TestDefaultConfigurationBuilder.java
jakarta/commons/proper/configuration/trunk/xdocs/changes.xml
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/DefaultConfigurationBuilder.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/DefaultConfigurationBuilder.java?view=diffrev=558368r1=558367r2=558368
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/DefaultConfigurationBuilder.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/DefaultConfigurationBuilder.java
Sat Jul 21 12:00:51 2007
@@ -30,10 +30,12 @@
import org.apache.commons.configuration.beanutils.BeanHelper;
import org.apache.commons.configuration.beanutils.DefaultBeanFactory;
import org.apache.commons.configuration.beanutils.XMLBeanDeclaration;
+import org.apache.commons.configuration.event.ConfigurationErrorListener;
import org.apache.commons.configuration.tree.ConfigurationNode;
import org.apache.commons.configuration.tree.DefaultExpressionEngine;
import org.apache.commons.configuration.tree.OverrideCombiner;
import org.apache.commons.configuration.tree.UnionCombiner;
+import org.apache.commons.logging.LogFactory;
/**
* p
@@ -120,7 +122,11 @@
* tr
* td valign=topcodeconfig-optional/code/td
* tdDeclares a configuration as optional. This means that errors that occur
- * when creating the configuration are silently ignored./td
+ * when creating the configuration are ignored. (However
+ * code[EMAIL PROTECTED] ConfigurationErrorListener}/codes registered at
the builder
+ * instance will get notified about this error: they receive an event of type
+ * codeEVENT_ERR_LOAD_OPTIONAL/code. The key property of this event
contains
+ * the name of the optional configuration source that caused this
problem.)/td
* /tr
* /table
* /p
@@ -178,6 +184,12 @@
.getName()
+ /ADDITIONAL_CONFIG;
+/**
+ * Constant for the type of error events caused by optional configurations
+ * that cannot be loaded.
+ */
+public static final int EVENT_ERR_LOAD_OPTIONAL = 51;
+
/** Constant for the name of the configuration bean factory. */
static final String CONFIG_BEAN_FACTORY_NAME =
DefaultConfigurationBuilder.class
.getName()
@@ -329,6 +341,8 @@
super();
providers = new HashMap();
registerDefaultProviders();
+setLogger(LogFactory.getLog(getClass()));
+addErrorLogListener(); // log errors per default
}
/**
@@ -1061,6 +1075,12 @@
}
else
{
+// Notify registered error listeners
+decl.getConfigurationBuilder().fireError(
+EVENT_ERR_LOAD_OPTIONAL,
+decl.getConfiguration().getString(ATTR_NAME), null,
+ex);
+
if (decl.isForceCreate())
{
try
Modified:
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/TestDefaultConfigurationBuilder.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/TestDefaultConfigurationBuilder.java?view=diffrev=558368r1=558367r2=558368
==
---
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/TestDefaultConfigurationBuilder.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/test/org/apache/commons/configuration/TestDefaultConfigurationBuilder.java
Sat Jul 21 12:00:51 2007
@@ -31,8 +31,7 @@
* Test class for DefaultConfigurationBuilder.
*
* @author Oliver Heger
- * @version $Id: TestDefaultConfigurationBuilder.java 384601 2006-03-09
- * 20:22:58Z oheger $
+ * @version $Id$
*/
public class TestDefaultConfigurationBuilder extends TestCase
{
@@ -70,6 +69,7 @@
System.setProperty(test_file_xml, test.xml);
System.setProperty(test_file_combine, testcombine1.xml);
factory = new DefaultConfigurationBuilder();
+factory.clearErrorListeners(); // avoid exception messages
}
/**
@@ -401,6 +401,16 @@
}
/**
+ * Tests whether a
[jira] Resolved: (CONFIGURATION-285) configuration fileName=local-configuration.xml config-optional=true / does not report parsing errors in local-configuration.xml
[ https://issues.apache.org/jira/browse/CONFIGURATION-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Heger resolved CONFIGURATION-285. Resolution: Fixed DefaultConfigurationBuilder now fires an error event when loading of an optional configuration source fails. If I understand this request correctly, you want to distinguish between cases where an optional configuration cannot be found and where it is present, but loading it causes an error. However this is not possible: Being present is specific for file-based configurations, but an optional configuration could be anything, e.g. a JNDI or database configuration. How could we decide, based on the thrown exceptions, whether the current problem was caused by a non-available configuration source or by a source that is available, but cannot be accessed because of an internal error? With the error listener mechanism you can hook into the process of loading the declared configuration sources. If an error occurs, you are notified and can make this decision yourself based on any criteria suitable for your concrete application and use case. configuration fileName=local-configuration.xml config-optional=true / does not report parsing errors in local-configuration.xml - Key: CONFIGURATION-285 URL: https://issues.apache.org/jira/browse/CONFIGURATION-285 Project: Commons Configuration Issue Type: Bug Affects Versions: 1.4 Reporter: Thorbjørn Ravn Andersen Assignee: Oliver Heger Fix For: 1.5 I'm trying to build a configuration system to be shared between our Java applications. I therefore want to have optional configurations included from the main configuration file read by DefaultConfigurationBuilder configuration fileName=local-configuration.xml config-optional=true / I have found that if the sub-configuration file is invalid the error is silently ignored. The same without config-options=true results in a ConfigurationException to be thrown (which wraps a ConfigurationRuntimeException which wraps the ConfigurationException which wraps the SAXException). I believe that the behaviour is incorrect. The sub-configuration file should be skipped if not found, but any errors found when parsing the existing file should be logged. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DBCP] close issues
On 7/21/07, Dain Sundstrom [EMAIL PROTECTED] wrote: On Jul 20, 2007, at 10:15 PM, Phil Steitz wrote: On 7/20/07, Dain Sundstrom [EMAIL PROTECTED] wrote: On Jul 20, 2007, at 11:26 AM, Dain Sundstrom wrote: I think this will require a patch to pooling (documented in DBCP-221). What are the plans for pooling? This is a tiny change so we could do a pool 1.3.1 or 1.4 release. Alternatively, we could wait until DBCP 1.4 (and the next pool release) to address this issue. I am fine waiting to DBCP 1.4, since unless we are talking about different things, this really amounts to a significant change to both dbcp and pool. If what we want is to *always* track open connections and have the lingering close apply to the active (i.e. checked out) as well as idle connections, we need to follow through on what looks like it was the original plan of moving AbandonedObjectPool to pool and use this _all the time_ in place of GenericObjectPool, which is really just an idle object pool (maintains no references to borrowed objects). I think there are two features here also. The first is a lingering close where we close the data source along with all idle connection. Then as the checked out connections are returned to the pool, we destroy them instead of putting them in a closed pool. The second feature is a force close which as you pointed out requires tracking of active connection. After looking at the pooling code, I think that will take a lot of work to implement with the current code. Agreed. Let's focus on getting dbcp 1.3 out with current (incomplete) lifecycle semantics supported by pool 1.3 and postpone major surgery for now. We should open a pool JIRA at some point, though, summarizing the need for full lifecycle support. In any case, we need to get a pool release out ASAP since pool 1.3 introduced some bugs that are causing problems (see for example POOL-97) since dbcp started using this version. Synchronization was increased in pool 1.3 as well. The hang here is lack of volunteer time and difficulty getting into the codebase. I have only recently started working on the pool code base. The compositepool package includes an alternative impl that we have been thinking about as a pool 2.0. The plan that I proposed a while back (http://www.mail-archive.com/commons-dev@jakarta.apache.org/ msg94027.html) was to push out a pool 1.3.1 patch release fixing POOL-97 (when reviewing the patch there, remember that dbcp statement pooling can create quite a few pools) and other bugs fixed since 1.3 and have DBCP 1.3 depend on that, both fully backward compatible with current versions. I still think we should do that. I can handle the RM duty for both of these and close a couple more of the pool bugs, but what we need to speed things up is more eyeballs validating and testing and contributing - and applying - patches. I'll try to review the patch. If we do do a 1.3.1, I think we should change GOP and GKOP to destroy objects returned to the pool after the pool is closed. Otherwise you end up with stuck objects in a closed pool. Its not quite that bad now; but the returning orphans do not get closed on return. What happens now is that the GOP throws IllegalStateException when you try to return an object (or perform any other operation) on a closed pool. We could include a patch in pool 1.3.1 to passivate and destroy a returning orphan before throwing the IllegalStateException, taking a baby step toward better lifeclycle management. Since the pool does not hold references to these orphans once its closed, I am not sure how big a problem this is in general; though certainly for dbcp, the underlying physical connections do not get closed right away in this case. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558377 - /jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java
Author: psteitz
Date: Sat Jul 21 13:19:21 2007
New Revision: 558377
URL: http://svn.apache.org/viewvc?view=revrev=558377
Log:
Added warning in GenericObjectPool returnObject javadoc about
dangers of multiple returns on same object.
JIRA: DBCP-94
Modified:
jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java
Modified:
jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java?view=diffrev=558377r1=558376r2=558377
==
---
jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java
(original)
+++
jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java
Sat Jul 21 13:19:21 2007
@@ -95,7 +95,7 @@
* p
* Optionally, one may configure the pool to examine and possibly evict
objects as they
* sit idle in the pool. This is performed by an idle object eviction
thread, which
- * runs asychronously. The idle object eviction thread may be configured
using the
+ * runs asynchronously. The idle object eviction thread may be configured
using the
* following attributes:
* ul
* li
@@ -958,6 +958,16 @@
return _pool.size();
}
+/**
+ * [EMAIL PROTECTED]
+ * pstrongNote: /strong There is no guard to prevent an object
+ * being returned to the pool multiple times. Clients are expected to
+ * discard references to returned objects and ensure that an object is not
+ * returned to the pool multiple times in sequence (i.e., without being
+ * borrowed again between returns). Violating this contract will result in
+ * the same object appearing multiple times in the pool and pool counters
+ * (numActive, numIdle) returning incorrect values./p
+ */
public synchronized void returnObject(Object obj) throws Exception {
try {
addObjectToPool(obj, true);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (POOL-94) GenericObjectPool allows checking in of previously checked in objects
[ https://issues.apache.org/jira/browse/POOL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved POOL-94. - Resolution: Won't Fix Javadoc has been updated to include a warning. GenericObjectPool allows checking in of previously checked in objects - Key: POOL-94 URL: https://issues.apache.org/jira/browse/POOL-94 Project: Commons Pool Issue Type: New Feature Affects Versions: 1.3 Environment: JDK 1.4.2, web application running under Tomcat 5.0.25 Reporter: Tim McCollough Priority: Minor I am using GenericObjectPool to store a pool of socket connections. While debugging the application I noticed that the result of GetNumActive() was becoming more and more negative, while the GetNumIldle() count was ever increasing. Further debug showed that my application was returning the same connection more than once and the GenericObjectPool implementation accepted the return silently and decremented the active count and incremented the idle count. I don't object to GenericObjectPool allowing multiple returns on the same object, but the bookkeeping problem will lead to bad things happening in the pool management code. I am investigating what it would take to fix GenericObjectPool but since I am inexperienced in these commons projects I don't know what I should do from here. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn propchange: r558377 - svn:log
Author: psteitz Revision: 558377 Modified property: svn:log Modified: svn:log at Sat Jul 21 13:27:21 2007 -- --- svn:log (original) +++ svn:log Sat Jul 21 13:27:21 2007 @@ -1,4 +1,4 @@ Added warning in GenericObjectPool returnObject javadoc about dangers of multiple returns on same object. -JIRA: DBCP-94 +JIRA: POOL-94 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558393 - /jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
Author: psteitz
Date: Sat Jul 21 16:43:04 2007
New Revision: 558393
URL: http://svn.apache.org/viewvc?view=revrev=558393
Log:
Added test to verify that maxWait = 0 means immediate failure for
PerUserPoolDataSource, per javadoc (different from BasicDataSource).
Modified:
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
Modified:
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java?view=diffrev=558393r1=558392r2=558393
==
---
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
(original)
+++
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
Sat Jul 21 16:43:04 2007
@@ -305,6 +305,23 @@
}
}
+/**
+ * Verify that defaultMaxWait = 0 means immediate failure when
+ * pool is exhausted.
+ */
+public void testMaxWaitZero() throws Exception {
+PerUserPoolDataSource tds = (PerUserPoolDataSource) ds;
+tds.setDefaultMaxWait(0);
+tds.setPerUserMaxActive(u1, new Integer(1));
+Connection conn = tds.getConnection(u1, p1);
+try {
+Connection conn2 = tds.getConnection(u1, p1);
+fail(Expecting Pool Exhausted exception);
+} catch (SQLException ex) {
+// expected
+}
+}
+
public void testPerUserMethods() throws Exception {
PerUserPoolDataSource tds = (PerUserPoolDataSource) ds;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558394 - /jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/BasicDataSource.java
Author: psteitz Date: Sat Jul 21 16:46:27 2007 New Revision: 558394 URL: http://svn.apache.org/viewvc?view=revrev=558394 Log: Fixed javadoc to match behavior when BasicDataSource maxWait is 0 (blocks indefinitely). JIRA: POOL-232 Modified: jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/BasicDataSource.java Modified: jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/BasicDataSource.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/BasicDataSource.java?view=diffrev=558394r1=558393r2=558394 == --- jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/BasicDataSource.java (original) +++ jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/BasicDataSource.java Sat Jul 21 16:46:27 2007 @@ -341,7 +341,7 @@ /** * The maximum number of milliseconds that the pool will wait (when there * are no available connections) for a connection to be returned before - * throwing an exception, or -1 to wait indefinitely. + * throwing an exception, or = 0 to wait indefinitely. */ protected long maxWait = GenericObjectPool.DEFAULT_MAX_WAIT; @@ -349,7 +349,8 @@ * pReturns the maximum number of milliseconds that the pool will wait * for a connection to be returned before throwing an exception. * /p - * pReturns -1 if the pool is set to wait indefinitely./p + * pA value less than or equal to zero means the pool is set to wait + * indefinitely./p * * @return the maxWait property value */ @@ -358,7 +359,10 @@ } /** - * Sets the maxWait property. + * pSets the maxWait property. + * /p + * pUse -1 to make the pool wait indefinitely. + * /p * * @param maxWait the new value for maxWait * @see #getMaxWait() - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (DBCP-232) maxWait = 0 waits indefinitely too, not only maxWait = -1
[ https://issues.apache.org/jira/browse/DBCP-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-232. -- Resolution: Fixed Javadoc fix committed in r558394. Thanks for reporting thi maxWait = 0 waits indefinitely too, not only maxWait = -1 -- Key: DBCP-232 URL: https://issues.apache.org/jira/browse/DBCP-232 Project: Commons Dbcp Issue Type: Improvement Environment: all Reporter: Peter Welkenbach Priority: Critical the documentation describes the maxWait property as: The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception, or -1 to wait indefinitely. this seems to be wrong. Compared to the source code it should be for a connection to be returned before throwing an exception, or -1 or 0 to wait indefinitely. in the source code of class GenericObjectPool the comparison is maxWait = 0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558397 - in /jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl: GenericKeyedObjectPool.java GenericObjectPool.java
Author: psteitz Date: Sat Jul 21 16:49:26 2007 New Revision: 558397 URL: http://svn.apache.org/viewvc?view=revrev=558397 Log: Fixed javadoc to match behavior when maxWait is 0 (blocks indefinitely if exhausted action is block). Modified: jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericKeyedObjectPool.java jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java Modified: jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericKeyedObjectPool.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericKeyedObjectPool.java?view=diffrev=558397r1=558396r2=558397 == --- jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericKeyedObjectPool.java (original) +++ jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericKeyedObjectPool.java Sat Jul 21 16:49:26 2007 @@ -524,7 +524,7 @@ * [EMAIL PROTECTED] #setWhenExhaustedAction when exhausted action} is * [EMAIL PROTECTED] #WHEN_EXHAUSTED_BLOCK}. * - * When less than 0, the [EMAIL PROTECTED] #borrowObject} method + * When less than or equal to 0, the [EMAIL PROTECTED] #borrowObject} method * may block indefinitely. * * @return the maximum number of milliseconds borrowObject will block. @@ -543,7 +543,7 @@ * [EMAIL PROTECTED] #setWhenExhaustedAction when exhausted action} is * [EMAIL PROTECTED] #WHEN_EXHAUSTED_BLOCK}. * - * When less than 0, the [EMAIL PROTECTED] #borrowObject} method + * When less than or equal to 0, the [EMAIL PROTECTED] #borrowObject} method * may block indefinitely. * * @param maxWait the maximum number of milliseconds borrowObject will block or negative for indefinitely. @@ -1596,7 +1596,7 @@ * [EMAIL PROTECTED] #getWhenExhaustedAction when exhausted action} is * [EMAIL PROTECTED] #WHEN_EXHAUSTED_BLOCK}. * - * When less than 0, the [EMAIL PROTECTED] #borrowObject} method + * When less than or equal to 0, the [EMAIL PROTECTED] #borrowObject} method * may block indefinitely. * * @see #setMaxWait Modified: jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java URL: http://svn.apache.org/viewvc/jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java?view=diffrev=558397r1=558396r2=558397 == --- jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java (original) +++ jakarta/commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java Sat Jul 21 16:49:26 2007 @@ -511,7 +511,7 @@ * [EMAIL PROTECTED] #setWhenExhaustedAction when exhausted action} is * [EMAIL PROTECTED] #WHEN_EXHAUSTED_BLOCK}. * - * When less than 0, the [EMAIL PROTECTED] #borrowObject} method + * When less than or equal to 0, the [EMAIL PROTECTED] #borrowObject} method * may block indefinitely. * * @return maximum number of milliseconds to block when borrowing an object. @@ -530,7 +530,7 @@ * [EMAIL PROTECTED] #setWhenExhaustedAction when exhausted action} is * [EMAIL PROTECTED] #WHEN_EXHAUSTED_BLOCK}. * - * When less than 0, the [EMAIL PROTECTED] #borrowObject} method + * When less than or equal to 0, the [EMAIL PROTECTED] #borrowObject} method * may block indefinitely. * * @param maxWait maximum number of milliseconds to block when borrowing an object. @@ -1292,7 +1292,7 @@ * [EMAIL PROTECTED] #getWhenExhaustedAction when exhausted action} is * [EMAIL PROTECTED] #WHEN_EXHAUSTED_BLOCK}. * - * When less than 0, the [EMAIL PROTECTED] #borrowObject} method + * When less than or equal to 0, the [EMAIL PROTECTED] #borrowObject} method * may block indefinitely. * * @see #setMaxWait - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558398 - /jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
Author: psteitz
Date: Sat Jul 21 16:53:32 2007
New Revision: 558398
URL: http://svn.apache.org/viewvc?view=revrev=558398
Log:
Added missing close.
Modified:
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
Modified:
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java?view=diffrev=558398r1=558397r2=558398
==
---
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
(original)
+++
jakarta/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/datasources/TestPerUserPoolDataSource.java
Sat Jul 21 16:53:32 2007
@@ -320,6 +320,7 @@
} catch (SQLException ex) {
// expected
}
+conn.close();
}
public void testPerUserMethods() throws Exception {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONFIGURATION-284) ability to read OS environment variables
[
https://issues.apache.org/jira/browse/CONFIGURATION-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514450
]
Vasily Ivanov commented on CONFIGURATION-284:
-
Thanks Oliver, feel free to add that code anywhere you want.
ability to read OS environment variables
Key: CONFIGURATION-284
URL: https://issues.apache.org/jira/browse/CONFIGURATION-284
Project: Commons Configuration
Issue Type: New Feature
Components: Interpolation
Reporter: Aksel Schmidt
Priority: Minor
Attachments: EnvironmentConfiguration.java
suggestion:
interpolation with system environment, i.e.
${sys:user.name} reads from systemproperties (as of today)
${sysenv:TEMP} reads from OS environment
these can be parsed from a supported set of OS's - windows read from a set in
a cmd /c, unix/linux from an env etc. (just once on demand)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r558450 - in /jakarta/commons/proper/math/trunk: src/java/org/apache/commons/math/distribution/NormalDistributionImpl.java src/test/org/apache/commons/math/distribution/NormalDistributionT
Author: psteitz
Date: Sat Jul 21 19:33:08 2007
New Revision: 558450
URL: http://svn.apache.org/viewvc?view=revrev=558450
Log:
Modified NormalDistributionImpl.cumulativeProbablity to catch
MaxIterationsExceededException and return 0 or 1, resp. if the argument
is more than 20 standard deviations from the mean.
JIRA: MATH-167
Modified:
jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/distribution/NormalDistributionImpl.java
jakarta/commons/proper/math/trunk/src/test/org/apache/commons/math/distribution/NormalDistributionTest.java
jakarta/commons/proper/math/trunk/xdocs/changes.xml
Modified:
jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/distribution/NormalDistributionImpl.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/distribution/NormalDistributionImpl.java?view=diffrev=558450r1=558449r2=558450
==
---
jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/distribution/NormalDistributionImpl.java
(original)
+++
jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/distribution/NormalDistributionImpl.java
Sat Jul 21 19:33:08 2007
@@ -20,6 +20,7 @@
import java.io.Serializable;
import org.apache.commons.math.MathException;
+import org.apache.commons.math.MaxIterationsExceededException;
import org.apache.commons.math.special.Erf;
/**
@@ -100,11 +101,23 @@
* For this disbution, X, this method returns P(X lt; codex/code).
* @param x the value at which the CDF is evaluated.
* @return CDF evaluted at codex/code.
- * @throws MathException if the algorithm fails to converge.
+ * @throws MathException if the algorithm fails to converge; unless
+ * x is more than 20 standard deviations from the mean, in which case the
+ * convergence exception is caught and 0 or 1 is returned.
*/
public double cumulativeProbability(double x) throws MathException {
-return 0.5 * (1.0 + Erf.erf((x - mean) /
-(standardDeviation * Math.sqrt(2.0;
+try {
+return 0.5 * (1.0 + Erf.erf((x - mean) /
+(standardDeviation * Math.sqrt(2.0;
+} catch (MaxIterationsExceededException ex) {
+if (x (mean - 20 * standardDeviation)) { // JDK 1.5 blows at 38
+return 0.0d;
+} else if (x (mean + 20 * standardDeviation)) {
+return 1.0d;
+} else {
+throw ex;
+}
+}
}
/**
Modified:
jakarta/commons/proper/math/trunk/src/test/org/apache/commons/math/distribution/NormalDistributionTest.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/math/trunk/src/test/org/apache/commons/math/distribution/NormalDistributionTest.java?view=diffrev=558450r1=558449r2=558450
==
---
jakarta/commons/proper/math/trunk/src/test/org/apache/commons/math/distribution/NormalDistributionTest.java
(original)
+++
jakarta/commons/proper/math/trunk/src/test/org/apache/commons/math/distribution/NormalDistributionTest.java
Sat Jul 21 19:33:08 2007
@@ -120,4 +120,26 @@
// Expected
}
}
+
+/**
+ * Check to make sure top-coding of extreme values works correctly.
+ * Verifies fix for JIRA MATH-167
+ */
+public void testExtremeValues() throws Exception {
+NormalDistribution distribution = (NormalDistribution)
getDistribution();
+distribution.setMean(0);
+distribution.setStandardDeviation(1);
+for (int i = 0; i 100; i+=5) { // make sure no convergence exception
+double lowerTail = distribution.cumulativeProbability((double)-i);
+double upperTail = distribution.cumulativeProbability((double) i);
+if (i 10) { // make sure not top-coded
+assertTrue(lowerTail 0.0d);
+assertTrue(upperTail 1.0d);
+}
+else { // make sure top coding not reversed
+assertTrue(lowerTail 0.1);
+assertTrue(upperTail 0.9);
+}
+}
+ }
}
Modified: jakarta/commons/proper/math/trunk/xdocs/changes.xml
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/math/trunk/xdocs/changes.xml?view=diffrev=558450r1=558449r2=558450
==
--- jakarta/commons/proper/math/trunk/xdocs/changes.xml (original)
+++ jakarta/commons/proper/math/trunk/xdocs/changes.xml Sat Jul 21 19:33:08 2007
@@ -87,6 +87,11 @@
action dev=psteitz type=update issue=MATH-160 due-to Matthias
Hummel
Added two sample (binned comparison) ChiSquare test.
/action
+ action dev=psteitz type=fix issue=MATH-167
+Modified NormalDistributionImpl.cumulativeProbablity to catch
+
[jira] Commented: (MATH-167) ConvergenceException in normal CDF
[ https://issues.apache.org/jira/browse/MATH-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514453 ] Phil Steitz commented on MATH-167: -- Fixed for nomal distribution in r558450. Leaving open because we should look at other distributions before closing. ConvergenceException in normal CDF -- Key: MATH-167 URL: https://issues.apache.org/jira/browse/MATH-167 Project: Commons Math Issue Type: Bug Reporter: Mikko Kauppila Priority: Minor Fix For: 1.2 NormalDistributionImpl::cumulativeProbability(double x) throws ConvergenceException if x deviates too much from the mean. For example, when x=+/-100, mean=0, sd=1. Of course the value of the CDF is hard to evaluate in these cases, but effectively it should be either zero or one. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MATH-167) ConvergenceException in normal CDF
[ https://issues.apache.org/jira/browse/MATH-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated MATH-167: - Fix Version/s: 1.2 ConvergenceException in normal CDF -- Key: MATH-167 URL: https://issues.apache.org/jira/browse/MATH-167 Project: Commons Math Issue Type: Bug Reporter: Mikko Kauppila Priority: Minor Fix For: 1.2 NormalDistributionImpl::cumulativeProbability(double x) throws ConvergenceException if x deviates too much from the mean. For example, when x=+/-100, mean=0, sd=1. Of course the value of the CDF is hard to evaluate in these cases, but effectively it should be either zero or one. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
