[BUILD] branches/2.2: Failed for Revision: 1164988
Geronimo Revision: 1164988 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110904/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110904/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -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.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) 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.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -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.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] [Closed] (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller closed GERONIMO-4222. -- Resolution: Fixed Fix Version/s: (was: Wish List) There have been multiple fixes to our connector implementation. As noted by David and Radim, we appear to have gotten things right... > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Attachments: PGtrial.patch, before and after wasce restart.txt, > connector.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6142) add backup/restore capability to Derby portlet
[ https://issues.apache.org/jira/browse/GERONIMO-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096892#comment-13096892 ] Kevan Miller commented on GERONIMO-6142: That's a nice idea. Thanks for the suggestion! Any interest in submitting a patch for this? > add backup/restore capability to Derby portlet > -- > > Key: GERONIMO-6142 > URL: https://issues.apache.org/jira/browse/GERONIMO-6142 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.7 >Reporter: Radim Kolar > > Included Derby can be used for user applications. This is good thing because > you do not need to install and maintain external database for not much loaded > applications. But there is major problem with that use scenario. You can do > database backups only when you shutdown application server. > Because Derby database can do online backups, please modify Derby portlet to > allow administrator to do online backups (and restores) to/from specified > directory. It would be best if it can be done via Geronimo shell too and then > used in backup scripts. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6142) add backup/restore capability to Derby portlet
[ https://issues.apache.org/jira/browse/GERONIMO-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096902#comment-13096902 ] Radim Kolar commented on GERONIMO-6142: --- I do not have knowledge how to set-up eclipse development environment to develop G console portlets. Its simple to do for somebody who has already dev environment setup. Just add new button and link it to procedure similar to this http://db.apache.org/derby/docs/10.5/adminguide/cadminhubbkup01.html > add backup/restore capability to Derby portlet > -- > > Key: GERONIMO-6142 > URL: https://issues.apache.org/jira/browse/GERONIMO-6142 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.7 >Reporter: Radim Kolar > > Included Derby can be used for user applications. This is good thing because > you do not need to install and maintain external database for not much loaded > applications. But there is major problem with that use scenario. You can do > database backups only when you shutdown application server. > Because Derby database can do online backups, please modify Derby portlet to > allow administrator to do online backups (and restores) to/from specified > directory. It would be best if it can be done via Geronimo shell too and then > used in backup scripts. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] branches/2.2: Failed for Revision: 1165075
Geronimo Revision: 1165075 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110904/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110904/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -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.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) 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.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -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.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
Re: G 2.2.1/Tomcat throws Unable to decrypt on Mac OS X
On Sat, Sep 3, 2011 at 11:43 PM, Kevan Miller wrote: >So, you may want to start with a fresh install. That was it. I can't find out what made the installation broken, but once I removed and reinstalled it, Geronimo runs fine now. Thanks! Jacek -- Jacek Laskowski Java EE, functional languages and IBM WebSphere - http://blog.japila.pl Warszawa JUG conference = Confitura (formerly Javarsovia) :: http://confitura.pl
[BUILD] branches/2.2: Failed for Revision: 1165129
Geronimo Revision: 1165129 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110904/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110904/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), 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.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -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.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), 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.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -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.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
Re: [VOTE] Release Geronimo Forked Tomcat 7.0.19.2
Close the vote, and send a result in another email. 2011/9/2 Forrest Xia > +1 > > Forrest > > On Thu, Sep 1, 2011 at 10:21 PM, Ivan wrote: > >> Please vote for the Geronimo Tomcat 7.0.19.2 release, which will be used >> in Geronimo 3.0-beta release >> >> The components up for vote are: >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-014/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.19/7.0.19.2/tomcat-parent-7.0.19-7.0.19.2-source-release.tar.gz >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-014/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.19/7.0.19.2/tomcat-parent-7.0.19-7.0.19.2-source-release.zip >> >> Staging repo is here: >> https://repository.apache.org/content/repositories/orgapachegeronimo-014 >> >> tag is here: >> >> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.19.2/ >> >> Vote open 72 hours >> >> [ ] +1 release this >> [ ] 0 don't care >> [ ] -1 don't release this (please explain) >> >> -- >> Ivan >> > > -- Ivan
[RESULT] Release Geronimo Forked Tomcat 7.0.19.2
The vote passed with the results below, thanks everyone ! +1 Shawn Jiang, Rex Wang, Kevan Miller, viola lu, Han hong Fang, Chi RunHua, Forrest Xia, Ivan no 0 and -1. 2011/9/5 Ivan > Close the vote, and send a result in another email. > > > 2011/9/2 Forrest Xia > >> +1 >> >> Forrest >> >> On Thu, Sep 1, 2011 at 10:21 PM, Ivan wrote: >> >>> Please vote for the Geronimo Tomcat 7.0.19.2 release, which will be used >>> in Geronimo 3.0-beta release >>> >>> The components up for vote are: >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-014/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.19/7.0.19.2/tomcat-parent-7.0.19-7.0.19.2-source-release.tar.gz >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-014/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.19/7.0.19.2/tomcat-parent-7.0.19-7.0.19.2-source-release.zip >>> >>> Staging repo is here: >>> https://repository.apache.org/content/repositories/orgapachegeronimo-014 >>> >>> tag is here: >>> >>> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.19.2/ >>> >>> Vote open 72 hours >>> >>> [ ] +1 release this >>> [ ] 0 don't care >>> [ ] -1 don't release this (please explain) >>> >>> -- >>> Ivan >>> >> >> > > > -- > Ivan > -- Ivan
Re: [VOTE] Release Geronimo Bundled woodstox-core-asl 4.1.2_1
Close the vote, and will send an email for the vote result. 2011/9/2 Forrest Xia > +1 > > Forrest > > On Thu, Sep 1, 2011 at 9:50 PM, Ivan wrote: > >> Please vote for the woodstox-core-asl 4.1.2_1 release, which will be used >> in Geronimo 3.0-beta release >> >> The components up for vote are: >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-013/org/apache/geronimo/bundles/woodstox-core-asl/4.1.2_1/woodstox-core-asl-4.1.2_1-source-release.tar.gz >> * >> https://repository.apache.org/content/repositories/orgapachegeronimo-013/org/apache/geronimo/bundles/woodstox-core-asl/4.1.2_1/woodstox-core-asl-4.1.2_1-source-release.zip >> * >> >> Staging repo is here: >> *https://repository.apache.org/content/repositories/orgapachegeronimo-013 >> * >> >> tag is here: >> >> https://svn.apache.org/repos/asf/geronimo/bundles/tags/woodstox-core-asl-4.1.2_1/ >> >> Vote open 72 hours >> >> [ ] +1 release this >> [ ] 0 don't care >> [ ] -1 don't release this (please explain) >> >> -- >> Ivan >> > > -- Ivan
[RESULT] Release Geronimo Bundled woodstox-core-asl 4.1.2_1
The vote passed with the result below, thanks, everyone ! +1 Shawn Jiang, Rex Wang, Kevan Miller, Viola lu, Han HongFang, Forrest Xia, Ivan no 0 and -1. 2011/9/5 Ivan > Close the vote, and will send an email for the vote result. > > > 2011/9/2 Forrest Xia > >> +1 >> >> Forrest >> >> On Thu, Sep 1, 2011 at 9:50 PM, Ivan wrote: >> >>> Please vote for the woodstox-core-asl 4.1.2_1 release, which will be >>> used in Geronimo 3.0-beta release >>> >>> The components up for vote are: >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-013/org/apache/geronimo/bundles/woodstox-core-asl/4.1.2_1/woodstox-core-asl-4.1.2_1-source-release.tar.gz >>> * >>> https://repository.apache.org/content/repositories/orgapachegeronimo-013/org/apache/geronimo/bundles/woodstox-core-asl/4.1.2_1/woodstox-core-asl-4.1.2_1-source-release.zip >>> * >>> >>> Staging repo is here: >>> * >>> https://repository.apache.org/content/repositories/orgapachegeronimo-013 >>> * >>> >>> tag is here: >>> >>> https://svn.apache.org/repos/asf/geronimo/bundles/tags/woodstox-core-asl-4.1.2_1/ >>> >>> Vote open 72 hours >>> >>> [ ] +1 release this >>> [ ] 0 don't care >>> [ ] -1 don't release this (please explain) >>> >>> -- >>> Ivan >>> >> >> > > > -- > Ivan > -- Ivan
[jira] [Created] (GERONIMO-6143) Create a fragment context for each sub modules in the EAR package
Create a fragment context for each sub modules in the EAR package - Key: GERONIMO-6143 URL: https://issues.apache.org/jira/browse/GERONIMO-6143 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Currently, all the sub modules share the same EARContext in one EAR package, it brings issues for general data, which should be kept for each module itself. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6144) NPE in DependencyManager if configurations/bundles are uninstalled
NPE in DependencyManager if configurations/bundles are uninstalled -- Key: GERONIMO-6144 URL: https://issues.apache.org/jira/browse/GERONIMO-6144 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: dependencies Affects Versions: 3.0 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 3.0 Steps to reproduce the issue. 1. start geronimo server 2. uninstall myfaces related configurations and bundles 3. deploy spring-samples\webflow-richfaces-showcase NullPointerException occurs in DependencyManager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6144) NPE in DependencyManager if configurations/bundles are uninstalled
[ https://issues.apache.org/jira/browse/GERONIMO-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096989#comment-13096989 ] Han Hong Fang commented on GERONIMO-6144: - Fixed at revision: 1165151. > NPE in DependencyManager if configurations/bundles are uninstalled > -- > > Key: GERONIMO-6144 > URL: https://issues.apache.org/jira/browse/GERONIMO-6144 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 3.0 >Reporter: Han Hong Fang >Assignee: Han Hong Fang > Fix For: 3.0 > > > Steps to reproduce the issue. > 1. start geronimo server > 2. uninstall myfaces related configurations and bundles > 3. deploy spring-samples\webflow-richfaces-showcase > NullPointerException occurs in DependencyManager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6144) NPE in DependencyManager if configurations/bundles are uninstalled
[ https://issues.apache.org/jira/browse/GERONIMO-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang resolved GERONIMO-6144. - Resolution: Fixed > NPE in DependencyManager if configurations/bundles are uninstalled > -- > > Key: GERONIMO-6144 > URL: https://issues.apache.org/jira/browse/GERONIMO-6144 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 3.0 >Reporter: Han Hong Fang >Assignee: Han Hong Fang > Fix For: 3.0 > > > Steps to reproduce the issue. > 1. start geronimo server > 2. uninstall myfaces related configurations and bundles > 3. deploy spring-samples\webflow-richfaces-showcase > NullPointerException occurs in DependencyManager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[RESULT][VOTE] Release geronimo rebundled bval-jsr303 0.3_1-incubating - 1st try
Vote result: Vote passed with 8 "+1" from: Shawn Jiang, Ivan, Kevan Miller, Viola Lu, Chi Run Hua, Han Hong Fang, Forrest Xia, and me. There is no 0 or -1. Thanks all for the review. I will release bval-jsr303 0.3_1-incubating soon. -Rex 2011/9/1 Rex Wang > Please vote for geronimo rebundled bval-jsr303 0.3_1-incubating release, > which will be used in Geronimo 3.0-beta release > > The components up for vote are: > > https://repository.apache.org/content/repositories/orgapachegeronimo-011/org/apache/geronimo/bundles/bval-jsr303/0.3_1-incubating/bval-jsr303-0.3_1-incubating-source-release.tar.gz > > https://repository.apache.org/content/repositories/orgapachegeronimo-011/org/apache/geronimo/bundles/bval-jsr303/0.3_1-incubating/bval-jsr303-0.3_1-incubating-source-release.zip > > Staging repo is here: > https://repository.apache.org/content/repositories/orgapachegeronimo-011/ > > tag is here: > > http://svn.apache.org/repos/asf/geronimo/bundles/tags/bval-jsr303-0.3_1-incubating/ > > Vote open 72 hours > > [ ] +1 release this > [ ] 0 don't care > [ ] -1 don't release this (please explain) > > > -- > Lei Wang (Rex) > rwonly AT apache.org > -- Lei Wang (Rex) rwonly AT apache.org
[RESULT] [VOTE] release xbean 3.8 - 1st try
Vote result: Vote passed with 7 "+1" from: Ivan, Forrest Xia, Shawn Jiang, Viola Lu, Kevan Miller, Han Hong Fang, and me. There is no 0 or -1. Thanks all for the review. I will release xbean 3.8 soon. -Rex 2011/8/31 Rex Wang > Please vote for the geronimo xbean 3.8 release, which will be used in > Geronimo 3.0-beta release > > The components up for vote are: > > https://repository.apache.org/content/repositories/orgapachegeronimo-005/org/apache/xbean/xbean/3.8/xbean-3.8-source-release.tar.gz > > https://repository.apache.org/content/repositories/orgapachegeronimo-005/org/apache/xbean/xbean/3.8/xbean-3.8-source-release.zip > > Staging repo is here: > https://repository.apache.org/content/repositories/orgapachegeronimo-005/ > > tag is here: > https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.8/ > > Vote open 72 hours > > [ ] +1 release this > [ ] 0 don't care > [ ] -1 don't release this (please explain) > > > -- > Lei Wang (Rex) > rwonly AT apache.org > -- Lei Wang (Rex) rwonly AT apache.org
[RESULT][VOTE] Release geronimo txmanager 3.1.1 - 1st attempt.
Vote result: Vote passed with 8 "+1" from: Forrest Xia, Ivan, Shawn Jiang, Viola Lu, Kevan Miller, Han Hong Fang, Chi Run Hua, and me. There is no 0 or -1. Thanks all for the review. I will release txmanager 3.1.1 soon. -Rex 2011/8/31 Rex Wang > This is a bug-fix release that will be used for the Geronimo Server > 3.0-beta release. > > The components up for vote are: > > https://repository.apache.org/content/repositories/orgapachegeronimo-004/org/apache/geronimo/components/geronimo-txmanager-parent/3.1.1/geronimo-txmanager-parent-3.1.1-source-release.tar.gz > > https://repository.apache.org/content/repositories/orgapachegeronimo-004/org/apache/geronimo/components/geronimo-txmanager-parent/3.1.1/geronimo-txmanager-parent-3.1.1-source-release.zip > > from the staging repository at: > https://repository.apache.org/content/repositories/orgapachegeronimo-004 > > > The tag is: > > http://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-3.1.1/ > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > > -- > Lei Wang (Rex) > rwonly AT apache.org > -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Closed] (GERONIMO-5635) corrupt JobSchedulerStore can cause server restart to fail
[
https://issues.apache.org/jira/browse/GERONIMO-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang closed GERONIMO-5635.
-
Resolution: Fixed
we upgraded activemq to 5.4.2 for 2.2.2 and 3.0.
> corrupt JobSchedulerStore can cause server restart to fail
> ---
>
> Key: GERONIMO-5635
> URL: https://issues.apache.org/jira/browse/GERONIMO-5635
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 2.2.1, 2.2.2
>Reporter: Kevan Miller
>Priority: Blocker
> Fix For: 2.2.2, 3.0
>
>
> A hard server stop (e.g. kill -9) will frequently result in a corrupt
> JobSchedulerStore. Subsequent restart will fail. See
> https://issues.apache.org/activemq/browse/AMQ-2935 for more information.
> This should be fixed in an ActiveMQ 5.4.2 release. In meantime, you can avoid
> the problem using the following in var/activemq/conf/activemq.xml:
> http://activemq.apache.org/schema/core";
> brokerName="${activemq.brokerName}"
> tmpDataDirectory="${activemq.data}/tmp_storage" useShutdownHook="false"
> start="false" schedulerSupport="false">
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5606) Bad persistenceUnitRoot for PUs in jars embedded in WARs
[ https://issues.apache.org/jira/browse/GERONIMO-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-5606. - Resolution: Fixed this has been fixed by Jarek. > Bad persistenceUnitRoot for PUs in jars embedded in WARs > > > Key: GERONIMO-5606 > URL: https://issues.apache.org/jira/browse/GERONIMO-5606 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > > The persistenceUnitRoot for PUs in jars embedded in WARs is computed > incorrectly which for example causes the META-INF/orm.xml files not to be > discovered by OpenJPA. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5338) ActiveMQ port is not listed as a listening port and is always bound to localhost
[ https://issues.apache.org/jira/browse/GERONIMO-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-5338. - Resolution: Duplicate It's a duplication of https://issues.apache.org/jira/browse/GERONIMO-6110 > ActiveMQ port is not listed as a listening port and is always bound to > localhost > > > Key: GERONIMO-5338 > URL: https://issues.apache.org/jira/browse/GERONIMO-5338 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Kevan Miller > Fix For: 3.0 > > > Listening on Ports: > 1050 10.0.1.8CORBA Naming Service > 1099 10.0.1.8RMI Naming > 1527 10.0.1.8Derby Connector > 2001 10.0.1.8OpenEJB ORB Adapter > 4201 10.0.1.8OpenEJB Daemon > 4203 10.0.1.8OpenEJB Daemon > 6142 239.255.3.2 OpenEJB Daemon > 6882 10.0.1.8OpenEJB ORB Adapter > 8009 0.0.0.0 Tomcat Connector AJP TomcatAJPConnector > 8080 0.0.0.0 Tomcat Connector HTTP BIO TomcatWebConnector > 8443 0.0.0.0 Tomcat Connector HTTPS BIO TomcatWebSSLConnector > 10.0.1.8JMX Remoting Connector > No ActiveMQ > netstat output: > tcp4 0 0 127.0.0.1.61616*.*LISTEN -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
