[jira] Updated: (GERONIMO-4757) "java.lang.IllegalStateException" error when use install-plugin goal
[ https://issues.apache.org/jira/browse/GERONIMO-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu updated GERONIMO-4757: --- Attachment: GERONIMO-4757.patch Pls help review it, thanks. > "java.lang.IllegalStateException" error when use install-plugin goal > > > Key: GERONIMO-4757 > URL: https://issues.apache.org/jira/browse/GERONIMO-4757 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: geronimo-maven-plugin >Affects Versions: 2.1.4, 2.1.5, 2.2 > Environment: os:windows >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Attachments: GERONIMO-4757.patch > > > 1.Maven repository is c::\Documents and > Settings\Administrator.IBM-B92C72F1CB7\.m2\repository, > Build plugin-farm-it plugin under plugins/clustering/pluin-farm-it > there is an execution in its pom.xml which install this plugin-farm-it plugin > to maven repository > > install-plugin > install > > install-plugin > > > > > > > 2.But when it execute install-plugin goal, there is an error: > 2009-07-21 10:40:20,859 ERROR [PluginRepositoryDownloader] Unable to format > plugin repository URL C:\Documents and > Settings\Administrator.IBM-B92C72F1CB7\.m2\repository/ > java.net.URISyntaxException: Illegal character in opaque part at index 2: > C:\Documents and Settings\Administrator.IBM-B92C72F1CB7\.m2\repository/ > at java.net.URI$Parser.fail(URI.java:2821) > at java.net.URI$Parser.checkChars(URI.java:2994) > at java.net.URI$Parser.parse(URI.java:3031) > at java.net.URI.(URI.java:590) > at > org.apache.geronimo.system.plugin.PluginRepositoryDownloader.resolveRepository(PluginRepositoryDownloader.java:231) > at > org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getSourceRepository(PluginRepositoryDownloader.java:202) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.getDefaultSourceRepository(PluginInstallerGBean.java:670) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:713) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean$3.run(PluginInstallerGBean.java:885) > at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) > at > org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > at java.lang.Thread.run(Thread.java:810) > Exception in thread "DefaultThreadPool 0" java.lang.IllegalStateException: > Can't locate repo C:\Documents and > Settings\Administrator.IBM-B92C72F1CB7\.m2\repository > at > org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getSourceRepository(PluginRepositoryDownloader.java:204) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.getDefaultSourceRepository(PluginInstallerGBean.java:670) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:713) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean$3.run(PluginInstallerGBean.java:885) > at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) > at > org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > at java.lang.Thread.run(Thread.java:810) > It's cozed by maven repositry path containing space, which is forbidden in > URI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4757) "java.lang.IllegalStateException" error when use install-plugin goal
"java.lang.IllegalStateException" error when use install-plugin goal Key: GERONIMO-4757 URL: https://issues.apache.org/jira/browse/GERONIMO-4757 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: geronimo-maven-plugin Affects Versions: 2.1.4, 2.1.5, 2.2 Environment: os:windows Reporter: viola.lu Assignee: viola.lu Priority: Minor 1.Maven repository is c::\Documents and Settings\Administrator.IBM-B92C72F1CB7\.m2\repository, Build plugin-farm-it plugin under plugins/clustering/pluin-farm-it there is an execution in its pom.xml which install this plugin-farm-it plugin to maven repository install-plugin install install-plugin 2.But when it execute install-plugin goal, there is an error: 2009-07-21 10:40:20,859 ERROR [PluginRepositoryDownloader] Unable to format plugin repository URL C:\Documents and Settings\Administrator.IBM-B92C72F1CB7\.m2\repository/ java.net.URISyntaxException: Illegal character in opaque part at index 2: C:\Documents and Settings\Administrator.IBM-B92C72F1CB7\.m2\repository/ at java.net.URI$Parser.fail(URI.java:2821) at java.net.URI$Parser.checkChars(URI.java:2994) at java.net.URI$Parser.parse(URI.java:3031) at java.net.URI.(URI.java:590) at org.apache.geronimo.system.plugin.PluginRepositoryDownloader.resolveRepository(PluginRepositoryDownloader.java:231) at org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getSourceRepository(PluginRepositoryDownloader.java:202) at org.apache.geronimo.system.plugin.PluginInstallerGBean.getDefaultSourceRepository(PluginInstallerGBean.java:670) at org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:713) at org.apache.geronimo.system.plugin.PluginInstallerGBean$3.run(PluginInstallerGBean.java:885) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:810) Exception in thread "DefaultThreadPool 0" java.lang.IllegalStateException: Can't locate repo C:\Documents and Settings\Administrator.IBM-B92C72F1CB7\.m2\repository at org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getSourceRepository(PluginRepositoryDownloader.java:204) at org.apache.geronimo.system.plugin.PluginInstallerGBean.getDefaultSourceRepository(PluginInstallerGBean.java:670) at org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:713) at org.apache.geronimo.system.plugin.PluginInstallerGBean$3.run(PluginInstallerGBean.java:885) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:810) It's cozed by maven repositry path containing space, which is forbidden in URI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Discuss] ApacheCon '09 Geronimo Track: Content
Looking at these proposals, my thoughts are pulled towards where is Geronimo going? Even though, we're busy finalizing a 2.2 release, I'd like to see a good portion of our session focused on where we're taking Geronimo. Hopefully, we'd already have a lot of actual implementation to discuss by November. So, looking towards a Geronimo of the future, I think of Blueprint, OSGi and EE6. That would leave me with the following talks. I might even ask if we can adjust the talks, slightly, to help with the overall theme. * Blueprint Container Specification and Geronimo * Custom Server Assemblies (include a good overview of Geronimo and OSGi) * JPA 2.0 Specification (also include a general EE 6 outlook?) Apologies if I'm playing editor too much. Feel free to whack my hands with a ruler... Vamsi, I think your topics are great and relevant. I know that some are proposed for the general sessions. I'd certainly love to see one or more, there... They just aren't in-sync with where my thoughts are running for the Geronimo track. --kevan
[Discuss] ApacheCon '09 Geronimo Track: Content
I had an IRC chat with Emmanuel Lecharny from Apache Directory. We decided that Geronimo would use the 3 afternoon talks and Directory will hold the two morning talks. IIUC, this means we'll have the following time slots: 2:30-3:20 Session 1 3:20-4:00 Break 4:00-4:50 Session 2 5:00-5:50 Session 3 I think the first few minutes of Session 1 will be used as an introduction and preview of the track. Since a Break follows Session 1, we could easily run 10 minutes over, without causing tremendous hardship to anyone. So, we should have room for 3 full sessions. That leaves the hard task of choosing. I have my thoughts and will follow up on this email thread... Proposals are: Blueprint Container Specification and Geornimo -- Jarek Geronimo Custom Server Assemblies -- David J JPA 2.0 Specification and Geronimo -- Donald Administering Apache Geronimo 2.x -- Vamsi Securing Java EE 5.0 Applications with Apache Geronimo -- Vamsi Load Balancing and high-availability with Geronimo clusters -- Vamsi --kevan
[jira] Commented: (GERONIMODEVTOOLS-510) Deployment plan editor warning message when opening source tab for openejb-jar.xml file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733487#action_12733487 ] Rodger Zhang commented on GERONIMODEVTOOLS-510: --- http://openejb.apache.org/xml/ns/openejb-jar-2.2 http://openejb.apache.org/xml/ns/pkgen-2.1 are not available. These urls are not linked to: http://openejb.apache.org/xml/ns/openejb-jar-2.2.xsd http://openejb.apache.org/xml/ns/pkgen-2.1.xsd So,the openejb-jar.xml created by GEP like http://geronimo.apache.org/xml/ns/j2ee/application-2.0"; xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0"; xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"; xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"; xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"; xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2"; xmlns:pers="http://java.sun.com/xml/ns/persistence"; xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"; xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"; xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1";> default 1.0 car === has a warning:"No grammar constraints (DTD or XML schema) detected for the document." Some should fix it. > Deployment plan editor warning message when opening source tab for > openejb-jar.xml file > --- > > Key: GERONIMODEVTOOLS-510 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-510 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.3 >Reporter: Tim McConnell >Assignee: Tim McConnell >Priority: Minor > Fix For: 2.2.0 > > > Warning message as shown in Eclipse: > No grammar constraints (DTD or XML schema) detected for the document. > openejb-jar.xml testEJB/ejbModule/META-INF line 1 XML Problem -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Welcome "Delos" Xuan Dai as a new committer
Congratulations! -Jack On Tue, Jul 21, 2009 at 12:09 PM, chi runhua wrote: > Way to go, Delos~! > > Jeff > > On Tue, Jul 21, 2009 at 11:16 AM, Ying Tang wrote: > >> Congratulations, Delos! >> >> 2009/7/21, Rex Wang : >> > congrats! :) >> > >> > -Rex >> > >> > 2009/7/21 Shawn Jiang >> > >> >> Congratulations ! >> >> >> >> >> >> On Tue, Jul 21, 2009 at 9:56 AM, Delos wrote: >> >> >> >>> Thank you very much for all your help! >> >>> >> >>> I'm so honored to contribute to the community. -:) >> >>> >> >>> 2009/7/21 Joe Bohn >> >>> >> >>> Congratulations Delos! >> >> >> >> Donald Woods wrote: >> >> > I would like to welcome Delos aboard, as he recently accepted the >> > Geronimo PMC invitation to become a committer. His account was >> created >> > last >> > week (delos), so you should start seeing some commits from him as >> soon >> > as we >> > finish granting him karma. >> > >> > >> > -Donald >> > >> > >> >> >>> >> >>> >> >>> -- >> >>> Best Regards, >> >>> >> >>> Delos >> >>> >> >> >> >> >> >> >> >> -- >> >> Shawn >> >> >> > >> > >
Re: ApacheCon '09 Geronimo Track Call for Papers
Thanks everyone! Lots of good topics there. I think they are all deserving. I'll start a discussion thread to finalize the content. --kevan
Re: Welcome "Delos" Xuan Dai as a new committer
Way to go, Delos~! Jeff On Tue, Jul 21, 2009 at 11:16 AM, Ying Tang wrote: > Congratulations, Delos! > > 2009/7/21, Rex Wang : > > congrats! :) > > > > -Rex > > > > 2009/7/21 Shawn Jiang > > > >> Congratulations ! > >> > >> > >> On Tue, Jul 21, 2009 at 9:56 AM, Delos wrote: > >> > >>> Thank you very much for all your help! > >>> > >>> I'm so honored to contribute to the community. -:) > >>> > >>> 2009/7/21 Joe Bohn > >>> > >>> Congratulations Delos! > > > > Donald Woods wrote: > > > I would like to welcome Delos aboard, as he recently accepted the > > Geronimo PMC invitation to become a committer. His account was > created > > last > > week (delos), so you should start seeing some commits from him as > soon > > as we > > finish granting him karma. > > > > > > -Donald > > > > > > >>> > >>> > >>> -- > >>> Best Regards, > >>> > >>> Delos > >>> > >> > >> > >> > >> -- > >> Shawn > >> > > >
Re: web console strange behavior
Also can not recreate in my firefox & IE8.0, windows xp. also trunk tomcat build. -Rex 2009/7/21 David Jencks > I wonder if this is expected or something that is just broken on my > machine... > > I went to the web app page in the admin console and uninstalled one app > the console popped up what I think is a dojo confirmation dialog box. > Then I uninstalled another app and it just uninstalled it without asking > for confirmation. > > Is this expected//anyone else see this? > > thanks > david jencks >
Re: Welcome "Delos" Xuan Dai as a new committer
Congratulations, Delos! 2009/7/21, Rex Wang : > congrats! :) > > -Rex > > 2009/7/21 Shawn Jiang > >> Congratulations ! >> >> >> On Tue, Jul 21, 2009 at 9:56 AM, Delos wrote: >> >>> Thank you very much for all your help! >>> >>> I'm so honored to contribute to the community. -:) >>> >>> 2009/7/21 Joe Bohn >>> >>> Congratulations Delos! Donald Woods wrote: > I would like to welcome Delos aboard, as he recently accepted the > Geronimo PMC invitation to become a committer. His account was created > last > week (delos), so you should start seeing some commits from him as soon > as we > finish granting him karma. > > > -Donald > > >>> >>> >>> -- >>> Best Regards, >>> >>> Delos >>> >> >> >> >> -- >> Shawn >> >
Re: Welcome "Delos" Xuan Dai as a new committer
congrats! :) -Rex 2009/7/21 Shawn Jiang > Congratulations ! > > > On Tue, Jul 21, 2009 at 9:56 AM, Delos wrote: > >> Thank you very much for all your help! >> >> I'm so honored to contribute to the community. -:) >> >> 2009/7/21 Joe Bohn >> >> Congratulations Delos! >>> >>> >>> >>> Donald Woods wrote: >>> I would like to welcome Delos aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was created last week (delos), so you should start seeing some commits from him as soon as we finish granting him karma. -Donald >>> >> >> >> -- >> Best Regards, >> >> Delos >> > > > > -- > Shawn >
[jira] Commented: (GERONIMO-4725) MySQL jdbc connector/driver jars don't show up in the database pool wizard
[ https://issues.apache.org/jira/browse/GERONIMO-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733451#action_12733451 ] Rex Wang commented on GERONIMO-4725: Hi, Jurgen, try rename your jar as: mysql-connector-java-3.1.14.jar and then add it to /mysql/mysql-connector-java/3.1.14/mysql-connector-java-3.1.14.jar -Rex > MySQL jdbc connector/driver jars don't show up in the database pool wizard > -- > > Key: GERONIMO-4725 > URL: https://issues.apache.org/jira/browse/GERONIMO-4725 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.4 > Environment: Geronimo 2.1.4, WindowsXP >Reporter: Jan Snelders >Assignee: Rex Wang > Fix For: 2.1.4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > MySQL connector/driver jars don't show up in the database pool wizard when > added to the repository even if you download the 3.x.x driver using the exact > same wizard. > Steps to reproduce; > - Start a newly installed geronimo 2.1.4. server (I only tested on WindowsXP) > - login to the web console > - Start adding a connection pool using the 'Geronimo database pool wizard' > - Choose 'MySQL' for 'Database Type' and click on 'Next' to go to the next > step > - The multiple select control labeled; 'Driver JAR' is empty at this time, > choose 'Download a driver' and install the MySQL Connector /J 3.1.12 > - When done installing the connector the wizard refuses to show the installed > connector/driver > - The problem also accures also when mannually adding the latest MySQL > connector to the repository (under the group "mysql") > This bug is not present in geronimo 2.1.3 (tested on WindowsXP) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Welcome "Delos" Xuan Dai as a new committer
Congratulations ! On Tue, Jul 21, 2009 at 9:56 AM, Delos wrote: > Thank you very much for all your help! > > I'm so honored to contribute to the community. -:) > > 2009/7/21 Joe Bohn > > Congratulations Delos! >> >> >> >> Donald Woods wrote: >> >>> I would like to welcome Delos aboard, as he recently accepted the >>> Geronimo PMC invitation to become a committer. His account was created last >>> week (delos), so you should start seeing some commits from him as soon as we >>> finish granting him karma. >>> >>> >>> -Donald >>> >>> >> > > > -- > Best Regards, > > Delos > -- Shawn
Re: web console strange behavior
Can't recreate this with firefox 3.5 on windows XP. I'm using the trunk 20090717 tomcat build. On Tue, Jul 21, 2009 at 7:43 AM, David Jencks wrote: > I wonder if this is expected or something that is just broken on my > machine... > > I went to the web app page in the admin console and uninstalled one app > the console popped up what I think is a dojo confirmation dialog box. > Then I uninstalled another app and it just uninstalled it without asking > for confirmation. > > Is this expected//anyone else see this? > > thanks > david jencks > -- Shawn
[jira] Resolved: (GERONIMO-4755) Warning message when starting the server due to Tomcat class not found
[ https://issues.apache.org/jira/browse/GERONIMO-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai resolved GERONIMO-4755. Resolution: Duplicate Duplicate with GERONIMO-4713 > Warning message when starting the server due to Tomcat class not found > -- > > Key: GERONIMO-4755 > URL: https://issues.apache.org/jira/browse/GERONIMO-4755 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 >Reporter: Jack Cai >Priority: Minor > > When starting the 2.2 server (tomcat assembly), the below warning message > will always appear during the starting of the juddi server. > WARN [NamingContextListener] Failed to register in JMX: > javax.naming.NamingException: Could not create resource factory instance > [Root exception is java.lang.ClassNotFoundException: > org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory] > Initial investigation shows that Tomcat uses the class > "org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory" as the default > datasource factory class, see org.apache.naming.factory.ResourceFactory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 796084
Geronimo Revision: 796084 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/build-2100.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 39 minutes 33 seconds [INFO] Finished at: Mon Jul 20 21:43:58 EDT 2009 [INFO] Final Memory: 467M/993M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/logs-2100-tomcat/ [INFO] --- [INFO] [INFO] commands-testsuite/deploy RUNNING [INFO] commands-testsuite/deploy SUCCESS (0:01:04.874) [INFO] commands-testsuite/gshell RUNNING [INFO] commands-testsuite/gshell SUCCESS (0:00:33.103) [INFO] commands-testsuite/jaxws RUNNING [INFO] commands-testsuite/jaxws SUCCESS (0:00:38.396) [INFO] commands-testsuite/shutdownRUNNING [INFO] commands-testsuite/shutdownSUCCESS (0:00:20.659) [INFO] concurrent-testsuite/concurrent-basic RUNNING [INFO] concurrent-testsuite/concurrent-basic FAILURE (0:01:05.920) Java returned: 1 [INFO] console-testsuite/advanced RUNNING [INFO] console-testsuite/advanced SUCCESS (0:01:30.980) [INFO] console-testsuite/basicRUNNING [INFO] console-testsuite/basicSUCCESS (0:01:59.547) [INFO] corba-testsuite/corba-helloworld RUNNING [INFO] corba-testsuite/corba-helloworld FAILURE (0:00:37.570) Java returned: 1 [INFO] corba-testsuite/corba-marshal RUNNING [INFO] corba-testsuite/corba-marshal FAILURE (0:00:29.586) Java returned: 1 [INFO] corba-testsuite/corba-mytime RUNNING [INFO] corba-testsuite/corba-mytime FAILURE (0:00:37.022) Java returned: 1 [INFO] deployment-testsuite/deployment-tests RUNNING [INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.034) [INFO] deployment-testsuite/jca-cms-tests RUNNING [INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:32.493) [INFO] deployment-testsuite/manifestcp-tests RUNNING [INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.856) [INFO] enterprise-testsuite/ejb-tests RUNNING [INFO] enterprise-testsuite/ejb-tests FAILURE (0:01:10.634) Java returned: 1 [INFO] enterprise-testsuite/jms-tests RUNNING [INFO] enterprise-testsuite/jms-tests FAILURE (0:00:45.736) Java returned: 1 [INFO] enterprise-testsuite/jpa-tests RUNNING [INFO] enterprise-testsuite/jpa-tests FAILURE (0:00:45.520) Java returned: 1 [INFO] enterprise-testsuite/sec-clientRUNNING [INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:29.335) [INFO] enterprise-testsuite/sec-tests RUNNING [INFO] enterprise-testsuite/sec-tests FAILURE (0:00:36.582) Java returned: 1 [INFO] security-testsuite/test-security RUNNING [INFO] security-testsuite/test-security FAILURE (0:00:46.057) Java returned: 1 [INFO] web-testsuite/test-2.1-jspsRUNNING [INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:37.592) [INFO] web-testsuite/test-2.5-servletsRUNNING [INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.544) [INFO] web-testsuite/test-myfaces RUNNING [INFO] web-testsuite/test-myfaces SUCCESS (0:00:34.281) [INFO] web-testsuite/test-tomcat RUNNING [INFO] web-testsuite/test-tomcat SUCCESS (0:00:25.296) [INFO] web-testsuite/test-web-forward RUNNING [INFO] web-testsuite/test-web-forward FAILURE (0:00:34.983) Java returned: 1 [INFO] web-testsuite/test-web-references RUNNING [INFO] web-testsuite/test-web-references FAILURE (0:00:39.336) Java returned: 1 [INFO] webservices-testsuite/jaxb-tests RUNNING [INFO] webservices-testsuite/jaxb-tests SUCCESS (0:01:05.884) [INFO] webservices-testsuite/jaxr-tests RUNNING [INFO] webservices-testsuite/jaxr-tests SUCCESS (0:00:59.418) [INFO] webservices-testsuite/jaxrpc-jaxws-tests RUNNING [INFO] webservices-testsuite/jaxrpc-jaxws-tests SUCCESS (0:00:38.998) [INFO] webservices-testsuite/jaxrpc-tests RUNNING [INFO] webservices-testsuite/jaxrpc-tests SUCCESS (0:00:48.394) [INFO] webservices-testsuite/jaxws-catalog-tests RUNNING [INFO] webservices
Re: Welcome "Delos" Xuan Dai as a new committer
Thank you very much for all your help! I'm so honored to contribute to the community. -:) 2009/7/21 Joe Bohn > Congratulations Delos! > > > > Donald Woods wrote: > >> I would like to welcome Delos aboard, as he recently accepted the Geronimo >> PMC invitation to become a committer. His account was created last week >> (delos), so you should start seeing some commits from him as soon as we >> finish granting him karma. >> >> >> -Donald >> >> > -- Best Regards, Delos
web console strange behavior
I wonder if this is expected or something that is just broken on my machine... I went to the web app page in the admin console and uninstalled one app the console popped up what I think is a dojo confirmation dialog box. Then I uninstalled another app and it just uninstalled it without asking for confirmation. Is this expected//anyone else see this? thanks david jencks
Re: [BUILD] trunk: Failed for Revision: 795940
I looked at the tomcat security-testsuite/test-security failures and think the either test or the tomcat default servlet is wrong. The test tries to access http://localhost:8080/demo/protect/hello.html Its protected, so you get dispatched to the login form. You can then login just fine. However, firefox thinks the login form is the actual content so it keeps showing it to you. If you press the refresh button, you get the expected content. For some reason safari works more smoothly. Anyone know how to prevent firefox from caching the login form? thanks david jencks On Jul 20, 2009, at 1:43 PM, ga...@apache.org wrote: Geronimo Revision: 795940 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 43 minutes 20 seconds [INFO] Finished at: Mon Jul 20 15:47:48 EDT 2009 [INFO] Final Memory: 401M/1003M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/logs-1500-tomcat/ [INFO] Using geronimoHome: /home/geronimo/geronimo/trunk/testsuite/ target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT [INFO] Installing assembly... [INFO] Expanding: /home/geronimo/.m2/repository/org/apache/geronimo/ assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6- javaee5-2.2-SNAPSHOT-bin.zip into /home/geronimo/geronimo/trunk/ testsuite/target [INFO] Starting Geronimo server... [INFO] Selected option set: default [INFO] Redirecting output to: /home/geronimo/geronimo/trunk/ testsuite/target/geronimo-logs/ org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log [INFO] Waiting for Geronimo server... [INFO] Geronimo server started in 0:00:47.079 [INFO] [shitty:install {execution: default}] [INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/ testsuite/testing/testsuite-testing.pom [INFO] [shitty:test {execution: default}] [INFO] Starting 36 test builds [INFO] [INFO] --- [INFO] [INFO] commands-testsuite/deploy RUNNING [INFO] commands-testsuite/deploy SUCCESS (0:01:18.934) [INFO] commands-testsuite/gshell RUNNING [INFO] commands-testsuite/gshell SUCCESS (0:00:35.141) [INFO] commands-testsuite/jaxws RUNNING [INFO] commands-testsuite/jaxws SUCCESS (0:00:41.560) [INFO] commands-testsuite/shutdownRUNNING [INFO] commands-testsuite/shutdownSUCCESS (0:00:21.053) [INFO] concurrent-testsuite/concurrent-basic RUNNING [INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:32.226) [INFO] console-testsuite/advanced RUNNING [INFO] console-testsuite/advanced SUCCESS (0:01:36.615) [INFO] console-testsuite/basicRUNNING [INFO] console-testsuite/basicSUCCESS (0:02:03.304) [INFO] corba-testsuite/corba-helloworld RUNNING [INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:52.655) [INFO] corba-testsuite/corba-marshal RUNNING [INFO] corba-testsuite/corba-marshal SUCCESS (0:01:05.044) [INFO] corba-testsuite/corba-mytime RUNNING [INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.602) [INFO] deployment-testsuite/deployment-tests RUNNING [INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.435) [INFO] deployment-testsuite/jca-cms-tests RUNNING [INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.921) [INFO] deployment-testsuite/manifestcp-tests RUNNING [INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.717) [INFO] enterprise-testsuite/ejb-tests RUNNING [INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:11.912) [INFO] enterprise-testsuite/jms-tests RUNNING [INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.206) [INFO] enterprise-testsuite/jpa-tests RUNNING [INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.272) [INFO] enterprise-testsuite/sec-clientRUNNING [INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.209) [INFO] enterprise-testsuite/sec-tests RUNNING [INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.764) [INFO] security-testsuite/test-security
[jira] Closed: (GERONIMO-4737) geronimo source code should follow resource filtering best practice defined in genesis.
[ https://issues.apache.org/jira/browse/GERONIMO-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4737. -- Resolution: Fixed rev 796043. I had to modify the svn command script extensively: - in general it's better to do svn mv on your local machine unless you are movng or copying an entire module. Otherwise there is no way to fine out if the change breaks everything. - When I edited the script to operate on my local working copy, it copied resources to filtered-resources/resources. The resulting servers seem to build and start OK. > geronimo source code should follow resource filtering best practice defined > in genesis. > --- > > Key: GERONIMO-4737 > URL: https://issues.apache.org/jira/browse/GERONIMO-4737 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 2.2 >Reporter: Shawn Jiang >Assignee: David Jencks >Priority: Minor > Fix For: 2.2 > > Attachments: G4737_filter_svn_commands_patch.txt, > G4737_filter_svn_commands_patch.txt, G4737_trunk > > > See the filtering setting in > http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis-default-flava/2.0/genesis-default-flava-2.0.pom > {code} > > > ${project.basedir}/src/main/resources > false > > **/* > > > > > ${project.basedir}/src/main/filtered-resources > true > > **/* > > > > > > ${project.basedir}/src/test/resources > false > > **/* > > > > > ${project.basedir}/src/test/filtered-resources > true > > **/* > > > > {code} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4737) geronimo source code should follow resource filtering best practice defined in genesis.
[ https://issues.apache.org/jira/browse/GERONIMO-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-4737: --- Attachment: G4737_filter_svn_commands_patch.txt Ths svn script I actually used, modified from shawn's > geronimo source code should follow resource filtering best practice defined > in genesis. > --- > > Key: GERONIMO-4737 > URL: https://issues.apache.org/jira/browse/GERONIMO-4737 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 2.2 >Reporter: Shawn Jiang >Assignee: David Jencks >Priority: Minor > Fix For: 2.2 > > Attachments: G4737_filter_svn_commands_patch.txt, > G4737_filter_svn_commands_patch.txt, G4737_trunk > > > See the filtering setting in > http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis-default-flava/2.0/genesis-default-flava-2.0.pom > {code} > > > ${project.basedir}/src/main/resources > false > > **/* > > > > > ${project.basedir}/src/main/filtered-resources > true > > **/* > > > > > > ${project.basedir}/src/test/resources > false > > **/* > > > > > ${project.basedir}/src/test/filtered-resources > true > > **/* > > > > {code} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 795940
Geronimo Revision: 795940 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 43 minutes 20 seconds [INFO] Finished at: Mon Jul 20 15:47:48 EDT 2009 [INFO] Final Memory: 401M/1003M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/logs-1500-tomcat/ [INFO] Using geronimoHome: /home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT [INFO] Installing assembly... [INFO] Expanding: /home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip into /home/geronimo/geronimo/trunk/testsuite/target [INFO] Starting Geronimo server... [INFO] Selected option set: default [INFO] Redirecting output to: /home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log [INFO] Waiting for Geronimo server... [INFO] Geronimo server started in 0:00:47.079 [INFO] [shitty:install {execution: default}] [INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom [INFO] [shitty:test {execution: default}] [INFO] Starting 36 test builds [INFO] [INFO] --- [INFO] [INFO] commands-testsuite/deploy RUNNING [INFO] commands-testsuite/deploy SUCCESS (0:01:18.934) [INFO] commands-testsuite/gshell RUNNING [INFO] commands-testsuite/gshell SUCCESS (0:00:35.141) [INFO] commands-testsuite/jaxws RUNNING [INFO] commands-testsuite/jaxws SUCCESS (0:00:41.560) [INFO] commands-testsuite/shutdownRUNNING [INFO] commands-testsuite/shutdownSUCCESS (0:00:21.053) [INFO] concurrent-testsuite/concurrent-basic RUNNING [INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:32.226) [INFO] console-testsuite/advanced RUNNING [INFO] console-testsuite/advanced SUCCESS (0:01:36.615) [INFO] console-testsuite/basicRUNNING [INFO] console-testsuite/basicSUCCESS (0:02:03.304) [INFO] corba-testsuite/corba-helloworld RUNNING [INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:52.655) [INFO] corba-testsuite/corba-marshal RUNNING [INFO] corba-testsuite/corba-marshal SUCCESS (0:01:05.044) [INFO] corba-testsuite/corba-mytime RUNNING [INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.602) [INFO] deployment-testsuite/deployment-tests RUNNING [INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.435) [INFO] deployment-testsuite/jca-cms-tests RUNNING [INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.921) [INFO] deployment-testsuite/manifestcp-tests RUNNING [INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.717) [INFO] enterprise-testsuite/ejb-tests RUNNING [INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:11.912) [INFO] enterprise-testsuite/jms-tests RUNNING [INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.206) [INFO] enterprise-testsuite/jpa-tests RUNNING [INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.272) [INFO] enterprise-testsuite/sec-clientRUNNING [INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.209) [INFO] enterprise-testsuite/sec-tests RUNNING [INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.764) [INFO] security-testsuite/test-security RUNNING [INFO] security-testsuite/test-security FAILURE (0:00:45.377) Java returned: 1 [INFO] web-testsuite/test-2.1-jspsRUNNING [INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:32.745) [INFO] web-testsuite/test-2.5-servletsRUNNING [INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.136) [INFO] web-testsuite/test-myfaces RUNNING [INFO] web-testsuite/test-myfaces SUCCESS (0:00:32.963) [INFO] web-testsuite/test-tomcat RUNNING [INFO] web-testsuite/test-tomcat FAILURE (0:00:19.778) Java returned: 1 [INFO] web-testsuite/test-web-forward
[jira] Assigned: (GERONIMO-4737) geronimo source code should follow resource filtering best practice defined in genesis.
[ https://issues.apache.org/jira/browse/GERONIMO-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-4737: -- Assignee: David Jencks (was: Shawn Jiang) > geronimo source code should follow resource filtering best practice defined > in genesis. > --- > > Key: GERONIMO-4737 > URL: https://issues.apache.org/jira/browse/GERONIMO-4737 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 2.2 >Reporter: Shawn Jiang >Assignee: David Jencks >Priority: Minor > Fix For: 2.2 > > Attachments: G4737_filter_svn_commands_patch.txt, G4737_trunk > > > See the filtering setting in > http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis-default-flava/2.0/genesis-default-flava-2.0.pom > {code} > > > ${project.basedir}/src/main/resources > false > > **/* > > > > > ${project.basedir}/src/main/filtered-resources > true > > **/* > > > > > > ${project.basedir}/src/test/resources > false > > **/* > > > > > ${project.basedir}/src/test/filtered-resources > true > > **/* > > > > {code} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4753) Upgrade dwr to 3.0.M1 or figure out why it won't work
[ https://issues.apache.org/jira/browse/GERONIMO-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733307#action_12733307 ] David Jencks commented on GERONIMO-4753: I went ahead and upgraded in rev 795946 (along with several other build tweaks). I couldn't see any problems in the console, but I also don't know where to look. > Upgrade dwr to 3.0.M1 or figure out why it won't work > - > > Key: GERONIMO-4753 > URL: https://issues.apache.org/jira/browse/GERONIMO-4753 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem, console >Affects Versions: 2.2 >Reporter: David Jencks > Fix For: 2.2 > > > The last artifact in the svn repo is dwr. We need to upgrade to 3.0.M1 which > is available through maven or figure out some other strategy, possibly trying > to convince the dwr team to release 2.0.5 through maven. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ApacheCon '09 Geronimo Track Call for Papers
* Title Load balancing and high-availability with Geronimo clusters * Speaker name(s) Vamsavardhana Reddy Chillakuru * Abstract (Short overview of the talk contents) Apache Geronimo 2.x is certified Java Enterprise Edition 5.0 container suitable for everything from a development environment to enterprise-level deployments. Geronimo can be clustered in different ways, for e.g. using clustering capabilities provided by Tomcat, using the WADI integration of Geronimo, etc. This session details on various clustering options available with Geronimo and configuring load-balancing and failover of web applications using mod_jk & Apache HTTP Server. After completing this session, the audience will be familiar with the clustering and farming features provided by Geronimo, running multiple instances of Geronimo server from the same installation, preparing their applications for deployment on the cluster and know how to configure Geronimo clusters to suit their needs. *Bio: Vamsavardhana Reddy Chillakuru a.k.a. Vamsi is an Advisory Software Engineer working with IBM India Private Limited since 1996 and has over 12 years experience in the IT industry. He is a committer on Apache Geronimo and Apache Tuscany projects and member of the Apache Geronimo PMC. On Mon, Jul 20, 2009 at 10:42 PM, Kevan Miller wrote: > > On Jul 20, 2009, at 9:33 AM, jean-frederic clere wrote: > > On 07/20/2009 09:18 AM, Vamsavardhana Reddy wrote: >> >>> Just wondering what happens to the proposals submitted through >>> conference web site. >>> >> >> They can be used too if Geronimo decides to do so. >> > > Vamsi, > You should post your proposal(s) here, for consideration in the Geronimo > track... Will give this some more time... > > --kevan > -- Vamsi
Re: Default Subject configuration for Jetty assembility
Well, its a bug :- )https://issues.apache.org/jira/browse/GERONIMO-4756 I think I fixed it but don't have a test case handy. Could you check? thanks david jencks On Jul 20, 2009, at 4:39 AM, Trygve Hardersen wrote: I'm also having this problem. Are you saying it will work if I configure JASPI authentication? Thanks Trygve On Mon, Jul 20, 2009 at 11:17 AM, Ivan wrote: Hi, While working with the current 2.2 Jetty assembility, I found that the way we used to configure the default subject does not take effect again. After checking the codes, it seems that, currently, jetty builder will always check for the jaspi authentication configuration, if not found, the runassource will be ignored. I wonder whether it is by design or an issue. Thanks for any comment ! -- Ivan
[jira] Commented: (GERONIMO-4756) jetty 7 ignores default subject settings unless authentication is set up
[ https://issues.apache.org/jira/browse/GERONIMO-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733303#action_12733303 ] David Jencks commented on GERONIMO-4756: I think rev 795937 should fix this but I don't have a test case handy. > jetty 7 ignores default subject settings unless authentication is set up > > > Key: GERONIMO-4756 > URL: https://issues.apache.org/jira/browse/GERONIMO-4756 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.2 > > > Jetty 7 should be setting up security stuff if a is > definied, not only if authentication is specifically configured: this will > make default subjects work when no auth is configured. Should not be a > problem for tomcat for some reason I found this problem there already :-) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ApacheCon '09 Geronimo Track Call for Papers
* Title Securing Java EE 5.0 Applications with Apache Geronimo * Speaker name(s) Vamsavardhana Reddy Chillakuru * Abstract (Short overview of the talk contents) Security is always a high priority in application development, and with complex applications the task becomes even more daunting. While the Java EE specification, JAAS and JACC provide a step in the right direction, every application server is free to implement container security differently. Apache Geronimo, a JEE 5.0 certified container, enables storing user credentials in a variety of data stores viz., simple text files, a database, an LDAP server and digital certificates. In this session we see how these data stores can be used to configure application security and how the necessary infrastructure can be run in Apache Geronimo itself. The session presents: a) Prerequisites for PropertiesFile, Database, LDAP and CertificatePropertiesFile realms and shows how to create these realms. b) Advanced features like auditing, lockout after repeated failures, prinicipal wrapping, single-sign-on, etc. c) Configuring Web/EJB/EAR application security. After completing this session, the audience will gain knowledge on their choice of data stores for user credentials, create various security realms and deployment plans necessary to secure their applications with Geronimo. * Bio: Vamsavardhana Reddy Chillakuru a.k.a. Vamsi is an Advisory Software Engineer working with IBM India Private Limited since 1996 and has over 12 years experience in the IT industry. He is a committer on Apache Geronimo and Apache Tuscany projects and member of the Apache Geronimo PMC. He received his B.Stat.(Hons.) and M.Stat. degrees from Indian Statistical Institute, Kolkata, India in the years 1994 and 1996 respectively. On Mon, Jul 20, 2009 at 10:42 PM, Kevan Miller wrote: > > On Jul 20, 2009, at 9:33 AM, jean-frederic clere wrote: > > On 07/20/2009 09:18 AM, Vamsavardhana Reddy wrote: >> >>> Just wondering what happens to the proposals submitted through >>> conference web site. >>> >> >> They can be used too if Geronimo decides to do so. >> > > Vamsi, > You should post your proposal(s) here, for consideration in the Geronimo > track... Will give this some more time... > > --kevan > -- Vamsi
Re: ApacheCon '09 Geronimo Track Call for Papers
* Title Administering Apache Geronimo 2.x * Speaker name(s) Vamsavardhana Reddy Chillakuru * Abstract (Short overview of the talk contents) Apache Geronimo 2.x is certified Java Enterprise Edition 5.0 container suitable for everything from a development environment to enterprise-level deployments. Geronimo leverages many Apache projects, such as Tomcat, OpenEJB, ActiveMQ, Derby. This session will cover administering Geronimo from two points of view: configuring an existing Geronimo server directly through the powerful web based administration console or editing configuration files, and secondly through Geronimo plugins containing configuration information either used in a custom server assembly or installed into an existing server. Some of the topics covered are: - First steps in getting Geronimo ready for a production environment, - Administering embedded Tomcat, ActiveMQ, Derby. - Managing keys, digital certificates and configuring SSL. - Running a cluster of multiple server instances from the same installation. *Bio: Vamsavardhana Reddy Chillakuru a.k.a. Vamsi is an Advisory Software Engineer working with IBM India Private Limited since 1996 and has over 12 years experience in the IT industry. He is a committer on Apache Geronimo and Apache Tuscany projects and member of the Apache Geronimo PMC. On Mon, Jul 20, 2009 at 10:42 PM, Kevan Miller wrote: > > On Jul 20, 2009, at 9:33 AM, jean-frederic clere wrote: > > On 07/20/2009 09:18 AM, Vamsavardhana Reddy wrote: >> >>> Just wondering what happens to the proposals submitted through >>> conference web site. >>> >> >> They can be used too if Geronimo decides to do so. >> > > Vamsi, > You should post your proposal(s) here, for consideration in the Geronimo > track... Will give this some more time... > > --kevan > -- Vamsi
Re: ApacheCon '09 Geronimo Track Call for Papers
So, just to be a little bit more clear. I'm going to give this call for papers a little more time. Hoping that Vamsi will respond with his proposal. We've had a few last minute proposals. Given that part of the time was the weekend, want to be sure that everyone has a chance... Heck, I may work up a proposal of my own... ;-) --kevan
Re: ApacheCon '09 Geronimo Track Call for Papers
Kevan Miller wrote: Please submit Talk proposals on this mail thread. Each suggestion should include: * Title JPA 2.0 Specification and Geronimo * Speaker name(s) Donald Woods * Abstract (Short overview of the talk contents) This talk will provide a general overview of the new features in JPA 2.0 and how users can start using OpenJPA 2.0.0 with Geronimo 2.2. The talk will describe how to create a Geronimo Server assembly which includes JPA 2.0 support and demonstrate the integration using a simple sample application. * Bio: Donald Woods is an Apache Geronimo committer and PMC member, along with being a committer on the Apache OpenJPA. He has been working on Apache Geronimo since 2005 and has been an IBM employee since 1995. Thanks! Look forward to seeing you at ApacheCon! --kevan
Re: Default Subject configuration for Jetty assembility
Bug, https://issues.apache.org/jira/browse/GERONIMO-4756, Thanks! david jencks On Jul 20, 2009, at 2:17 AM, Ivan wrote: Hi, While working with the current 2.2 Jetty assembility, I found that the way we used to configure the default subject does not take effect again. After checking the codes, it seems that, currently, jetty builder will always check for the jaspi authentication configuration, if not found, the runassource will be ignored. I wonder whether it is by design or an issue. Thanks for any comment ! -- Ivan
[BUILD] branches/2.1: Failed for Revision: 795911
Geronimo Revision: 795911 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090720/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090720/unit-test-reports apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://repository.apache.org/snapshots/), codehaus-snapshots (http://snapshots.repository.codehaus.org), snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20-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.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-1-20070806 2) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20-SNAPSHOT -- 1 required artifact is missing. for artifact: org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-1-20070806 from the specified remote repositories: codehaus.org (http://repository.codehaus.org), ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://repository.apache.org/snapshots/), codehaus-snapshots (http://snapshots.repository.codehaus.org), snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:575) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) 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:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20-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.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-1-20070806 2) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20-SNAPSHOT -- 1 required artifact is missing. for artifact: org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-1-20070806 from the specified remote repositories: codehaus.org (http://repository.codehaus.org), ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://repository.apache.org/snapshots
Re: ApacheCon '09 Geronimo Track Call for Papers
On Jul 20, 2009, at 9:33 AM, jean-frederic clere wrote: On 07/20/2009 09:18 AM, Vamsavardhana Reddy wrote: Just wondering what happens to the proposals submitted through conference web site. They can be used too if Geronimo decides to do so. Vamsi, You should post your proposal(s) here, for consideration in the Geronimo track... Will give this some more time... --kevan
Re: Welcome "Delos" Xuan Dai as a new committer
Congratulations Delos! Donald Woods wrote: I would like to welcome Delos aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was created last week (delos), so you should start seeing some commits from him as soon as we finish granting him karma. -Donald
Re: Welcome "Delos" Xuan Dai as a new committer
Congrates, Delos ! 2009/7/21 Kevan Miller > > On Jul 20, 2009, at 11:42 AM, Donald Woods wrote: > > I would like to welcome Delos aboard, as he recently accepted the Geronimo > PMC invitation to become a committer. His account was created last week > (delos), so you should start seeing some commits from him as soon as we > finish granting him karma. > > > Congrats Delos! > > You should be all set, karma-wise. Look forward to your contributions! > > --kevan > -- Ivan
[jira] Created: (GERONIMO-4756) jetty 7 ignores default subject settings unless authentication is set up
jetty 7 ignores default subject settings unless authentication is set up Key: GERONIMO-4756 URL: https://issues.apache.org/jira/browse/GERONIMO-4756 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.2 Jetty 7 should be setting up security stuff if a is definied, not only if authentication is specifically configured: this will make default subjects work when no auth is configured. Should not be a problem for tomcat for some reason I found this problem there already :-) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Welcome "Delos" Xuan Dai as a new committer
On Jul 20, 2009, at 11:42 AM, Donald Woods wrote: I would like to welcome Delos aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was created last week (delos), so you should start seeing some commits from him as soon as we finish granting him karma. Congrats Delos! You should be all set, karma-wise. Look forward to your contributions! --kevan
Welcome "Delos" Xuan Dai as a new committer
I would like to welcome Delos aboard, as he recently accepted the Geronimo PMC invitation to become a committer. His account was created last week (delos), so you should start seeing some commits from him as soon as we finish granting him karma. -Donald
[BUILD] trunk: Failed for Revision: 795790
Geronimo Revision: 795790 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/build-0900.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 42 minutes 59 seconds [INFO] Finished at: Mon Jul 20 09:47:30 EDT 2009 [INFO] Final Memory: 401M/1007M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/logs-0900-tomcat/ [INFO] Using geronimoHome: /home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT [INFO] Installing assembly... [INFO] Expanding: /home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip into /home/geronimo/geronimo/trunk/testsuite/target [INFO] Starting Geronimo server... [INFO] Selected option set: default [INFO] Redirecting output to: /home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log [INFO] Waiting for Geronimo server... [INFO] Geronimo server started in 0:00:45.202 [INFO] [shitty:install {execution: default}] [INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom [INFO] [shitty:test {execution: default}] [INFO] Starting 36 test builds [INFO] [INFO] --- [INFO] [INFO] commands-testsuite/deploy RUNNING [INFO] commands-testsuite/deploy SUCCESS (0:01:17.713) [INFO] commands-testsuite/gshell RUNNING [INFO] commands-testsuite/gshell SUCCESS (0:00:34.544) [INFO] commands-testsuite/jaxws RUNNING [INFO] commands-testsuite/jaxws SUCCESS (0:00:40.529) [INFO] commands-testsuite/shutdownRUNNING [INFO] commands-testsuite/shutdownSUCCESS (0:00:21.017) [INFO] concurrent-testsuite/concurrent-basic RUNNING [INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:33.428) [INFO] console-testsuite/advanced RUNNING [INFO] console-testsuite/advanced SUCCESS (0:01:33.840) [INFO] console-testsuite/basicRUNNING [INFO] console-testsuite/basicSUCCESS (0:02:02.403) [INFO] corba-testsuite/corba-helloworld RUNNING [INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:53.080) [INFO] corba-testsuite/corba-marshal RUNNING [INFO] corba-testsuite/corba-marshal SUCCESS (0:00:56.810) [INFO] corba-testsuite/corba-mytime RUNNING [INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.742) [INFO] deployment-testsuite/deployment-tests RUNNING [INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.019) [INFO] deployment-testsuite/jca-cms-tests RUNNING [INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.024) [INFO] deployment-testsuite/manifestcp-tests RUNNING [INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.109) [INFO] enterprise-testsuite/ejb-tests RUNNING [INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:25.258) [INFO] enterprise-testsuite/jms-tests RUNNING [INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:58.623) [INFO] enterprise-testsuite/jpa-tests RUNNING [INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:52.062) [INFO] enterprise-testsuite/sec-clientRUNNING [INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.075) [INFO] enterprise-testsuite/sec-tests RUNNING [INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.142) [INFO] security-testsuite/test-security RUNNING [INFO] security-testsuite/test-security FAILURE (0:00:46.121) Java returned: 1 [INFO] web-testsuite/test-2.1-jspsRUNNING [INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.106) [INFO] web-testsuite/test-2.5-servletsRUNNING [INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.159) [INFO] web-testsuite/test-myfaces RUNNING [INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.543) [INFO] web-testsuite/test-tomcat RUNNING [INFO] web-testsuite/test-tomcat FAILURE (0:00:19.604) Java returned: 1 [INFO] web-testsuite/test-web-forward
[jira] Commented: (GERONIMO-4725) MySQL jdbc connector/driver jars don't show up in the database pool wizard
[ https://issues.apache.org/jira/browse/GERONIMO-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733228#action_12733228 ] Jürgen Weber commented on GERONIMO-4725: Got the same problem. Added mysql-connector-java-3.1.14-bin.jar to the repository auf 2.2 07-16 and tried to install a pool. See screenshot. > MySQL jdbc connector/driver jars don't show up in the database pool wizard > -- > > Key: GERONIMO-4725 > URL: https://issues.apache.org/jira/browse/GERONIMO-4725 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.4 > Environment: Geronimo 2.1.4, WindowsXP >Reporter: Jan Snelders >Assignee: Rex Wang > Fix For: 2.1.4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > MySQL connector/driver jars don't show up in the database pool wizard when > added to the repository even if you download the 3.x.x driver using the exact > same wizard. > Steps to reproduce; > - Start a newly installed geronimo 2.1.4. server (I only tested on WindowsXP) > - login to the web console > - Start adding a connection pool using the 'Geronimo database pool wizard' > - Choose 'MySQL' for 'Database Type' and click on 'Next' to go to the next > step > - The multiple select control labeled; 'Driver JAR' is empty at this time, > choose 'Download a driver' and install the MySQL Connector /J 3.1.12 > - When done installing the connector the wizard refuses to show the installed > connector/driver > - The problem also accures also when mannually adding the latest MySQL > connector to the repository (under the group "mysql") > This bug is not present in geronimo 2.1.3 (tested on WindowsXP) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4725) MySQL jdbc connector/driver jars don't show up in the database pool wizard
[ https://issues.apache.org/jira/browse/GERONIMO-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen Weber updated GERONIMO-4725: --- Attachment: screenshot-2.jpg > MySQL jdbc connector/driver jars don't show up in the database pool wizard > -- > > Key: GERONIMO-4725 > URL: https://issues.apache.org/jira/browse/GERONIMO-4725 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.4 > Environment: Geronimo 2.1.4, WindowsXP >Reporter: Jan Snelders >Assignee: Rex Wang > Fix For: 2.1.4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > MySQL connector/driver jars don't show up in the database pool wizard when > added to the repository even if you download the 3.x.x driver using the exact > same wizard. > Steps to reproduce; > - Start a newly installed geronimo 2.1.4. server (I only tested on WindowsXP) > - login to the web console > - Start adding a connection pool using the 'Geronimo database pool wizard' > - Choose 'MySQL' for 'Database Type' and click on 'Next' to go to the next > step > - The multiple select control labeled; 'Driver JAR' is empty at this time, > choose 'Download a driver' and install the MySQL Connector /J 3.1.12 > - When done installing the connector the wizard refuses to show the installed > connector/driver > - The problem also accures also when mannually adding the latest MySQL > connector to the repository (under the group "mysql") > This bug is not present in geronimo 2.1.3 (tested on WindowsXP) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-4714) Turn on openejb.strict.interface.declaration for OpenEJB
[ https://issues.apache.org/jira/browse/GERONIMO-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reopened GERONIMO-4714: WIth the latest OpenEJB 3.1.2-SNAPSHOT, most failure cases are resolved, I will remove this configuration later > Turn on openejb.strict.interface.declaration for OpenEJB > > > Key: GERONIMO-4714 > URL: https://issues.apache.org/jira/browse/GERONIMO-4714 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 >Reporter: Ivan >Assignee: Ivan > Fix For: 2.2 > > > In OpenEJB 3.1.*, a new option openejb.strict.interface.declaration is > imported. > I would like to set this option with true, by default its value is false. > Currently, there maybe some issues of this option with the default value. > Please refer to OpenEJB 1039, > https://issues.apache.org/jira/browse/OPENEJB-1039. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Branch notice for 2.2 (trunk)
I'm now working on GERONIMO-3003 and hopefully it can make G2.2, even though it is a small feature VS. defect. -Jack On Mon, Jul 20, 2009 at 2:06 PM, Shawn Jiang wrote: > Agreed. > > Besides, I would prefer the patch for > https://issues.apache.org/jira/browse/GERONIMO-4737 is applied before 2.2 > branch. There are too many code changes in the jira. > > > On Mon, Jul 20, 2009 at 10:09 AM, Jarek Gawor wrote: > >> Looks like the testsuites are mostly passing for Jetty but they are >> failing for Tomcat. I think it would be good to resolve those before >> branching. >> >> Jarek >> >> On Sat, Jul 18, 2009 at 4:13 AM, David Jencks >> wrote: >> > I'm thinking I will branch 2.2 off of trunk sunday or monday unless >> there >> > are convincing arguments against it. I think we need to stop adding >> > features :-) >> > >> > Trunk will become 3.0-SNAPSHOT. >> > >> > Also, I added a list of stuff we need to get released before 2.2 can be >> > released at the bottom of >> > >> > >> http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.2+Release+Roadmap >> > >> > many thanks >> > david jencks >> > >> > > > > -- > Shawn >
Re: ApacheCon '09 Geronimo Track Call for Papers
On 07/20/2009 09:18 AM, Vamsavardhana Reddy wrote: Just wondering what happens to the proposals submitted through conference web site. They can be used too if Geronimo decides to do so. Cheers Jean-Frederic
Re: Default Subject configuration for Jetty assembility
I'm also having this problem. Are you saying it will work if I configure JASPI authentication? Thanks Trygve On Mon, Jul 20, 2009 at 11:17 AM, Ivan wrote: > Hi, >While working with the current 2.2 Jetty assembility, I found that the > way we used to configure the default subject does not take effect again. >After checking the codes, it seems that, currently, jetty builder will > always check for the jaspi authentication configuration, if not found, the > runassource will be ignored. > I wonder whether it is by design or an issue. Thanks for any comment ! > > -- > Ivan >
[BUILD] branches/2.1: Failed for Revision: 795757
Geronimo Revision: 795757 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090720/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090720/unit-test-reports apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://repository.apache.org/snapshots/), codehaus-snapshots (http://snapshots.repository.codehaus.org), snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20-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.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-1-20070806 2) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20-SNAPSHOT -- 1 required artifact is missing. for artifact: org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-1-20070806 from the specified remote repositories: codehaus.org (http://repository.codehaus.org), ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://repository.apache.org/snapshots/), codehaus-snapshots (http://snapshots.repository.codehaus.org), snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:575) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) 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:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20-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.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-1-20070806 2) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20-SNAPSHOT -- 1 required artifact is missing. for artifact: org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-1-20070806 from the specified remote repositories: codehaus.org (http://repository.codehaus.org), ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://repository.apache.org/snapshots
Default Subject configuration for Jetty assembility
Hi, While working with the current 2.2 Jetty assembility, I found that the way we used to configure the default subject does not take effect again. After checking the codes, it seems that, currently, jetty builder will always check for the jaspi authentication configuration, if not found, the runassource will be ignored. I wonder whether it is by design or an issue. Thanks for any comment ! -- Ivan
[BUILD] trunk: Failed for Revision: 795698
Geronimo Revision: 795698 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 42 minutes 33 seconds [INFO] Finished at: Mon Jul 20 03:46:54 EDT 2009 [INFO] Final Memory: 431M/972M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090720/logs-0300-tomcat/ [INFO] Using geronimoHome: /home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT [INFO] Installing assembly... [INFO] Expanding: /home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip into /home/geronimo/geronimo/trunk/testsuite/target [INFO] Starting Geronimo server... [INFO] Selected option set: default [INFO] Redirecting output to: /home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log [INFO] Waiting for Geronimo server... [INFO] Geronimo server started in 0:00:46.763 [INFO] [shitty:install {execution: default}] [INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom [INFO] [shitty:test {execution: default}] [INFO] Starting 36 test builds [INFO] [INFO] --- [INFO] [INFO] commands-testsuite/deploy RUNNING [INFO] commands-testsuite/deploy SUCCESS (0:01:22.237) [INFO] commands-testsuite/gshell RUNNING [INFO] commands-testsuite/gshell SUCCESS (0:00:35.411) [INFO] commands-testsuite/jaxws RUNNING [INFO] commands-testsuite/jaxws SUCCESS (0:00:40.610) [INFO] commands-testsuite/shutdownRUNNING [INFO] commands-testsuite/shutdownSUCCESS (0:00:21.407) [INFO] concurrent-testsuite/concurrent-basic RUNNING [INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:46.922) [INFO] console-testsuite/advanced RUNNING [INFO] console-testsuite/advanced SUCCESS (0:01:43.886) [INFO] console-testsuite/basicRUNNING [INFO] console-testsuite/basicSUCCESS (0:02:04.635) [INFO] corba-testsuite/corba-helloworld RUNNING [INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:52.938) [INFO] corba-testsuite/corba-marshal RUNNING [INFO] corba-testsuite/corba-marshal SUCCESS (0:01:08.971) [INFO] corba-testsuite/corba-mytime RUNNING [INFO] corba-testsuite/corba-mytime SUCCESS (0:00:48.016) [INFO] deployment-testsuite/deployment-tests RUNNING [INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.558) [INFO] deployment-testsuite/jca-cms-tests RUNNING [INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:41.262) [INFO] deployment-testsuite/manifestcp-tests RUNNING [INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.340) [INFO] enterprise-testsuite/ejb-tests RUNNING [INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:27.840) [INFO] enterprise-testsuite/jms-tests RUNNING [INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.197) [INFO] enterprise-testsuite/jpa-tests RUNNING [INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:52.744) [INFO] enterprise-testsuite/sec-clientRUNNING [INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.836) [INFO] enterprise-testsuite/sec-tests RUNNING [INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.702) [INFO] security-testsuite/test-security RUNNING [INFO] security-testsuite/test-security FAILURE (0:00:46.256) Java returned: 1 [INFO] web-testsuite/test-2.1-jspsRUNNING [INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.217) [INFO] web-testsuite/test-2.5-servletsRUNNING [INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.760) [INFO] web-testsuite/test-myfaces RUNNING [INFO] web-testsuite/test-myfaces SUCCESS (0:00:34.799) [INFO] web-testsuite/test-tomcat RUNNING [INFO] web-testsuite/test-tomcat FAILURE (0:00:20.138) Java returned: 1 [INFO] web-testsuite/test-web-forward
[jira] Commented: (GERONIMO-3815) ContextManager.getCurrentContext() throws NullPointerException
[ https://issues.apache.org/jira/browse/GERONIMO-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733164#action_12733164 ] Mircea commented on GERONIMO-3815: -- Still an issue as of geronimo-jetty6-javaee5-2.1.4 on CentOS (I think it happens when trying to access the database layer in my app. but I'm not sure). Caused by: java.lang.NullPointerException at org.apache.geronimo.security.ContextManager.getCurrentContext(ContextManager.java:164) at org.apache.geronimo.openejb.GeronimoSecurityService.isCallerAuthorized(GeronimoSecurityService.java:101) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:142) at org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267) at org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy84.create(Unknown Source) > ContextManager.getCurrentContext() throws NullPointerException > -- > > Key: GERONIMO-3815 > URL: https://issues.apache.org/jira/browse/GERONIMO-3815 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.0.2, 2.0.3, 2.1, 2.1.4 >Reporter: Vamsavardhana Reddy >Assignee: David Jencks > Fix For: Wish List > > Attachments: GERONIMO-3815-2.debug.patch, > GERONIMO-3815-3.debug.patch, GERONIMO-3815.debug.patch > > > ContextManager.getCurrentContext() is throwing a NullPointerException. This > is observed only when there is heavy load on the application. Most likely it > is a threading issue where one thread is unregistering the subject while > another is executing getCurrentContext(). Excerpt from stacktrace given > below. > > Caused by: java.lang.NullPointerException > at > org.apache.geronimo.security.ContextManager.getCurrentContext(ContextManager.java:197) > at > org.apache.geronimo.openejb.GeronimoSecurityService.isCallerAuthorized(GeronimoSecurityService.java:101) > at > org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:142) > at > org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267) > at > org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158) > at > org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) > at > org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) > at $Proxy16.create(Unknown Source) > ... 53 more > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4755) Warning message when starting the server due to Tomcat class not found
[ https://issues.apache.org/jira/browse/GERONIMO-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733162#action_12733162 ] viola.lu commented on GERONIMO-4755: Duplicate with https://issues.apache.org/jira/browse/GERONIMO-4713, thanks. > Warning message when starting the server due to Tomcat class not found > -- > > Key: GERONIMO-4755 > URL: https://issues.apache.org/jira/browse/GERONIMO-4755 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 >Reporter: Jack Cai >Priority: Minor > > When starting the 2.2 server (tomcat assembly), the below warning message > will always appear during the starting of the juddi server. > WARN [NamingContextListener] Failed to register in JMX: > javax.naming.NamingException: Could not create resource factory instance > [Root exception is java.lang.ClassNotFoundException: > org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory] > Initial investigation shows that Tomcat uses the class > "org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory" as the default > datasource factory class, see org.apache.naming.factory.ResourceFactory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4628) Console plan wizards need to save plans
[ https://issues.apache.org/jira/browse/GERONIMO-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-4628: --- Attachment: Geronimo-4628-b21-new.patch Geronimo-4628-b21-new.patch is the new one for branch 2.1 based on trunk rev790327 & 790633. -Rex > Console plan wizards need to save plans > --- > > Key: GERONIMO-4628 > URL: https://issues.apache.org/jira/browse/GERONIMO-4628 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.1.5, 2.2 > > Attachments: Geronimo-4628-b21-new.patch, > GERONIMO-4628-b21-updated.patch, GERONIMO-4628-b21.patch > > > Currently we have a lot of console wizards that are great at creating basic > plans for datasources, security realms, etc etc. However once you've > deployed the plan through the wizard the plan is gone gone gone never to be > seen again. > The wizards need to do _something_ so the plans are saved on disk somehow. > One possibliity is that deployment could always save the plan into the car > file, like the car-maven-plugin does. I'm not certain but I think this would > fix the admin console wizard problem as well. > Also it would be very handy if the wizard inserted a comment mentioning the > intended target artifact, such as which tranql adapter to use for a > datasource plan. > Furthermore you ought to be able to specify all components of the artifact id > (groupId, etc) in all the wizards. In fact you should be able to set the > default groupId for the whole admin console -- probably your company wants > all the groupIds the same. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ApacheCon '09 Geronimo Track Call for Papers
On Jul 16, 2009, at 8:04 PM, Kevan Miller wrote: This years ApacheCon US Conference (Oakland, CA, USA - Nov 2 to 6 2009) will include a 1/2 day Geronimo Track. This is a call for session proposals. Please have submissions in by Monday 12 Noon EDT. We need to finalize the session contents early next week. Apache Geronimo is a lightweight, flexible, component-based server for building dynamic application server environments. Geronimo plugins can be assembled into a fully compliant Java EE Server. However, it can be easily assembled into a server providing a subset of functionality or a minimal subset required to meet the requirements of a set of applications. In addition to the Apache Geronimo Server, the Geronimo project is also comprised of a number of subprojects: Development Tools, XBean, Yoko, GShell, JavaMail, Connector/Transaction, etc. Potential topics for the Geronimo Track include, but are in no way limited to: * Geronimo architecture, * Systems management, * Custom server assemblies, * Application development and user experiences, * OSGi Blueprint, * Kernel restructuring, * Java EE 6, * etc. Please submit Talk proposals on this mail thread. Each suggestion should include: * Title Geronimo Custom Server Assemblies * Speaker name(s) David Jencks * Abstract (Short overview of the talk contents) Geronimo makes it easy to assemble a custom server around your applications, including only those features needed to run your apps. We'll see how to use maven to integrate this into your build process. We'll discuss how this works in recent geronimo releases such as 2.2 and how it will work in the osgi environment in geronimo 3.0. Bio: See apachecon eu 2009 thanks david jencks Thanks! Look forward to seeing you at ApacheCon! --kevan
Re: ApacheCon '09 Geronimo Track Call for Papers
On 07/17/2009 05:04 AM, Kevan Miller wrote: This years ApacheCon US Conference (Oakland, CA, USA - Nov 2 to 6 2009) will include a 1/2 day Geronimo Track. This is a call for session proposals. Please have submissions in by Monday 12 Noon EDT. We need to finalize the session contents early next week. Apache Geronimo is a lightweight, flexible, component-based server for building dynamic application server environments. Geronimo plugins can be assembled into a fully compliant Java EE Server. However, it can be easily assembled into a server providing a subset of functionality or a minimal subset required to meet the requirements of a set of applications. In addition to the Apache Geronimo Server, the Geronimo project is also comprised of a number of subprojects: Development Tools, XBean, Yoko, GShell, JavaMail, Connector/Transaction, etc. Potential topics for the Geronimo Track include, but are in no way limited to: * Geronimo architecture, * Systems management, * Custom server assemblies, * Application development and user experiences, * OSGi Blueprint, * Kernel restructuring, * Java EE 6, * etc. Please submit Talk proposals on this mail thread. Each suggestion should include: * Title * Speaker name(s) A short bio of the speaker too. * Abstract (Short overview of the talk contents) Thanks! Look forward to seeing you at ApacheCon! Please hurry a little: It would be nice to have all the tracks defined on Tuesday 21th of July. Cheers Jean-Frederic
Re: ApacheCon '09 Geronimo Track Call for Papers
Just wondering what happens to the proposals submitted through conference web site. On Fri, Jul 17, 2009 at 8:34 AM, Kevan Miller wrote: > This years ApacheCon US Conference (Oakland, CA, USA - Nov 2 to 6 2009) > will include a 1/2 day Geronimo Track. This is a call for session proposals. > Please have submissions in by Monday 12 Noon EDT. We need to finalize the > session contents early next week. > > Apache Geronimo is a lightweight, flexible, component-based server for > building dynamic application server environments. Geronimo plugins can be > assembled into a fully compliant Java EE Server. However, it can be easily > assembled into a server providing a subset of functionality or a minimal > subset required to meet the requirements of a set of applications. In > addition to the Apache Geronimo Server, the Geronimo project is also > comprised of a number of subprojects: Development Tools, XBean, Yoko, > GShell, JavaMail, Connector/Transaction, etc. > > Potential topics for the Geronimo Track include, but are in no way limited > to: > * Geronimo architecture, > * Systems management, > * Custom server assemblies, > * Application development and user experiences, > * OSGi Blueprint, > * Kernel restructuring, > * Java EE 6, > * etc. > > Please submit Talk proposals on this mail thread. Each suggestion should > include: > > * Title > * Speaker name(s) > * Abstract (Short overview of the talk contents) > > Thanks! Look forward to seeing you at ApacheCon! > > --kevan > -- Vamsi
[jira] Created: (GERONIMO-4755) Warning message when starting the server due to Tomcat class not found
Warning message when starting the server due to Tomcat class not found -- Key: GERONIMO-4755 URL: https://issues.apache.org/jira/browse/GERONIMO-4755 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Affects Versions: 2.2 Reporter: Jack Cai Priority: Minor When starting the 2.2 server (tomcat assembly), the below warning message will always appear during the starting of the juddi server. WARN [NamingContextListener] Failed to register in JMX: javax.naming.NamingException: Could not create resource factory instance [Root exception is java.lang.ClassNotFoundException: org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory] Initial investigation shows that Tomcat uses the class "org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory" as the default datasource factory class, see org.apache.naming.factory.ResourceFactory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ApacheCon '09 Geronimo Track Call for Papers
On 07/17/2009 10:17 PM, Jarek Gawor wrote: Here's a talk proposal about Blueprint Container Specification. However, it might fit better within some more general talk about Geronimo and OSGi (if there is going to be one like that). Title: Blueprint Container Specification and Geronimo Speaker name(s): Jarek Gawor Abstract: This talk will provide a general overview of the Blueprint Container Specification and demonstrate some of its core features using Geronimo's Blueprint Container implementation. The talk will also describe some more advanced features of the Geronimo implementation such as Configuration Admin Service support and custom namespace handlers. Future plans will be discussed as well as how the Blueprint Container might be used and integrated within the existing Geronimo Kernel. We also need a short bio of the speaker :-) Cheers Jean-Frederic