[jira] Commented: (GERONIMO-5191) G 2.1.5 startup console log messages are being generated
[ https://issues.apache.org/jira/browse/GERONIMO-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846768#action_12846768 ] Forrest Xia commented on GERONIMO-5191: --- tested in my latest local build with those commits by Ivan, then run geronimo.sh run, no extra console msgs show up. > G 2.1.5 startup console log messages are being generated > - > > Key: GERONIMO-5191 > URL: https://issues.apache.org/jira/browse/GERONIMO-5191 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.5 >Reporter: Kevan Miller >Assignee: Ivan > Fix For: 2.1.5 > > > I'm seeing a lot of log messages during startup of a G 2.1.5-SNAPSHOT tomcat > java ee server, that I didn't see in 2.1.4. They should be cleaned up... > INFO: Set JAAS app name Geronimo > Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded start > INFO: Starting tomcat server > Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded initNaming > INFO: Catalina naming disabled > Mar 17, 2010 4:18:27 PM org.apache.catalina.core.AprLifecycleListener init > INFO: The APR based Apache Tomcat Native library which allows optimal > performance in production environments was not found on the > java.library.path: :/Applications/YourKit Java Profiler > 6.0.12.app/bin/mac:.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java > [*** ] 38% 28s Starting > org.apache.ger...Mar 17, 2010 4:18:27 PM > org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Geronimo (Embedded Tomcat/@VERSION@) > Mar 17, 2010 4:18:27 PM org.apache.catalina.realm.RealmBase start > INFO: This Realm has already been started > [*** ] 38% 29s Starting > org.apache.ger...Mar 17, 2010 4:18:27 PM > org.apache.catalina.core.DefaultInstanceManager > SEVERE: "Restricted listeners property file not found > [*** ] 38% 29s Starting > org.apache.ger...Mar 17, 2010 4:18:28 PM > org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080 > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 > Mar 17, 2010 4:18:28 PM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > [*** ] 38% 30s Starting > org.apache.ger...Mar 17, 2010 4:18:28 PM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/129 config=null > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443 > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8443 > [** ] 77% 38s Loading > org.apache.ger...Mar 17, 2010 4:18:36 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 77% 38s Starting > org.apache.ger...Mar 17, 2010 4:18:37 PM > org.apache.catalina.core.ApplicationContext log > INFO: Initializing Spring root WebApplicationContext > [** ] 77% 39s Starting > org.apache.ger...Mar 17, 2010 4:18:38 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [*** ] 78% 41s Starting > org.apache.ger...Mar 17, 2010 4:18:39 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [] 81% 42s Loading > org.apache.ger...Mar 17, 2010 4:18:40 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [* ] 83% 43s Starting > org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [* ] 84% 43s Loading > org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 85% 43s Loading > org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 87% 44s Starting > org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useCont
[jira] Closed: (GERONIMO-5191) G 2.1.5 startup console log messages are being generated
[ https://issues.apache.org/jira/browse/GERONIMO-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5191. - Resolution: Fixed > G 2.1.5 startup console log messages are being generated > - > > Key: GERONIMO-5191 > URL: https://issues.apache.org/jira/browse/GERONIMO-5191 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.5 >Reporter: Kevan Miller >Assignee: Ivan > Fix For: 2.1.5 > > > I'm seeing a lot of log messages during startup of a G 2.1.5-SNAPSHOT tomcat > java ee server, that I didn't see in 2.1.4. They should be cleaned up... > INFO: Set JAAS app name Geronimo > Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded start > INFO: Starting tomcat server > Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded initNaming > INFO: Catalina naming disabled > Mar 17, 2010 4:18:27 PM org.apache.catalina.core.AprLifecycleListener init > INFO: The APR based Apache Tomcat Native library which allows optimal > performance in production environments was not found on the > java.library.path: :/Applications/YourKit Java Profiler > 6.0.12.app/bin/mac:.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java > [*** ] 38% 28s Starting > org.apache.ger...Mar 17, 2010 4:18:27 PM > org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Geronimo (Embedded Tomcat/@VERSION@) > Mar 17, 2010 4:18:27 PM org.apache.catalina.realm.RealmBase start > INFO: This Realm has already been started > [*** ] 38% 29s Starting > org.apache.ger...Mar 17, 2010 4:18:27 PM > org.apache.catalina.core.DefaultInstanceManager > SEVERE: "Restricted listeners property file not found > [*** ] 38% 29s Starting > org.apache.ger...Mar 17, 2010 4:18:28 PM > org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080 > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 > Mar 17, 2010 4:18:28 PM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > [*** ] 38% 30s Starting > org.apache.ger...Mar 17, 2010 4:18:28 PM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/129 config=null > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443 > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8443 > [** ] 77% 38s Loading > org.apache.ger...Mar 17, 2010 4:18:36 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 77% 38s Starting > org.apache.ger...Mar 17, 2010 4:18:37 PM > org.apache.catalina.core.ApplicationContext log > INFO: Initializing Spring root WebApplicationContext > [** ] 77% 39s Starting > org.apache.ger...Mar 17, 2010 4:18:38 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [*** ] 78% 41s Starting > org.apache.ger...Mar 17, 2010 4:18:39 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [] 81% 42s Loading > org.apache.ger...Mar 17, 2010 4:18:40 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [* ] 83% 43s Starting > org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [* ] 84% 43s Loading > org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 85% 43s Loading > org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 87% 44s Starting > org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [*** ] 99% 49s Loading > org.apache.ger...Mar 17, 2010 4:18:48 PM org.apache.catalina.rea
[jira] Resolved: (GERONIMO-5027) Redeploy option for farming
[ https://issues.apache.org/jira/browse/GERONIMO-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-5027. --- Resolution: Fixed Fix Version/s: 3.0 Committed the patch to 21, 22, trunk with Revsion 924620,924622,924625 Thanks Ashish for the patch ! Please open another JIRA to track the gshell equivalence. > Redeploy option for farming > --- > > Key: GERONIMO-5027 > URL: https://issues.apache.org/jira/browse/GERONIMO-5027 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.1.4, 2.2 > Environment: Windows XP g214 >Reporter: Ashish Jain >Assignee: Shawn Jiang > Fix For: 2.1.5, 2.2.1, 3.0 > > Attachments: 5027_21.patch, 5027_21_updated.patch > > > Redeploy feature for farming. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release txmanager-2.1.4 - RC1
Vote passes with the following voting +1: Donald Woods, Kevan Miller, Ivan There were no 0 or -1 votes. Thanks 2010/3/18 Ivan > +1 > > 2010/3/17 Kevan Miller > > +1 >> >> Source and build all look good. >> >> --kevan >> >> On Mar 3, 2010, at 4:23 AM, Rex Wang wrote: >> >> To support the upcoming Geronimo 2.1.5 release,I would like to release >> txmanager-2.1.4. However, we need a full TCK against it. >> >> Staging repo: >> https://repository.apache.org/content/repositories/orgapachegeronimo-002/ >> >> Source tag: >> >> https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.4/ >> >> Vote will be open for 72 hours. >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> >> Thanks, >> >> >> -- >> Lei Wang (Rex) >> rwonly AT apache.org >> >> >> > > > -- > Ivan > -- Lei Wang (Rex) rwonly AT apache.org
[jira] Commented: (GERONIMO-5191) G 2.1.5 startup console log messages are being generated
[ https://issues.apache.org/jira/browse/GERONIMO-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846723#action_12846723 ] Ivan commented on GERONIMO-5191: Commit changes to Geronim customized Tomcat 6.0.26 at rev: 924596, Geronimo 2.1 branch at rev:924600 > G 2.1.5 startup console log messages are being generated > - > > Key: GERONIMO-5191 > URL: https://issues.apache.org/jira/browse/GERONIMO-5191 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.5 >Reporter: Kevan Miller >Assignee: Ivan > Fix For: 2.1.5 > > > I'm seeing a lot of log messages during startup of a G 2.1.5-SNAPSHOT tomcat > java ee server, that I didn't see in 2.1.4. They should be cleaned up... > INFO: Set JAAS app name Geronimo > Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded start > INFO: Starting tomcat server > Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded initNaming > INFO: Catalina naming disabled > Mar 17, 2010 4:18:27 PM org.apache.catalina.core.AprLifecycleListener init > INFO: The APR based Apache Tomcat Native library which allows optimal > performance in production environments was not found on the > java.library.path: :/Applications/YourKit Java Profiler > 6.0.12.app/bin/mac:.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java > [*** ] 38% 28s Starting > org.apache.ger...Mar 17, 2010 4:18:27 PM > org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Geronimo (Embedded Tomcat/@VERSION@) > Mar 17, 2010 4:18:27 PM org.apache.catalina.realm.RealmBase start > INFO: This Realm has already been started > [*** ] 38% 29s Starting > org.apache.ger...Mar 17, 2010 4:18:27 PM > org.apache.catalina.core.DefaultInstanceManager > SEVERE: "Restricted listeners property file not found > [*** ] 38% 29s Starting > org.apache.ger...Mar 17, 2010 4:18:28 PM > org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080 > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 > Mar 17, 2010 4:18:28 PM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > [*** ] 38% 30s Starting > org.apache.ger...Mar 17, 2010 4:18:28 PM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/129 config=null > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443 > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8443 > [** ] 77% 38s Loading > org.apache.ger...Mar 17, 2010 4:18:36 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 77% 38s Starting > org.apache.ger...Mar 17, 2010 4:18:37 PM > org.apache.catalina.core.ApplicationContext log > INFO: Initializing Spring root WebApplicationContext > [** ] 77% 39s Starting > org.apache.ger...Mar 17, 2010 4:18:38 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [*** ] 78% 41s Starting > org.apache.ger...Mar 17, 2010 4:18:39 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [] 81% 42s Loading > org.apache.ger...Mar 17, 2010 4:18:40 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [* ] 83% 43s Starting > org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [* ] 84% 43s Loading > org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 85% 43s Loading > org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 87% 44s Starting > org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [
[jira] Assigned: (GERONIMO-5192) Changeing http port to 80 causes a port in use exception in the RMI service
[ https://issues.apache.org/jira/browse/GERONIMO-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reassigned GERONIMO-5192: - Assignee: Forrest Xia > Changeing http port to 80 causes a port in use exception in the RMI service > --- > > Key: GERONIMO-5192 > URL: https://issues.apache.org/jira/browse/GERONIMO-5192 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 > Environment: Linux, geronimo-tomcat6-minimal-2.2, java 6 >Reporter: Brill Pappin >Assignee: Forrest Xia >Priority: Blocker > > a fresh install of geronimo-tomcat6-minimal-2.2 simply extracted. > change the http port in the config file and you immediatly get a port in use > exception from the RMI service when the server is started. > This doesn't happen if you leave the default ports alone and start it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5192) Changeing http port to 80 causes a port in use exception in the RMI service
[ https://issues.apache.org/jira/browse/GERONIMO-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846722#action_12846722 ] Forrest Xia commented on GERONIMO-5192: --- And you need to ensure the target port not in use. > Changeing http port to 80 causes a port in use exception in the RMI service > --- > > Key: GERONIMO-5192 > URL: https://issues.apache.org/jira/browse/GERONIMO-5192 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 > Environment: Linux, geronimo-tomcat6-minimal-2.2, java 6 >Reporter: Brill Pappin >Assignee: Forrest Xia >Priority: Blocker > > a fresh install of geronimo-tomcat6-minimal-2.2 simply extracted. > change the http port in the config file and you immediatly get a port in use > exception from the RMI service when the server is started. > This doesn't happen if you leave the default ports alone and start it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5192) Changeing http port to 80 causes a port in use exception in the RMI service
[ https://issues.apache.org/jira/browse/GERONIMO-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846721#action_12846721 ] Forrest Xia commented on GERONIMO-5192: --- How and where you change the http port? By default, Geronimo uses 8080 for http request listening. If you want to change that, you can modify PortOffset value in GERONIMO_HOME/var/config/config-substitutions.properties file. > Changeing http port to 80 causes a port in use exception in the RMI service > --- > > Key: GERONIMO-5192 > URL: https://issues.apache.org/jira/browse/GERONIMO-5192 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 > Environment: Linux, geronimo-tomcat6-minimal-2.2, java 6 >Reporter: Brill Pappin >Priority: Blocker > > a fresh install of geronimo-tomcat6-minimal-2.2 simply extracted. > change the http port in the config file and you immediatly get a port in use > exception from the RMI service when the server is started. > This doesn't happen if you leave the default ports alone and start it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5191) G 2.1.5 startup console log messages are being generated
[ https://issues.apache.org/jira/browse/GERONIMO-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-5191: -- Assignee: Ivan > G 2.1.5 startup console log messages are being generated > - > > Key: GERONIMO-5191 > URL: https://issues.apache.org/jira/browse/GERONIMO-5191 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.5 >Reporter: Kevan Miller >Assignee: Ivan > Fix For: 2.1.5 > > > I'm seeing a lot of log messages during startup of a G 2.1.5-SNAPSHOT tomcat > java ee server, that I didn't see in 2.1.4. They should be cleaned up... > INFO: Set JAAS app name Geronimo > Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded start > INFO: Starting tomcat server > Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded initNaming > INFO: Catalina naming disabled > Mar 17, 2010 4:18:27 PM org.apache.catalina.core.AprLifecycleListener init > INFO: The APR based Apache Tomcat Native library which allows optimal > performance in production environments was not found on the > java.library.path: :/Applications/YourKit Java Profiler > 6.0.12.app/bin/mac:.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java > [*** ] 38% 28s Starting > org.apache.ger...Mar 17, 2010 4:18:27 PM > org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Geronimo (Embedded Tomcat/@VERSION@) > Mar 17, 2010 4:18:27 PM org.apache.catalina.realm.RealmBase start > INFO: This Realm has already been started > [*** ] 38% 29s Starting > org.apache.ger...Mar 17, 2010 4:18:27 PM > org.apache.catalina.core.DefaultInstanceManager > SEVERE: "Restricted listeners property file not found > [*** ] 38% 29s Starting > org.apache.ger...Mar 17, 2010 4:18:28 PM > org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080 > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 > Mar 17, 2010 4:18:28 PM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > [*** ] 38% 30s Starting > org.apache.ger...Mar 17, 2010 4:18:28 PM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/129 config=null > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443 > Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8443 > [** ] 77% 38s Loading > org.apache.ger...Mar 17, 2010 4:18:36 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 77% 38s Starting > org.apache.ger...Mar 17, 2010 4:18:37 PM > org.apache.catalina.core.ApplicationContext log > INFO: Initializing Spring root WebApplicationContext > [** ] 77% 39s Starting > org.apache.ger...Mar 17, 2010 4:18:38 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [*** ] 78% 41s Starting > org.apache.ger...Mar 17, 2010 4:18:39 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [] 81% 42s Loading > org.apache.ger...Mar 17, 2010 4:18:40 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [* ] 83% 43s Starting > org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [* ] 84% 43s Loading > org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 85% 43s Loading > org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [** ] 87% 44s Starting > org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm > setUseContextClassLoader > INFO: Setting useContextClassLoader = false > [*** ] 99% 49s Loading > org.apache.ger...Mar 17, 2010 4:18:48 PM org.apache.catalina.realm.JAASRe
[BUILD] trunk: Failed for Revision: 924577
Geronimo Revision: 924577 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100317/build-2100.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100317/unit-test-reports
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/framework/buildsupport/geronimo-assembly-archetype/src/test/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/framework/buildsupport/geronimo-assembly-archetype/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/framework/buildsupport/geronimo-assembly-archetype/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/framework/buildsupport/geronimo-assembly-archetype/target/geronimo-assembly-archetype-3.0-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-assembly-archetype-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/framework/buildsupport/geronimo-assembly-archetype/target/geronimo-assembly-archetype-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/buildsupport/geronimo-assembly-archetype/3.0-SNAPSHOT/geronimo-assembly-archetype-3.0-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Framework, Configs
[INFO]task-segment: [install]
[INFO]
[INFO] Reloading plugin container for:
org.apache.geronimo.buildsupport:car-maven-plugin:3.0-SNAPSHOT. The plugin
artifact has changed.
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/geronimo/geronimo/trunk/framework/configs/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/framework/configs/3.0-SNAPSHOT/configs-3.0-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo Framework, Configs :: GBean Deployer Boostrap
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/framework/configs/geronimo-gbean-deployer-bootstrap/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/framework/configs/geronimo-gbean-deployer-bootstrap/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration {execution: default-validate-configuration}]
[INFO] [car:prepare-plan {execution: default-prepare-plan}]
[INFO] Generated:
/home/geronimo/geronimo/trunk/framework/configs/geronimo-gbean-deployer-bootstrap/target/work/plan.xml
[INFO] [car:verify-no-dependency-change {execution:
default-verify-no-dependency-change}]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/trunk/framework/configs/geronimo-gbean-deployer-bootstrap/target/history/dependencies.added.xml
Tree listing is saved here:
/home/geronimo/geronimo/trunk/framework/configs/geronimo-gbean-deployer-bootstrap/target/history/treeListing.txt
Delete
/home/geronimo/geronimo/trunk/framework/configs/geronimo-gbean-deployer-bootstrap/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureExc
Re: The way to scan annotation in Geronimo 3.0
In the servlet 3.0, while merging web-fragment and annotations, it says : --> After processing the web-fragment.xml, annotations from the corresponding fragment are processed to complete the effective metadata for the fragment before processing the next fragment. The following rules are used for processing annotations: Also, according to sorting policy, if some webfagments are excluded (e.g. Absolute soring is used in web.xml, and some founded webfagments are not explicitly configured), those excluded jars should not be used for annotation scan, also TLD scan might be affected. Later, I would try to add something like filter to scanning classes. Scanning all the required classes/annotations is a good idea, but we might be some way to record where those classes are from. I hope that we could do all the annotations scanning together in the future. I agree that we move those code scanning classes to xbean, as they are not 'belonged to' the geronimo-kernel. 2010/3/18 David Jencks > > On Mar 17, 2010, at 7:02 AM, Ivan wrote: > > Hi, >> While working on Servlet 3.0, it is required to scan WebServlet >> annotations in the specified jar file. >> > > Can you be more specific about what you need? Is this really scanning > specific jars within a war, or an entire war inside an ear bundle? If it is > the second case, I think we should solve this by turning ears into > one-bundle-per-module. > > > In the past, we could use the classfinder with a temp url classloader, >> while in the new OSGI environment, there is a BundleClassFinder is added in >> the framework. But I could not configure it to only scan the specific parts >> of the bundle. I am thinking we might need to introduce some more functions >> to it : >> a. Something like DiscoveryPolicy, with it, we could ask the >> BundleClassFinder to scan parts of the bundle file according to the url, >> like web-inf/a.jar. Or only scan the classes in the bundle classpath. >> b. Use ASM as much as possible, currently, seems that BundleClassFinder >> may load all the classes in the scanning process. It might be performance >> issue in the runtime. >> Any comment ? >> > > I needed some annotation scanning code for connector so I combined the asm > code from xbean-finder (moved to an abstract superclass) and Jareks really > nice bundle scanning code in BundleResourceFinder in kernel to come up with > a BundleAnnotationFinder that does what I want so far. See XBEAN-145 and > rev 924429 in geronimo-kernel. > > I don't have a problem with introducing a bundle-classpath filter in > BundleResourceFinder if we actually need it. > > I think all this scanning code should end up in somewhere more easily > accessible than geronimo-kernel so e.g. openejb can use it. I thought it > would be a good idea to discuss where it should go before moving or > duplicating it so I came up with the 2-part solution above. One possibility > is xbean-finder; I don't know if its a good idea to have one jar that deals > with "finding" in both osgi and non-osgi environments. > > thanks > david jencks > > -- >> Ivan >> > > -- Ivan
Re: [VOTE] Release txmanager-2.1.4 - RC1
+1 2010/3/17 Kevan Miller > +1 > > Source and build all look good. > > --kevan > > On Mar 3, 2010, at 4:23 AM, Rex Wang wrote: > > To support the upcoming Geronimo 2.1.5 release,I would like to release > txmanager-2.1.4. However, we need a full TCK against it. > > Staging repo: > https://repository.apache.org/content/repositories/orgapachegeronimo-002/ > > Source tag: > > https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.4/ > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > > Thanks, > > > -- > Lei Wang (Rex) > rwonly AT apache.org > > > -- Ivan
[jira] Created: (GERONIMO-5192) Changeing http port to 80 causes a port in use exception in the RMI service
Changeing http port to 80 causes a port in use exception in the RMI service --- Key: GERONIMO-5192 URL: https://issues.apache.org/jira/browse/GERONIMO-5192 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Affects Versions: 2.2 Environment: Linux, geronimo-tomcat6-minimal-2.2, java 6 Reporter: Brill Pappin Priority: Blocker a fresh install of geronimo-tomcat6-minimal-2.2 simply extracted. change the http port in the config file and you immediatly get a port in use exception from the RMI service when the server is started. This doesn't happen if you leave the default ports alone and start it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5191) G 2.1.5 startup console log messages are being generated
G 2.1.5 startup console log messages are being generated - Key: GERONIMO-5191 URL: https://issues.apache.org/jira/browse/GERONIMO-5191 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1.5 Reporter: Kevan Miller Fix For: 2.1.5 I'm seeing a lot of log messages during startup of a G 2.1.5-SNAPSHOT tomcat java ee server, that I didn't see in 2.1.4. They should be cleaned up... INFO: Set JAAS app name Geronimo Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded start INFO: Starting tomcat server Mar 17, 2010 4:18:26 PM org.apache.catalina.startup.Embedded initNaming INFO: Catalina naming disabled Mar 17, 2010 4:18:27 PM org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: :/Applications/YourKit Java Profiler 6.0.12.app/bin/mac:.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java [*** ] 38% 28s Starting org.apache.ger...Mar 17, 2010 4:18:27 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Geronimo (Embedded Tomcat/@VERSION@) Mar 17, 2010 4:18:27 PM org.apache.catalina.realm.RealmBase start INFO: This Realm has already been started [*** ] 38% 29s Starting org.apache.ger...Mar 17, 2010 4:18:27 PM org.apache.catalina.core.DefaultInstanceManager SEVERE: "Restricted listeners property file not found [*** ] 38% 29s Starting org.apache.ger...Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080 Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 Mar 17, 2010 4:18:28 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 [*** ] 38% 30s Starting org.apache.ger...Mar 17, 2010 4:18:28 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/129 config=null Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443 Mar 17, 2010 4:18:28 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-0.0.0.0-8443 [** ] 77% 38s Loading org.apache.ger...Mar 17, 2010 4:18:36 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [** ] 77% 38s Starting org.apache.ger...Mar 17, 2010 4:18:37 PM org.apache.catalina.core.ApplicationContext log INFO: Initializing Spring root WebApplicationContext [** ] 77% 39s Starting org.apache.ger...Mar 17, 2010 4:18:38 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [*** ] 78% 41s Starting org.apache.ger...Mar 17, 2010 4:18:39 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [] 81% 42s Loading org.apache.ger...Mar 17, 2010 4:18:40 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [* ] 83% 43s Starting org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [* ] 84% 43s Loading org.apache.ger...Mar 17, 2010 4:18:41 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [** ] 85% 43s Loading org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [** ] 87% 44s Starting org.apache.ger...Mar 17, 2010 4:18:42 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [*** ] 99% 49s Loading org.apache.ger...Mar 17, 2010 4:18:48 PM org.apache.catalina.realm.JAASRealm setUseContextClassLoader INFO: Setting useContextClassLoader = false [] 100% 52s Startup complete -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5190) Use jaxb for plans instead of xmlbeans
Use jaxb for plans instead of xmlbeans -- Key: GERONIMO-5190 URL: https://issues.apache.org/jira/browse/GERONIMO-5190 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Openejb has a jaxb tree for the ee dds that is much easier to work with than the xmlbeans classes we have been using. We should move towards using this code. I'm starting in the connector module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5091) Bundlize the yoko jar files.
[ https://issues.apache.org/jira/browse/GERONIMO-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-5091: --- Component/s: osgi CORBA This is actually done, and there is a small amount of evidence that the orb might still work to some extent. > Bundlize the yoko jar files. > - > > Key: GERONIMO-5091 > URL: https://issues.apache.org/jira/browse/GERONIMO-5091 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: CORBA, osgi >Reporter: Rick McGuire > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5129) Fix to be picked from tomcat for Spnego support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-5129: --- Component/s: Tomcat for 2.2 and later I'd suggest using the open source jaspic spnego module. > Fix to be picked from tomcat for Spnego support in geronimo > --- > > Key: GERONIMO-5129 > URL: https://issues.apache.org/jira/browse/GERONIMO-5129 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Tomcat >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.1.5, 2.2.1 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5157) Tomcat 6.0.20 NIO connector cause connection always terminates in a very short time interval
[ https://issues.apache.org/jira/browse/GERONIMO-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-5157: --- Component/s: Tomcat > Tomcat 6.0.20 NIO connector cause connection always terminates in a very > short time interval > > > Key: GERONIMO-5157 > URL: https://issues.apache.org/jira/browse/GERONIMO-5157 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1.5 >Reporter: Rex Wang >Assignee: Ashish Jain > Fix For: 2.1.5 > > > Hi, > I have a sample application which uses the Web messaging service tosimulate > stock quotes to a Dojo-enabled client application and i use Tomcat NIO > connector for comet support. I tried deploying the application in > G2.1.5-snapshot the stock quotes update doesn't happen properly but it works > very well in G2.1.4. A look at the requests inthe firebug shows that the > bayeux connection always terminates in a very > short time interval. however, I don't see any exceptions or errors in the > console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5161) OpenEJB is starting an ejbds listener which is not currently controlled by geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-5161: --- Component/s: OpenEJB > OpenEJB is starting an ejbds listener which is not currently controlled by > geronimo > --- > > Key: GERONIMO-5161 > URL: https://issues.apache.org/jira/browse/GERONIMO-5161 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: OpenEJB >Affects Versions: 2.2.1 >Reporter: Kevan Miller > Fix For: 2.2.1 > > > OpenEJB 3.1.3-SNAPSHOT is starting an ejbds listener. Seems like we need to > either disable ejbds or make the host and port easily configurable (via > config-substitution.properties). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5163) Admin console assemble server problems
[ https://issues.apache.org/jira/browse/GERONIMO-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-5163: --- Component/s: console > Admin console assemble server problems > -- > > Key: GERONIMO-5163 > URL: https://issues.apache.org/jira/browse/GERONIMO-5163 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2.1 >Reporter: Kevan Miller >Priority: Blocker > Fix For: 2.2.1 > > > 1) The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go > to assemble server page, click "expert user" and try to scroll down. Unless I > make the font type very small, I can't see the system plugins and can't > scroll down to them. > 2) Also, the default value for "assembly target path" used to default to > var/temp. It doesn't default to anything > 3) This is a potentially very bad problem (and be very careful testing or you > will lose files). The assembly process seems to be trying to clean up after > itself -- which is nice. However, if you specify an existing directory, it > will wipe out all of the files in your directory. I specified the root > directory of my server and it deleted the entire server. Very bad and could > have been worse!. We should be generating a temporary directory and only > deleting this temporary directory, only. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5182) Fix compile errors caused by Jetty 8.0.0.M0 release
[ https://issues.apache.org/jira/browse/GERONIMO-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-5182: --- Component/s: Jetty > Fix compile errors caused by Jetty 8.0.0.M0 release > --- > > Key: GERONIMO-5182 > URL: https://issues.apache.org/jira/browse/GERONIMO-5182 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Jetty >Affects Versions: 3.0 >Reporter: Kevan Miller >Assignee: Kevan Miller > Fix For: 3.0 > > > There are multiple updates in the latest Jetty 8.0.0.M0 release which are > breaking the build -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: The way to scan annotation in Geronimo 3.0
On Mar 17, 2010, at 7:02 AM, Ivan wrote: Hi, While working on Servlet 3.0, it is required to scan WebServlet annotations in the specified jar file. Can you be more specific about what you need? Is this really scanning specific jars within a war, or an entire war inside an ear bundle? If it is the second case, I think we should solve this by turning ears into one-bundle-per-module. In the past, we could use the classfinder with a temp url classloader, while in the new OSGI environment, there is a BundleClassFinder is added in the framework. But I could not configure it to only scan the specific parts of the bundle. I am thinking we might need to introduce some more functions to it : a. Something like DiscoveryPolicy, with it, we could ask the BundleClassFinder to scan parts of the bundle file according to the url, like web-inf/a.jar. Or only scan the classes in the bundle classpath. b. Use ASM as much as possible, currently, seems that BundleClassFinder may load all the classes in the scanning process. It might be performance issue in the runtime. Any comment ? I needed some annotation scanning code for connector so I combined the asm code from xbean-finder (moved to an abstract superclass) and Jareks really nice bundle scanning code in BundleResourceFinder in kernel to come up with a BundleAnnotationFinder that does what I want so far. See XBEAN-145 and rev 924429 in geronimo-kernel. I don't have a problem with introducing a bundle-classpath filter in BundleResourceFinder if we actually need it. I think all this scanning code should end up in somewhere more easily accessible than geronimo-kernel so e.g. openejb can use it. I thought it would be a good idea to discuss where it should go before moving or duplicating it so I came up with the 2-part solution above. One possibility is xbean-finder; I don't know if its a good idea to have one jar that deals with "finding" in both osgi and non-osgi environments. thanks david jencks -- Ivan
[jira] Commented: (GERONIMO-5030) Implement web container extender (RFC 66)
[ https://issues.apache.org/jira/browse/GERONIMO-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846544#action_12846544 ] Jarek Gawor commented on GERONIMO-5030: --- Updated Tomcat & Jetty code to consider attached fragment bundles when looking up resources. Committed in revision 924430. > Implement web container extender (RFC 66) > - > > Key: GERONIMO-5030 > URL: https://issues.apache.org/jira/browse/GERONIMO-5030 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 924379
Geronimo Revision: 924379 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100317/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100317/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-myfaces:jar:2.2.1-SNAPSHOT from the specified remote repositories: 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.myfaces.core:myfaces-impl:jar:1.2.6 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.myfaces.core -DartifactId=myfaces-impl -Dversion=1.2.6 -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.myfaces.core -DartifactId=myfaces-impl -Dversion=1.2.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-myfaces:jar:2.2.1-SNAPSHOT 2) org.apache.myfaces.core:myfaces-impl:jar:1.2.6 -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-myfaces:jar:2.2.1-SNAPSHOT from the specified remote repositories: 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:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) 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.myfaces.core:myfaces-impl:jar:1.2.6 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.myfaces.core -DartifactId=myfaces-impl -Dversion=1.2.6 -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.myfaces.core -DartifactId=myfaces-impl -Dversion=1.2.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-myfaces:jar:2.2.1-SNAPSHOT 2) org.apache.myfaces.core:myfaces-impl:jar:1.2.6 -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-myfaces:jar:2.2.1-SNAPSHOT from the specified remote repositories: 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.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417) at
[jira] Created: (GERONIMO-5189) Deployment message indicates that the deployment fails, but the app actually does deploy but does not start
Deployment message indicates that the deployment fails, but the app actually does deploy but does not start --- Key: GERONIMO-5189 URL: https://issues.apache.org/jira/browse/GERONIMO-5189 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ, dependencies, deployment, Tomcat Affects Versions: 2.2 Environment: Windows Server 2003 ee SP2 Geronimo with Tomcat Reporter: Steven Ashwill Priority: Minor We are having an issue similar to the jira listed below. We get the message that the deployment fails, but the app actually does deploy but does not start. All we have to do is click start and everything seems fine. We do not get this error on Version 2.2-SNAPSHOT Build 2009.03.23-15:10:47.340-0400 But it started when we upgraded to the 2.2 release. Here is a portion of the stack trace we receive when we attempt to redeploy an application ear: INFO | jvm 1| 2010/03/17 09:25:09 | java.lang.ClassCastException: org.apache.geronimo.connector.outbound.connectiontracking.ConnectorInsta nceContextImpl cannot be cast to org.apache.geronimo.connector.outbound.connectiontracking.SharedConnecto rInstanceContext INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.before (InstanceContextBeforeAfter.java:49) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.befor e(ComponentContextBeforeAfter.java:40) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.before (UserTransactionBeforeAfter.java:63) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(Geronim oBeforeAfterValve.java:43) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandar dContext.java:264) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja va:791) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.ja va:339) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppConte xt.java:525) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInst ance.java:953) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GB eanInstanceState.java:269) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstance State.java:103) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java :525) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBean Dependency.java:110) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDepende ncy.java:145) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDepende ncy.java:119) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent( BasicLifecycleMonitor.java:175) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicL ifecycleMonitor.java:44) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroad caster.fireRunningEvent(BasicLifecycleMonitor.java:253) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GB eanInstanceState.java:295) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstance State.java:103) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBea nInstanceState.java:125) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInst ance.java:539) INFO | jvm 1| 2010/03/17 09:25:09 | at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKe rnel.java
[jira] Updated: (GERONIMO-5178) Inconsistent handling of META-INF/services files by different Geronmo specs.
[ https://issues.apache.org/jira/browse/GERONIMO-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5178: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5090 > Inconsistent handling of META-INF/services files by different Geronmo specs. > - > > Key: GERONIMO-5178 > URL: https://issues.apache.org/jira/browse/GERONIMO-5178 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: Rick McGuire > Fix For: 3.0 > > > A number of the Geronimo specs use the provider resolution pattern defined by > the ServiceLoader class in Java 6 to resolve different provider classes. In > this pattern, a file with a given class name in the META-INF/services > directory can define one or more provider classes for a given source > interface name. As implemented by the ServiceLoader class, these files can > contain multiple lines with pure comment lines and line comments on lines > that define classes, as well as multiple providers defined per file. Thus a > file like this would be considered valiid: > # A set of provider classes for the blah.blah interface > org.apache.geronimo.foo.BlahImpl # The default first one > org.apache.geronimo.bar.BlahImpl # The secondary fall back. > The different spec projects that use these files parse them under different > assumptions: > - Some unilaterally take the first line without any comment processing at all > or recognition that there might be multiple providers defined per file. > - Some projects allow for pure comment lines but don't parse for comments on > a definition line. > - Not all projects are opening these files assuming a utf-8 encoding. > This could best be solved by refactoring the code to use some common methods. > This refactoring will also allow OSGi-awareness to be added to the service > file lookups. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release txmanager-2.1.4 - RC1
+1 Source and build all look good. --kevan On Mar 3, 2010, at 4:23 AM, Rex Wang wrote: > To support the upcoming Geronimo 2.1.5 release,I would like to release > txmanager-2.1.4. However, we need a full TCK against it. > > Staging repo: > https://repository.apache.org/content/repositories/orgapachegeronimo-002/ > > Source tag: > https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.4/ > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > > Thanks, > > > -- > Lei Wang (Rex) > rwonly AT apache.org
The way to scan annotation in Geronimo 3.0
Hi, While working on Servlet 3.0, it is required to scan WebServlet annotations in the specified jar file. In the past, we could use the classfinder with a temp url classloader, while in the new OSGI environment, there is a BundleClassFinder is added in the framework. But I could not configure it to only scan the specific parts of the bundle. I am thinking we might need to introduce some more functions to it : a. Something like DiscoveryPolicy, with it, we could ask the BundleClassFinder to scan parts of the bundle file according to the url, like web-inf/a.jar. Or only scan the classes in the bundle classpath. b. Use ASM as much as possible, currently, seems that BundleClassFinder may load all the classes in the scanning process. It might be performance issue in the runtime. Any comment ? -- Ivan
[jira] Created: (GERONIMO-5188) Uplevel the stax spec implementation to the 1.3 maintenance release level.
Uplevel the stax spec implementation to the 1.3 maintenance release level. --- Key: GERONIMO-5188 URL: https://issues.apache.org/jira/browse/GERONIMO-5188 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: specs Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 The Java EE 6 spec does not list a requirement for the maintenance revision 3 of the STAX API because STAX is included in the Java 6 JRE. However, the Geronimo spec jar should be brought up to the matching level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5148) Remove the dependency of clustering over JMXConnector
[ https://issues.apache.org/jira/browse/GERONIMO-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5148: -- Attachment: 5148_updated_21.patch Rex, Here is the updated patch. Using this both the JMXSecure and JMX Non Secure connector can be used simultaneously. I have tested this with farming and seems to be working fine. Please verify and apply. > Remove the dependency of clustering over JMXConnector > - > > Key: GERONIMO-5148 > URL: https://issues.apache.org/jira/browse/GERONIMO-5148 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.1.5, 2.2.1, 3.0 >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.1.5, 2.2.1, 3.0 > > Attachments: 5148.patch, 5148_updated_21.patch, JavaAgent.jar > > > It should be possible to make use of JMXSecureConnector for clustering. > Currently if we use JMXSecureConnector than we have to disable the clustering > modules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
