[BUILD] trunk: Failed for Revision: 1034954
Geronimo Revision: 1034954 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 51 minutes 33 seconds [INFO] Finished at: Sun Nov 14 03:57:31 EST 2010 [INFO] Final Memory: 474M/1006M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/logs-0300-tomcat/ Running TestSuite Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 10.308 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.718 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/logs-0300-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.509 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/samples-0300.log Build status: FAILED
[BUILD] branches/2.2: Failed for Revision: 1034991
Geronimo Revision: 1034991 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101114/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101114/unit-test-reports from the specified remote repositories: openejb-staging (https://repository.apache.org/content/repositories/orgapacheopenejb-005/), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots), txmanager-staging (https://repository.apache.org/content/repositories/orgapachegeronimo-037/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: openejb-staging (https://repository.apache.org/content/repositories/orgapacheopenejb-005/), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots), txmanager-staging (https://repository.apache.org/content/repositories/orgapachegeronimo-037/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: openejb-staging (https://repository.apache.org/content/repositories/orgapacheopenejb-005
[BUILD] trunk: Failed for Revision: 1034998
Geronimo Revision: 1034998 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/build-0900.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 38 minutes 52 seconds [INFO] Finished at: Sun Nov 14 09:44:47 EST 2010 [INFO] Final Memory: 480M/1007M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/logs-0900-tomcat/ Running TestSuite Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 9.127 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.545 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/logs-0900-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.568 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/samples-0900.log Build status: FAILED
[BUILD] branches/2.2: Failed for Revision: 1035041
Geronimo Revision: 1035041 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101114/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101114/unit-test-reports from the specified remote repositories: openejb-staging (https://repository.apache.org/content/repositories/orgapacheopenejb-005/), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots), txmanager-staging (https://repository.apache.org/content/repositories/orgapachegeronimo-037/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: openejb-staging (https://repository.apache.org/content/repositories/orgapacheopenejb-005/), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots), txmanager-staging (https://repository.apache.org/content/repositories/orgapachegeronimo-037/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: openejb-staging (https://repository.apache.org/content/repositories/orgapacheopenejb-005
[BUILD] trunk: Failed for Revision: 1035058
Geronimo Revision: 1035058 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 37 minutes 45 seconds [INFO] Finished at: Sun Nov 14 15:43:46 EST 2010 [INFO] Final Memory: 480M/1007M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/logs-1500-tomcat/ Running TestSuite Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 8.582 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.576 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/logs-1500-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.591 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20101114/samples-1500.log Build status: FAILED
[BUILD] branches/2.2: Failed for Revision: 1035108
Geronimo Revision: 1035108 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101114/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101114/unit-test-reports from the specified remote repositories: txmanager-staging (https://repository.apache.org/content/repositories/orgapachegeronimo-037/), openejb-staging (https://repository.apache.org/content/repositories/orgapacheopenejb-005/), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: txmanager-staging (https://repository.apache.org/content/repositories/orgapachegeronimo-037/), openejb-staging (https://repository.apache.org/content/repositories/orgapacheopenejb-005/), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.2.1 -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: txmanager-staging (https://repository.apache.org/content/repositories/orgapachegeronimo-037
Re: [VOTE] release JASPI component 1.1.1
+1 2010/11/12 Donald Woods dwo...@apache.org +1 Donald On 11/9/10 7:31 AM, Rick McGuire wrote: This is a bug fix release to fix a problem with the JASPI OSGi integration: https://issues.apache.org/jira/browse/GERONIMO-5656 The components up for vote are: org/apache/geronimo/components/geronimo-jaspi/1.1.1/geronimo-jaspi-1.1.1-source-release.zip org/apache/geronimo/components/geronimo-jaspi/1.1.1/geronimo-jaspi-1.1.1-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachegeronimo-049/ The source repo is: https://svn.apache.org/repos/asf/geronimo/components/jaspi/tags/geronimo-jaspi-1.1.1 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Rick -- Ivan
Re: [VOTE] release EJB 3.1 spec version 1.0.2
+1 2010/11/12 Donald Woods dwo...@apache.org +1 Donald On 11/9/10 6:50 AM, Rick McGuire wrote: This is a bug fix release to fix a small spec compliance issue The components up for vote are: org/apache/geronimo/specs/geronimo-ejb_3.1_spec/1.0.2/geronimo-ejb_3.1_spec-1.0.2-source-release.zip org/apache/geronimo/specs/geronimo-ejb_3.1_spec/1.0.2/geronimo-ejb_3.1_spec-1.0.2-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachegeronimo-047/ The source repo is: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-ejb_3.1_spec-1.0.2 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Rick -- Ivan
Re: [VOTE] release EL 2.2 spec version 1.0.1
+1 2010/11/12 Donald Woods dwo...@apache.org +1 Donald On 11/9/10 7:13 AM, Rick McGuire wrote: This is a bug fix release to fix a couple of problems EL spec implementation. The components up for vote are: org/apache/geronimo/specs/geronimo-el_2.2_spec/1.0.1/geronimo-el_2.2_spec-1.0.1-source-release.zip org/apache/geronimo/specs/geronimo-el_2.2_spec/1.0.1/geronimo-el_2.2_spec-1.0.1-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachegeronimo-048/ The source repo is: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_2.2_spec-1.0.1 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Rick -- Ivan
applying for authority to change JIRA status
Hi I wish to be granted the authority to change JIRA status as I would like to help on the project. My username is mao. Best wishes, MAO Jia
Re: applying for authority to change JIRA status
Hi, You should be all set. --kevan On Nov 14, 2010, at 9:00 PM, Jia Mao wrote: Hi I wish to be granted the authority to change JIRA status as I would like to help on the project. My username is mao. Best wishes, MAO Jia
Jira - geronimo-administrators
I've created a geronimo-administrators group on Jira. Members of this group should be able to administer the Geronimo Jira project. Any PMC volunteers to help out? We don't want too big of a group. So, 2 or 3 people should do... --kevan
Re: Jira - geronimo-administrators
Please add me. thanks! Forrest On Mon, Nov 15, 2010 at 10:35 AM, Kevan Miller kevan.mil...@gmail.comwrote: I've created a geronimo-administrators group on Jira. Members of this group should be able to administer the Geronimo Jira project. Any PMC volunteers to help out? We don't want too big of a group. So, 2 or 3 people should do... --kevan
[jira] Commented: (GERONIMO-5655) switch to tomcat standard taglibs
[ https://issues.apache.org/jira/browse/GERONIMO-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12931975#action_12931975 ] Rex Wang commented on GERONIMO-5655: commit to trunk At revision: 1035140 -Rex switch to tomcat standard taglibs - Key: GERONIMO-5655 URL: https://issues.apache.org/jira/browse/GERONIMO-5655 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 1. push tomcat community to release their jstl implementation 2. persuade tomcat community to bundle-ify their jstl implementation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5688) ContextNotActiveException while accessing a JSF application without using web beans components
ContextNotActiveException while accessing a JSF application without using web beans components -- Key: GERONIMO-5688 URL: https://issues.apache.org/jira/browse/GERONIMO-5688 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: OpenWebBeans Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 Please check the thread http://apache-geronimo.328035.n3.nabble.com/OWB-is-always-enabled-even-no-web-beans-in-the-web-application-td1881240.html#a1881240 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: OWB is always enabled even no web beans in the web application
I have created a jira https://issues.apache.org/jira/browse/GERONIMO-5688for this. Also, another jira https://issues.apache.org/jira/browse/GERONIMO-5685 is also related to openwebbeans integration, and a patch is attached. David, when avaible, help to review the patch, thanks. 2010/11/13 Mark Struberg strub...@yahoo.de I'd say we should not enable OWB support if non of these beans.xml files are present /WEB-INF/beans.xml of one web app /WEB-INF/classes/META-INF/beans.xml /WEB-INF/lib/*.jar containing a META-INF/beans.xml LieGrue, strub --- On Fri, 11/12/10, Shawn Jiang genspr...@gmail.com wrote: From: Shawn Jiang genspr...@gmail.com Subject: Re: OWB is always enabled even no web beans in the web application To: dev@geronimo.apache.org Date: Friday, November 12, 2010, 9:24 AM Most of current BV tck failures are also regressions of this. Some BV tck war can't be deployed when OWB is scaning it's classes. The service J2EEApplication=null,j2eeType=WebModule,name=default/org.hibernate.jsr303.tck.tests.xmlconfiguration.XmlConfigurationTest/1289 552829745/war did not start because java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy java.lang.RuntimeException: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy at org.apache.webbeans.portable.AnnotatedElementFactory.newAnnotatedType(AnnotatedElementFactory.java:141) at org.apache.webbeans.config.BeansDeployer.deployFromClassPath(BeansDeployer.java:472) at org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:170) at org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:124) at org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:78) at org.apache.geronimo.openwebbeans.OpenWebBeansWebInitializer.init(OpenWebBeansWebInitializer.java:55) at org.apache.geronimo.tomcat.GeronimoStandardContext.setContextProperties(GeronimoStandardContext.java:233) at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:317) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:566) On Fri, Nov 12, 2010 at 1:06 AM, David Jencks david_jen...@yahoo.com wrote: There's definitely a bug possibly several. I'd like to know exactly what isn't getting initialized that causes this error. On the other hand if there's no beans.xml we really shouldn't be installing any webbeans functionality. On the third hand :-) we don't really know how much of an ee application is supposed to be covered by a single owb context so I'm unsure of some details about how to decide when to install owb stuff. I'm hoping to catch pete muir to ask him about this... thanks david jencks On Nov 10, 2010, at 11:57 PM, Ivan wrote: Hi, I found some jsf and ejb cases failed with the exception below, and apparently, no web beans is used in those application, suppose that all the OWB related codes should not be executed. After checking the integration codes, I found something like in the OpenWebBeansWebInitializer : --- servletContext.setAttribute(OpenWebBeansConfiguration.PROPERTY_OWB_APPLICATION, true); --- Seems that OWB uses this to identify whether the current application is an OWB application. But the set action is always executed even no web bean exists in the application. So is there a bug here ? thanks. 2010-11-11 14:35:46,515 ERROR [ErrorPageWriter] An exception occurred javax.faces.FacesException: javax.enterprise.context.ContextNotActiveException: WebBeans context with scope type annotation @RequestScoped does not exist within current thread at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241) at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:191) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:725) at
[jira] Created: (GERONIMO-5689) Derby connection failed when enabled derby system level authentication
Derby connection failed when enabled derby system level authentication -- Key: GERONIMO-5689 URL: https://issues.apache.org/jira/browse/GERONIMO-5689 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: databases Affects Versions: 2.1.7, 2.2.1 Environment: ubuntu 10.04.1 LTS sun java 1.5.0_22 Reporter: Forrest Xia Priority: Minor Consider this scenario: 1. User firstly disables derby authentication, then start the server and deploy an application which is using embedded derby database. The datasource deployment plan is like this: resourceadapter outbound-resourceadapter connection-definition connectionfactory-interfacejavax.sql.DataSource/connectionfactory-interface connectiondefinition-instance nameBankPool/name config-property-setting name=Driverorg.apache.derby.jdbc.EmbeddedDriver/config-property-setting config-property-setting name=UserNameapp/config-property-setting config-property-setting name=Passwordapp/config-property-setting config-property-setting name=ConnectionURLjdbc:derby:BankDB;create=true/config-property-setting connectionmanager local-transaction/ single-pool max-size10/max-size min-size0/min-size match-one/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter In the plan, user specifies an username and password. 2. Shutdown the server, enable derby authentication, and start the server again 3. Now the server cannot start successfullly, because this exception: Module 69/69 org.apache.geronimo.samples/bank-ear/2.1.1.4/car 2010-11-15 15:12:25,224 WARN [DerbyUserAuthenticator] User authentication failure (userName userPassword databaseName): app app BankDB 2010-11-15 15:12:25,240 ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for handle: nullManagedConnectionInfo: org.apache.geronimo.connector.outbound.managedconnectioni...@123288b. mc: null] javax.resource.spi.ResourceAllocationException: Unable to obtain physical connection to jdbc:derby:BankDB;create=true ... Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.samples/bank-ear/2.1.1.4/car failed to start due to the following reasons: The service J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.4/car,j2eeType=GBean,name=BankDBInit did not start because Connection authentication failure occurred. Reason: Invalid authentication.. I think this exception may cause by derby user is hard-coded in code to acquire server connection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5689) Derby connection failed when enabled derby system level authentication
[ https://issues.apache.org/jira/browse/GERONIMO-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5689: -- Attachment: bank-ear-2.1.1.4.ear The sample app is used to test. Derby connection failed when enabled derby system level authentication -- Key: GERONIMO-5689 URL: https://issues.apache.org/jira/browse/GERONIMO-5689 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: databases Affects Versions: 2.1.7, 2.2.1 Environment: ubuntu 10.04.1 LTS sun java 1.5.0_22 Reporter: Forrest Xia Priority: Minor Attachments: bank-ear-2.1.1.4.ear Consider this scenario: 1. User firstly disables derby authentication, then start the server and deploy an application which is using embedded derby database. The datasource deployment plan is like this: resourceadapter outbound-resourceadapter connection-definition connectionfactory-interfacejavax.sql.DataSource/connectionfactory-interface connectiondefinition-instance nameBankPool/name config-property-setting name=Driverorg.apache.derby.jdbc.EmbeddedDriver/config-property-setting config-property-setting name=UserNameapp/config-property-setting config-property-setting name=Passwordapp/config-property-setting config-property-setting name=ConnectionURLjdbc:derby:BankDB;create=true/config-property-setting connectionmanager local-transaction/ single-pool max-size10/max-size min-size0/min-size match-one/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter In the plan, user specifies an username and password. 2. Shutdown the server, enable derby authentication, and start the server again 3. Now the server cannot start successfullly, because this exception: Module 69/69 org.apache.geronimo.samples/bank-ear/2.1.1.4/car 2010-11-15 15:12:25,224 WARN [DerbyUserAuthenticator] User authentication failure (userName userPassword databaseName): app app BankDB 2010-11-15 15:12:25,240 ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for handle: nullManagedConnectionInfo: org.apache.geronimo.connector.outbound.managedconnectioni...@123288b. mc: null] javax.resource.spi.ResourceAllocationException: Unable to obtain physical connection to jdbc:derby:BankDB;create=true ... Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.samples/bank-ear/2.1.1.4/car failed to start due to the following reasons: The service J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.4/car,j2eeType=GBean,name=BankDBInit did not start because Connection authentication failure occurred. Reason: Invalid authentication.. I think this exception may cause by derby user is hard-coded in code to acquire server connection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Please test tranql connectors on java 1.5
I've released these artifacts david jencks On Nov 12, 2010, at 3:28 PM, David Jencks wrote: I've staged all the tranql stuff here: https://nexus.codehaus.org/content/repositories/orgtranql-023/ Unless someone reports problems I expect to promote this before monday. thanks david jencks On Nov 11, 2010, at 3:46 PM, David Jencks wrote: Hi Forrest and Johannes, Many thanks for the patches!. With Kevan's help I got java 1.5 running again on my mac and have pushed snapshots of everything. I'll allow a few hours for testing and push a release late tonight or early tomorrow morning PST. many thanks! david jencks On Nov 10, 2010, at 6:33 AM, Forrest Xia wrote: Hi Johannes, Thanks for this patch, and I just did a quick test, seems to me it works well with G 2.1.7 snapshot under java 5. To David, I attached two patches in TQL-22 and TQL-27, pls help review and commit them along with Johannes' patch into trunk, then we can roll out a tranql release for use. Let me know if anything I can help on the release. Forrest
[jira] Updated: (GERONIMO-5689) User-defined derby connection user name and password should be honored when enabling derby authentication
[ https://issues.apache.org/jira/browse/GERONIMO-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5689: -- Summary: User-defined derby connection user name and password should be honored when enabling derby authentication (was: Derby connection failed when enabled derby system level authentication) User-defined derby connection user name and password should be honored when enabling derby authentication - Key: GERONIMO-5689 URL: https://issues.apache.org/jira/browse/GERONIMO-5689 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: databases Affects Versions: 2.1.7, 2.2.1 Environment: ubuntu 10.04.1 LTS sun java 1.5.0_22 Reporter: Forrest Xia Priority: Minor Attachments: bank-ear-2.1.1.4.ear Consider this scenario: 1. User firstly disables derby authentication, then start the server and deploy an application which is using embedded derby database. The datasource deployment plan is like this: resourceadapter outbound-resourceadapter connection-definition connectionfactory-interfacejavax.sql.DataSource/connectionfactory-interface connectiondefinition-instance nameBankPool/name config-property-setting name=Driverorg.apache.derby.jdbc.EmbeddedDriver/config-property-setting config-property-setting name=UserNameapp/config-property-setting config-property-setting name=Passwordapp/config-property-setting config-property-setting name=ConnectionURLjdbc:derby:BankDB;create=true/config-property-setting connectionmanager local-transaction/ single-pool max-size10/max-size min-size0/min-size match-one/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter In the plan, user specifies an username and password. 2. Shutdown the server, enable derby authentication, and start the server again 3. Now the server cannot start successfullly, because this exception: Module 69/69 org.apache.geronimo.samples/bank-ear/2.1.1.4/car 2010-11-15 15:12:25,224 WARN [DerbyUserAuthenticator] User authentication failure (userName userPassword databaseName): app app BankDB 2010-11-15 15:12:25,240 ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for handle: nullManagedConnectionInfo: org.apache.geronimo.connector.outbound.managedconnectioni...@123288b. mc: null] javax.resource.spi.ResourceAllocationException: Unable to obtain physical connection to jdbc:derby:BankDB;create=true ... Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.samples/bank-ear/2.1.1.4/car failed to start due to the following reasons: The service J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.4/car,j2eeType=GBean,name=BankDBInit did not start because Connection authentication failure occurred. Reason: Invalid authentication.. I think this exception may cause by derby user is hard-coded in code to acquire server connection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
