date:20090721

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
execution
idinstall-plugin/id
phaseinstall/phase
goals
goalinstall-plugin/goal
/goals
!--configuration--

!--defaultGeronimoRepositoryhttp://geronimo.apache.org/plugins/geronimo-${version}//defaultGeronimoRepository--
!--/configuration--
/execution

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.init(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] 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
 execution
 idinstall-plugin/id
 phaseinstall/phase
 goals
 goalinstall-plugin/goal
 /goals
 !--configuration--
 
 !--defaultGeronimoRepositoryhttp://geronimo.apache.org/plugins/geronimo-${version}//defaultGeronimoRepository--
 !--/configuration--
 /execution
 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.init(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: Default Subject configuration for Jetty assembility

Seem, it still does not work.
I did not find those codes like ContextManager.setCaller() in the
SecurityHandler, so, did not think that the defaultSubject in attached to
the current thread.

2009/7/21 David Jencks david_jen...@yahoo.com

 Well, its a bug :- 
 )https://issues.apache.org/jira/browse/GERONIMO-475https://issues.apache.org/jira/browse/GERONIMO-4756
 6
 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 xhh...@gmail.com 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






-- 
Ivan

[BUILD] trunk: Failed for Revision: 796154

Geronimo Revision: 796154 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/build-0300.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 43 minutes 21 seconds
[INFO] Finished at: Tue Jul 21 03:47:46 EDT 2009
[INFO] Final Memory: 429M/963M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/logs-0300-tomcat/
 
 
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:21.346) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:35.072) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:39.591) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.067) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  FAILURE (0:01:10.733) Java 
returned: 1
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.061) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:02.364) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   FAILURE (0:00:35.955) Java 
returned: 1
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  FAILURE (0:00:33.605) Java 
returned: 1
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   FAILURE (0:00:38.673) Java 
returned: 1
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:36.364) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.405) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:37.332) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests FAILURE (0:01:46.935) Java 
returned: 1
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:46.552) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests FAILURE (0:00:47.611) Java 
returned: 1
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:35.380) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:39.347) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:52.103) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:36.412) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.398) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:34.022) 
[INFO] web-testsuite/test-tomcat  RUNNING
[INFO] web-testsuite/test-tomcat  SUCCESS (0:00:25.191) 
[INFO] web-testsuite/test-web-forward RUNNING
[INFO] web-testsuite/test-web-forward FAILURE (0:00:33.708) Java 
returned: 1
[INFO] web-testsuite/test-web-references  RUNNING
[INFO] web-testsuite/test-web-references  FAILURE (0:00:39.319) Java 
returned: 1
[INFO] webservices-testsuite/jaxb-tests   RUNNING
[INFO] webservices-testsuite/jaxb-tests   SUCCESS (0:01:08.030) 
[INFO] webservices-testsuite/jaxr-tests   RUNNING
[INFO] webservices-testsuite/jaxr-tests   SUCCESS (0:00:59.935) 
[INFO] webservices-testsuite/jaxrpc-jaxws-tests   RUNNING
[INFO] webservices-testsuite/jaxrpc-jaxws-tests   SUCCESS (0:00:38.765) 
[INFO] webservices-testsuite/jaxrpc-tests RUNNING
[INFO] webservices-testsuite/jaxrpc-tests SUCCESS (0:00:49.122) 
[INFO] webservices-testsuite/jaxws-catalog-tests  RUNNING
[INFO] webservices-testsuite

[jira] Commented: (GERONIMO-4725) MySQL jdbc connector/driver jars don't show up in the database pool wizard

2009-07-21 Thread JIRA


[ 
https://issues.apache.org/jira/browse/GERONIMO-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12733536#action_12733536
 ] 

Jürgen Weber commented on GERONIMO-4725:


OK, made a fresh install of geronimo-tomcat6-javaee5-2.2-SNAPSHOT 
2009.07.16-15:10:04.515-0400

Installed mysql-connector-java-3.1.14.jar as
groupIdcom.mysql/groupId
artifactIdmysql-connector-java/artifactId
version3.1.14/version
typejar/type


tried to add Database Type MySQL. On the next screen there is again the empty 
driver list shown in the screen shot.

I think this should be fixed and should work without having to rename driver 
jars.

 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-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

 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
 execution
 idinstall-plugin/id
 phaseinstall/phase
 goals
 goalinstall-plugin/goal
 /goals
 !--configuration--
 
 !--defaultGeronimoRepositoryhttp://geronimo.apache.org/plugins/geronimo-${version}//defaultGeronimoRepository--
 !--/configuration--
 /execution
 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.init(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] 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: (was: GERONIMO-4757.patch)

 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
 execution
 idinstall-plugin/id
 phaseinstall/phase
 goals
 goalinstall-plugin/goal
 /goals
 !--configuration--
 
 !--defaultGeronimoRepositoryhttp://geronimo.apache.org/plugins/geronimo-${version}//defaultGeronimoRepository--
 !--/configuration--
 /execution
 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.init(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] Commented: (GERONIMO-4284) Server farm management based on plugins


[ 
https://issues.apache.org/jira/browse/GERONIMO-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12733539#action_12733539
 ] 

viola.lu commented on GERONIMO-4284:


Hi,david, this function is complete? After verfication, i found out that, 
Plugin-farm-it(Intergration Test) plugin which usesTestGbean  will run a test 
add plugin to cluster, but the sample plugin to be installed  
org.apache.geronimo.samples/customer-service-jetty/2.2-SNAPSHOT/car doesn't 
exist , so this will result in error, this intergration test plugin will be 
removed?And i can't find farm command in server trunck, thanks.


 Server farm management based on plugins
 ---

 Key: GERONIMO-4284
 URL: https://issues.apache.org/jira/browse/GERONIMO-4284
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: Clustering
Affects Versions: 2.2
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.2


 Our current farm support is based on (IIUC) fairly hard coded farm members 
 and deployment of applications with automatic distribution to farm members.  
 We could also use farm management based on installing plugins with more 
 dynamic farm membership and explicit distribution commands.  For something 
 like this database persistence seems more appropriate than using gbeans and 
 repositories.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-4758) The Server Console page displays messy codes

2009-07-21 Thread Siqi Du (JIRA)

The Server Console page displays messy codes


 Key: GERONIMO-4758
 URL: https://issues.apache.org/jira/browse/GERONIMO-4758
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1.4, 2.2
 Environment: Windows XP + IE6
Reporter: Siqi Du


Set zh_cn the 1st place in the language preference list ( from Internet Options 
of Control Panel)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: branches/2.1 update

2009-07-21 Thread Shawn Jiang

Adding a apache-snapshot as plugin repository could resolve this problem.

pluginRepositories
pluginRepository
idapache-snapshots/id
nameApache Snapshots Repository/name
urlhttp://repository.apache.org/snapshots/url
layoutdefault/layout
snapshots
enabledtrue/enabled
updatePolicydaily/updatePolicy
checksumPolicyignore/checksumPolicy
/snapshots
releases
enabledfalse/enabled
/releases
/pluginRepository
/pluginRepositories

I think It should be a defect of MAVEN. But anyway, we should add the plugin
repository to workaround this problem for now.

On Fri, Jul 17, 2009 at 11:08 PM, Kevan Miller kevan.mil...@gmail.comwrote:


 On Jul 17, 2009, at 9:23 AM, Donald Woods wrote:

  I ran into build problems like the automated 2.1 build, as I didn't build
 the new Tomcat artifacts locally and the snapshot resolution seems to be
 broken due to using unique timestamps for the deployed artifacts


 K. Sigh. I'll have a look, but not likely to be until this afternoon... If
 anybody wants to have a look, feel free. Until then, building
 geronimo/external/trunk/tomcat-parent-6.0.20/ should avoid the problem...

 --kevan




-- 
Shawn

[BUILD] branches/2.1: Failed for Revision: 796247

Geronimo Revision: 796247 built with tests included
 
See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090721/build-0800.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090721/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: Default Subject configuration for Jetty assembility

2009-07-21 Thread Trygve Hardersen

I'll start working on getting our app to run with Geronimo 2.2  Jetty7
today. We're currently using Jetty6 because of security configuration
problems.

Will let you know what I find.

Thanks

Trygve

On Tue, Jul 21, 2009 at 9:55 AM, Ivan xhh...@gmail.com wrote:

 Seem, it still does not work.
 I did not find those codes like ContextManager.setCaller() in the
 SecurityHandler, so, did not think that the defaultSubject in attached to
 the current thread.

 2009/7/21 David Jencks david_jen...@yahoo.com

 Well, its a bug :- 
 )https://issues.apache.org/jira/browse/GERONIMO-475https://issues.apache.org/jira/browse/GERONIMO-4756
 6
 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 xhh...@gmail.com 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






 --
 Ivan

Re: [Discuss] ApacheCon '09 Geronimo Track: Content

2009-07-21 Thread Joe Bohn



I definitely agree that we need some theme for the afternoon and talking 
about the future (especially for Geronimo where things will be changing 
a fair amount) is always a good choice.


I'm not sure if there was an implied order below ... but I would 
recommend the following:
1) Custom Server Assemblies (with a strong emphasis on current Geronimo 
architecture and the move to OSGi  IMHO this sets the stage well for 
Blueprint).

2) Blueprint Container Specification and Geronimo
3) JPA 2.0 Specification (I agree it would be best to include general 
EE6 outlook).


Great suggestions everybody ... wish I could attend ApacheCon!

Joe

Kevan Miller wrote:
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

Re: [Discuss] ApacheCon '09 Geronimo Track: Content

2009-07-21 Thread Donald Woods


Maybe we can create a mashup of the proposals to cover the following:

Session 1 - Geronimo 2.2 topics (current user community)
Administering Geronimo
Custom Server Assemblies
Securing Apps
Load balancing and high-availability
Would expect this session would contain more than we could cover in 50 
minutes, but we should introduce each topic and include pointers to the 
online docs that users could reference later for more details.


Session 2 - Blueprint Container Spec and Geronimo

Session 3 - Geronimo 3.0 and Java EE 6 (futures)
Geronimo 3.0 based on OSGi
Current milestone features
Present how much of Web Profile is available
JPA 2.0, EJB 3.1, Servlet 3.0, ...
How to start using 3.0 builds


-Donald


Kevan Miller wrote:
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

Re: branches/2.1 update

2009-07-21 Thread Kevan Miller



On Jul 21, 2009, at 5:56 AM, Shawn Jiang wrote:

Adding a apache-snapshot as plugin repository could resolve this  
problem.


pluginRepositories
pluginRepository
idapache-snapshots/id
nameApache Snapshots Repository/name
urlhttp://repository.apache.org/snapshots/url
layoutdefault/layout
snapshots
enabledtrue/enabled
updatePolicydaily/updatePolicy
checksumPolicyignore/checksumPolicy
/snapshots
releases
enabledfalse/enabled
/releases
/pluginRepository
/pluginRepositories


Thanks for the pointer, Shawn. Works for me.

--kevan

[BUILD] trunk: Failed for Revision: 796268

Geronimo Revision: 796268 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 43 minutes 6 seconds
[INFO] Finished at: Tue Jul 21 09:47:56 EDT 2009
[INFO] Final Memory: 400M/1014M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/logs-0900-tomcat/
 
 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:18.110) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:35.438) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:40.040) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.145) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  FAILURE (0:01:02.257) Java 
returned: 1
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:34.237) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:03.987) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   FAILURE (0:00:37.538) Java 
returned: 1
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  FAILURE (0:00:31.478) Java 
returned: 1
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   FAILURE (0:00:38.511) Java 
returned: 1
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:35.017) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.879) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:36.766) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests FAILURE (0:01:06.704) Java 
returned: 1
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:00:45.748) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests FAILURE (0:00:44.101) Java 
returned: 1
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.810) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:35.854) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:46.252) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:35.117) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:30.992) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:32.811) 
[INFO] web-testsuite/test-tomcat  RUNNING
[INFO] web-testsuite/test-tomcat  SUCCESS (0:00:24.121) 
[INFO] web-testsuite/test-web-forward RUNNING
[INFO] web-testsuite/test-web-forward FAILURE (0:00:33.124) Java 
returned: 1
[INFO] web-testsuite/test-web-references  RUNNING
[INFO] web-testsuite/test-web-references  FAILURE (0:00:37.549) Java 
returned: 1
[INFO] webservices-testsuite/jaxb-tests   RUNNING
[INFO] webservices-testsuite/jaxb-tests   SUCCESS (0:01:07.333) 
[INFO] webservices-testsuite/jaxr-tests   RUNNING
[INFO] webservices-testsuite/jaxr-tests   SUCCESS (0:00:57.782) 
[INFO] webservices-testsuite/jaxrpc-jaxws-tests   RUNNING
[INFO] webservices-testsuite/jaxrpc-jaxws-tests   SUCCESS (0:00:39.106) 
[INFO] webservices-testsuite/jaxrpc-tests RUNNING
[INFO] webservices-testsuite/jaxrpc-tests SUCCESS (0:00:50.092) 
[INFO] webservices-testsuite/jaxws-catalog-tests  RUNNING
[INFO] webservices

Re: Encrypt password in deployment plans and config.ser

2009-07-21 Thread Jack Cai

I've completed most of the coding for this small feature. Now I need to
figure out a way to get the encrypted meta-information from GAttributeInfo
in the GBeanOverride class so that it will encrypt attributes according to
the meta-information when saved to config.xml. This turns out to be a
non-trivial work, as GBeanOverride does not maintain any direct/indirect
reference to GAttributeInfo! It does contain a gbeanInfo field, but its
type is String and I cannot understand how its value could be used in any
way.

One possible solution is to duplicate the encrypted“ meta-information in
the config.xml, in a similar way as what we are doing with null
attributes. But apparently this is not the ideal way. Does anybody have a
better idea? Thanks a lot!

-Jack

On Wed, May 13, 2009 at 4:04 PM, Jack Cai greensi...@gmail.com wrote:

Thanks Jarek for your comments! I should have provided more description
about the fix -

1. setAttribute() is usually called by the unmarshaller, so it should
actually do the decryption. Since the decryption will automatically bypass
unecrypted values, it won't do any harm if the passed-in attribute value is
not encrypted.

2. getAttribute() is usually called by various consumers that wants to read
the real value (decrypted), so it just returns what is stored in the
GBeanData (already decrypted value).

3. The current patch does do encryption for writeExternal(). The reason
decryption is not done for readExternal() directly is because readExternal()
calls setAttribute() which does the decryption.

I agree that it's not optimal to hard-code to encrypt password
attributes, and better to use the GAttributeInfo to make this configurable.
My suggestion is to set encryption on for all attributes whose name contains
password and off for the rest. We can thus eliminate the hard-code logic
in GBeanOverride too (for encrption in config.xml).

I'm going to create a patch if no objection.

-Jack

2009/5/13 Jarek Gawor jga...@gmail.com

Jack,

I was thinking about this a while ago and had a slightly different
approach. I was thinking of adding a 'protected' or 'encrypted'
attribute to the GAttributeInfo (for example, just like the
'persistent' attribute) to indicate that this attribute should be
encrypted in the serialized file. I wanted to allow for any
attribute to be encrypted even if it doesn't have the password name
in it. And I think with this way we could also expose that setting via
our GBean annotations.

Btw, hmm... shouldn't encrypt be called in setAttribute() and decrypt
in getAttribute() or at least encrypt in writeExternal() and decrypt
in readExternal() ?

Jarek

On Tue, May 12, 2009 at 4:06 AM, Jack Cai greensi...@gmail.com wrote:
Recently someone pointed out to us that password specified in the
deployment
plan is stored in clear text in the config.ser after deployment, for
example, when deploying a datasource with the database password
specified in
the deployment plan. I notice that there was another user mentioning
exactly
the same problem in the geronimo-user list two years ago [1].

I did a little more dig and also found this JIRA [2] along with this
discussion [3] on encrypting passwords in deployment plans.

I understand that there are different arguments on what is real
security.
But I also well appreciate users' concerns on having clear text password
appearing in the system. In China, we have a saying guard against the
good
guys but not the bad guys, meaning the guard is there just to prevent
the
good guys from doing bad. Taking the same example as in the old thread
[3],
if we lock a bicycle, then the good guys won't steal it, while the bad
guys
with the intention to steal it can still find ways to steal it. But if
we
leave the bicycle unlocked, then the good guys are tempted to steal the
bicycle too, because it's so easy.

Back to JIRA [2], I think an alternative is to let user input the
password
in encrypted form in the deployment plan at the very beginning. We can
provide a small command line tool to let user ecrypt the password
beforehands. If this is acceptable, then there is a very simple way to
satisfy requirement [1] [2]. We can simply add a little encryption
logic
in the class org.apache.geronimo.gbean.GBeanData [4], similar to what we
did
in GBeanOverride for config.xml.

Comments are welcome.

-Jack

[1]
http://www.nabble.com/plaintext-password-in-config.ser-to9834211.html
[2] http://issues.apache.org/jira/browse/GERONIMO-3003
[3]

http://www.nabble.com/Plaintext-passwords-in-Geronimo-plans-and-config-files-td9100565s134.html
[4]
Index:

D:/Dev/s/wasce_v2.1.0.1/server/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/gbean/GBeanData.java
===
---

Re: Encrypt password in deployment plans and config.ser

gbeanInfo is used to delare the class name of the gbean, it is used to add
new gbean in the config.xml.
eg. gbean name=... gbeanInfo=org.apache.myGBean

2009/7/21 Jack Cai greensi...@gmail.com

 I've completed most of the coding for this small feature. Now I need to
 figure out a way to get the encrypted meta-information from GAttributeInfo
 in the GBeanOverride class so that it will encrypt attributes according to
 the meta-information when saved to config.xml. This turns out to be a
 non-trivial work, as GBeanOverride does not maintain any direct/indirect
 reference to GAttributeInfo! It does contain a gbeanInfo field, but its
 type is String and I cannot understand how its value could be used in any
 way.

 One possible solution is to duplicate the encrypted“ meta-information in
 the config.xml, in a similar way as what we are doing with null
 attributes. But apparently this is not the ideal way. Does anybody have a
 better idea? Thanks a lot!

 -Jack



 On Wed, May 13, 2009 at 4:04 PM, Jack Cai greensi...@gmail.com wrote:

 Thanks Jarek for your comments! I should have provided more description
 about the fix -

 1. setAttribute() is usually called by the unmarshaller, so it should
 actually do the decryption. Since the decryption will automatically bypass
 unecrypted values, it won't do any harm if the passed-in attribute value is
 not encrypted.

 2. getAttribute() is usually called by various consumers that wants to
 read the real value (decrypted), so it just returns what is stored in the
 GBeanData (already decrypted value).

 3. The current patch does do encryption for writeExternal(). The reason
 decryption is not done for readExternal() directly is because readExternal()
 calls setAttribute() which does the decryption.

 I agree that it's not optimal to hard-code to encrypt password
 attributes, and better to use the GAttributeInfo to make this configurable.
 My suggestion is to set encryption on for all attributes whose name contains
 password and off for the rest. We can thus eliminate the hard-code logic
 in GBeanOverride too (for encrption in config.xml).

 I'm going to create a patch if no objection.

 -Jack

 2009/5/13 Jarek Gawor jga...@gmail.com

 Jack,

 I was thinking about this a while ago and had a slightly different
 approach. I was thinking of adding a 'protected' or 'encrypted'
 attribute to the GAttributeInfo (for example, just like the
 'persistent' attribute) to indicate that this attribute should be
 encrypted in the serialized file. I wanted to allow for any
 attribute to be encrypted even if it doesn't have the password name
 in it. And I think with this way we could also expose that setting via
 our GBean annotations.

 Btw, hmm... shouldn't encrypt be called in setAttribute() and decrypt
 in getAttribute() or at least encrypt in writeExternal() and decrypt
 in readExternal() ?

 Jarek

 On Tue, May 12, 2009 at 4:06 AM, Jack Cai greensi...@gmail.com wrote:
  Recently someone pointed out to us that password specified in the
 deployment
  plan is stored in clear text in the config.ser after deployment, for
  example, when deploying a datasource with the database password
 specified in
  the deployment plan. I notice that there was another user mentioning
 exactly
  the same problem in the geronimo-user list two years ago [1].
 
  I did a little more dig and also found this JIRA [2] along with this
  discussion [3] on encrypting passwords in deployment plans.
 
  I understand that there are different arguments on what is real
 security.
  But I also well appreciate users' concerns on having clear text
 password
  appearing in the system. In China, we have a saying guard against the
 good
  guys but not the bad guys, meaning the guard is there just to prevent
 the
  good guys from doing bad. Taking the same example as in the old thread
 [3],
  if we lock a bicycle, then the good guys won't steal it, while the bad
 guys
  with the intention to steal it can still find ways to steal it. But if
 we
  leave the bicycle unlocked, then the good guys are tempted to steal the
  bicycle too, because it's so easy.
 
  Back to JIRA [2], I think an alternative is to let user input the
 password
  in encrypted form in the deployment plan at the very beginning. We can
  provide a small command line tool to let user ecrypt the password
  beforehands. If this is acceptable, then there is a very simple way to
  satisfy requirement [1]  [2]. We can simply add a little encryption
 logic
  in the class org.apache.geronimo.gbean.GBeanData [4], similar to what
 we did
  in GBeanOverride for config.xml.
 
  Comments are welcome.
 
  -Jack
 
 
  [1]
 http://www.nabble.com/plaintext-password-in-config.ser-to9834211.html
  [2] http://issues.apache.org/jira/browse/GERONIMO-3003
  [3]
 
 http://www.nabble.com/Plaintext-passwords-in-Geronimo-plans-and-config-files-td9100565s134.html
  [4]
  Index:

Re: [BUILD] trunk: Failed for Revision: 796268

Seems that those placeholders in the pom.xml are not replaced, like
${project.build.directory}/${artifactId}-${version}.ear.

2009/7/21 ga...@apache.org

 Geronimo Revision: 796268 built with tests included

 See the full build-0900.log file at
 http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/build-0900.log

 Download the binaries from
 http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721
 [INFO] BUILD SUCCESSFUL
 [INFO]
 
 [INFO] Total time: 43 minutes 6 seconds
 [INFO] Finished at: Tue Jul 21 09:47:56 EDT 2009
 [INFO] Final Memory: 400M/1014M
 [INFO]
 

 TESTSUITE RESULTS (Failures only)
 =

 Assembly: tomcat
 =
 See full test results and logs at
 http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/logs-0900-tomcat/


 [INFO]
 ---
 [INFO]
 [INFO] commands-testsuite/deploy  RUNNING
 [INFO] commands-testsuite/deploy  SUCCESS (0:01:18.110)
 [INFO] commands-testsuite/gshell  RUNNING
 [INFO] commands-testsuite/gshell  SUCCESS (0:00:35.438)
 [INFO] commands-testsuite/jaxws   RUNNING
 [INFO] commands-testsuite/jaxws   SUCCESS (0:00:40.040)
 [INFO] commands-testsuite/shutdownRUNNING
 [INFO] commands-testsuite/shutdownSUCCESS (0:00:21.145)
 [INFO] concurrent-testsuite/concurrent-basic  RUNNING
 [INFO] concurrent-testsuite/concurrent-basic  FAILURE (0:01:02.257)
 Java returned: 1
 [INFO] console-testsuite/advanced RUNNING
 [INFO] console-testsuite/advanced SUCCESS (0:01:34.237)
 [INFO] console-testsuite/basicRUNNING
 [INFO] console-testsuite/basicSUCCESS (0:02:03.987)
 [INFO] corba-testsuite/corba-helloworld   RUNNING
 [INFO] corba-testsuite/corba-helloworld   FAILURE (0:00:37.538)
 Java returned: 1
 [INFO] corba-testsuite/corba-marshal  RUNNING
 [INFO] corba-testsuite/corba-marshal  FAILURE (0:00:31.478)
 Java returned: 1
 [INFO] corba-testsuite/corba-mytime   RUNNING
 [INFO] corba-testsuite/corba-mytime   FAILURE (0:00:38.511)
 Java returned: 1
 [INFO] deployment-testsuite/deployment-tests  RUNNING
 [INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:35.017)
 [INFO] deployment-testsuite/jca-cms-tests RUNNING
 [INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.879)
 [INFO] deployment-testsuite/manifestcp-tests  RUNNING
 [INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:36.766)
 [INFO] enterprise-testsuite/ejb-tests RUNNING
 [INFO] enterprise-testsuite/ejb-tests FAILURE (0:01:06.704)
 Java returned: 1
 [INFO] enterprise-testsuite/jms-tests RUNNING
 [INFO] enterprise-testsuite/jms-tests FAILURE (0:00:45.748)
 Java returned: 1
 [INFO] enterprise-testsuite/jpa-tests RUNNING
 [INFO] enterprise-testsuite/jpa-tests FAILURE (0:00:44.101)
 Java returned: 1
 [INFO] enterprise-testsuite/sec-clientRUNNING
 [INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.810)
 [INFO] enterprise-testsuite/sec-tests RUNNING
 [INFO] enterprise-testsuite/sec-tests FAILURE (0:00:35.854)
 Java returned: 1
 [INFO] security-testsuite/test-security   RUNNING
 [INFO] security-testsuite/test-security   FAILURE (0:00:46.252)
 Java returned: 1
 [INFO] web-testsuite/test-2.1-jspsRUNNING
 [INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:35.117)
 [INFO] web-testsuite/test-2.5-servletsRUNNING
 [INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:30.992)
 [INFO] web-testsuite/test-myfaces RUNNING
 [INFO] web-testsuite/test-myfaces SUCCESS (0:00:32.811)
 [INFO] web-testsuite/test-tomcat  RUNNING
 [INFO] web-testsuite/test-tomcat  SUCCESS (0:00:24.121)
 [INFO] web-testsuite/test-web-forward RUNNING
 [INFO] web-testsuite/test-web-forward FAILURE (0:00:33.124)
 Java returned: 1
 [INFO] web-testsuite/test-web-references  RUNNING
 [INFO] web-testsuite/test-web-references  FAILURE (0:00:37.549)
 Java returned: 1
 [INFO] webservices-testsuite/jaxb-tests   RUNNING
 [INFO] webservices-testsuite/jaxb-tests   SUCCESS (0:01:07.333)
 [INFO] webservices-testsuite/jaxr-tests   RUNNING
 [INFO] webservices-testsuite/jaxr-tests   SUCCESS (0:00:57.782)
 [INFO] webservices-testsuite/jaxrpc-jaxws-tests   RUNNING
 [INFO] webservices-testsuite/jaxrpc-jaxws-tests   SUCCESS (0:00:39.106)
 [INFO

Re: [BUILD] trunk: Failed for Revision: 796268

No the pom.xml file, the reason is that those deployment plan files contains
the placeholders, I guess that we need to move them to the
filtered-resources folder ?

2009/7/21 Ivan xhh...@gmail.com

 Seems that those placeholders in the pom.xml are not replaced, like
 ${project.build.directory}/${artifactId}-${version}.ear.

 2009/7/21 ga...@apache.org

 Geronimo Revision: 796268 built with tests included

 See the full build-0900.log file at
 http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/build-0900.log

 Download the binaries from
 http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721
 [INFO] BUILD SUCCESSFUL
 [INFO]
 
 [INFO] Total time: 43 minutes 6 seconds
 [INFO] Finished at: Tue Jul 21 09:47:56 EDT 2009
 [INFO] Final Memory: 400M/1014M
 [INFO]
 

 TESTSUITE RESULTS (Failures only)
 =

 Assembly: tomcat
 =
 See full test results and logs at
 http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/logs-0900-tomcat/


 [INFO]
 ---
 [INFO]
 [INFO] commands-testsuite/deploy  RUNNING
 [INFO] commands-testsuite/deploy  SUCCESS (0:01:18.110)
 [INFO] commands-testsuite/gshell  RUNNING
 [INFO] commands-testsuite/gshell  SUCCESS (0:00:35.438)
 [INFO] commands-testsuite/jaxws   RUNNING
 [INFO] commands-testsuite/jaxws   SUCCESS (0:00:40.040)
 [INFO] commands-testsuite/shutdownRUNNING
 [INFO] commands-testsuite/shutdownSUCCESS (0:00:21.145)
 [INFO] concurrent-testsuite/concurrent-basic  RUNNING
 [INFO] concurrent-testsuite/concurrent-basic  FAILURE (0:01:02.257)
 Java returned: 1
 [INFO] console-testsuite/advanced RUNNING
 [INFO] console-testsuite/advanced SUCCESS (0:01:34.237)
 [INFO] console-testsuite/basicRUNNING
 [INFO] console-testsuite/basicSUCCESS (0:02:03.987)
 [INFO] corba-testsuite/corba-helloworld   RUNNING
 [INFO] corba-testsuite/corba-helloworld   FAILURE (0:00:37.538)
 Java returned: 1
 [INFO] corba-testsuite/corba-marshal  RUNNING
 [INFO] corba-testsuite/corba-marshal  FAILURE (0:00:31.478)
 Java returned: 1
 [INFO] corba-testsuite/corba-mytime   RUNNING
 [INFO] corba-testsuite/corba-mytime   FAILURE (0:00:38.511)
 Java returned: 1
 [INFO] deployment-testsuite/deployment-tests  RUNNING
 [INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:35.017)
 [INFO] deployment-testsuite/jca-cms-tests RUNNING
 [INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.879)
 [INFO] deployment-testsuite/manifestcp-tests  RUNNING
 [INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:36.766)
 [INFO] enterprise-testsuite/ejb-tests RUNNING
 [INFO] enterprise-testsuite/ejb-tests FAILURE (0:01:06.704)
 Java returned: 1
 [INFO] enterprise-testsuite/jms-tests RUNNING
 [INFO] enterprise-testsuite/jms-tests FAILURE (0:00:45.748)
 Java returned: 1
 [INFO] enterprise-testsuite/jpa-tests RUNNING
 [INFO] enterprise-testsuite/jpa-tests FAILURE (0:00:44.101)
 Java returned: 1
 [INFO] enterprise-testsuite/sec-clientRUNNING
 [INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.810)
 [INFO] enterprise-testsuite/sec-tests RUNNING
 [INFO] enterprise-testsuite/sec-tests FAILURE (0:00:35.854)
 Java returned: 1
 [INFO] security-testsuite/test-security   RUNNING
 [INFO] security-testsuite/test-security   FAILURE (0:00:46.252)
 Java returned: 1
 [INFO] web-testsuite/test-2.1-jspsRUNNING
 [INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:35.117)
 [INFO] web-testsuite/test-2.5-servletsRUNNING
 [INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:30.992)
 [INFO] web-testsuite/test-myfaces RUNNING
 [INFO] web-testsuite/test-myfaces SUCCESS (0:00:32.811)
 [INFO] web-testsuite/test-tomcat  RUNNING
 [INFO] web-testsuite/test-tomcat  SUCCESS (0:00:24.121)
 [INFO] web-testsuite/test-web-forward RUNNING
 [INFO] web-testsuite/test-web-forward FAILURE (0:00:33.124)
 Java returned: 1
 [INFO] web-testsuite/test-web-references  RUNNING
 [INFO] web-testsuite/test-web-references  FAILURE (0:00:37.549)
 Java returned: 1
 [INFO] webservices-testsuite/jaxb-tests   RUNNING
 [INFO] webservices-testsuite/jaxb-tests   SUCCESS (0:01:07.333)
 [INFO] webservices-testsuite/jaxr-tests   RUNNING
 [INFO

[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile

2009-07-21 Thread Forrest Xia (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12733655#action_12733655
]

Forrest Xia commented on GERONIMO-4222:
---

Does some testing on this issue. Conclude that:
1. tranql-connector-postgresql-xa adapter has no such problem.
2. tranql-connector-postgresql-local does have such problem

Besides the exception described by Radim Kolar, additional exceptions are:
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:103)
at java.net.SocketOutputStream.write(SocketOutputStream.java:147)
at
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:76)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:134)
at org.postgresql.core.PGStream.flush(PGStream.java:508)
at
org.postgresql.core.v3.QueryExecutorImpl.sendSync(QueryExecutorImpl.java:676)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
... 62 more

Seems for local transaction db pool of Postgresql, the bad connection won't be
threw out, for following db request, the server still return the bad connection
to application.

But for XA transaction db pool of Postgresql, no such problem.

Database pool unusable after database unavailable for awhile

Key: GERONIMO-4222
URL: https://issues.apache.org/jira/browse/GERONIMO-4222
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0.2, 2.1.3, 2.1.4
Environment: Red Hat Enterprise Linux Server v5.2
WAS-CE v2.0.0.1, based on Geronimo v2.0.2
Reporter: David Frahm
Fix For: Wish List

Attachments: before and after wasce restart.txt, stacktrace.txt

I have frequent trouble with my database pool to an AS/400. The database is
taken down every night for backup, and at least once a week the connection
pool is unusable after the database comes back up. Restarting the connection
pool makes everything work again.
We are new to Geronimo/WAS-CE -- just this one app on one server -- so I
don't have anything to compare to. However, we have had this same issue with
a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are
several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble.
Configuration Info
Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver)
Pool Min Size: 0
Pool Max Size: 100
Blocking Timeout: 5000
Idle Timeout: 15

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [BUILD] trunk: Failed for Revision: 796268

2009-07-21 Thread David Jencks


I moved at least one file from each failure :-)

we'll see if that is enough...

thanks
david jencks

On Jul 21, 2009, at 8:14 AM, Ivan wrote:

No the pom.xml file, the reason is that those deployment plan files  
contains the placeholders, I guess that we need to move them to the  
filtered-resources folder ?


2009/7/21 Ivan xhh...@gmail.com
Seems that those placeholders in the pom.xml are not replaced, like $ 
{project.build.directory}/${artifactId}-${version}.ear.


2009/7/21 ga...@apache.org

Geronimo Revision: 796268 built with tests included

See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/build-0900.log

Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721
[INFO] BUILD SUCCESSFUL
[INFO]  


[INFO] Total time: 43 minutes 6 seconds
[INFO] Finished at: Tue Jul 21 09:47:56 EDT 2009
[INFO] Final Memory: 400M/1014M
[INFO]  



TESTSUITE RESULTS (Failures only)
=

Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/logs-0900-tomcat/


[INFO]  
---

[INFO]
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS  
(0:01:18.110)

[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS  
(0:00:35.438)

[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS  
(0:00:40.040)

[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS  
(0:00:21.145)

[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  FAILURE  
(0:01:02.257) Java returned: 1

[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS  
(0:01:34.237)

[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS  
(0:02:03.987)

[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   FAILURE  
(0:00:37.538) Java returned: 1

[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  FAILURE  
(0:00:31.478) Java returned: 1

[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   FAILURE  
(0:00:38.511) Java returned: 1

[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS  
(0:00:35.017)

[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS  
(0:00:31.879)

[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS  
(0:00:36.766)

[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests FAILURE  
(0:01:06.704) Java returned: 1

[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE  
(0:00:45.748) Java returned: 1

[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests FAILURE  
(0:00:44.101) Java returned: 1

[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS  
(0:00:30.810)

[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE  
(0:00:35.854) Java returned: 1

[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE  
(0:00:46.252) Java returned: 1

[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS  
(0:00:35.117)

[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS  
(0:00:30.992)

[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS  
(0:00:32.811)

[INFO] web-testsuite/test-tomcat  RUNNING
[INFO] web-testsuite/test-tomcat  SUCCESS  
(0:00:24.121)

[INFO] web-testsuite/test-web-forward RUNNING
[INFO] web-testsuite/test-web-forward FAILURE  
(0:00:33.124) Java returned: 1

[INFO] web-testsuite/test-web-references  RUNNING
[INFO] web-testsuite/test-web-references  FAILURE  
(0:00:37.549) Java returned: 1

[INFO] webservices-testsuite/jaxb-tests

Re: [Discuss] ApacheCon '09 Geronimo Track: Content

2009-07-21 Thread Kevan Miller



On Jul 21, 2009, at 9:23 AM, Donald Woods wrote:


Maybe we can create a mashup of the proposals to cover the following:

Session 1 - Geronimo 2.2 topics (current user community)
Administering Geronimo
Custom Server Assemblies
Securing Apps
Load balancing and high-availability
Would expect this session would contain more than we could cover in  
50 minutes, but we should introduce each topic and include pointers  
to the online docs that users could reference later for more details.


That's too much for a single session, IMO. IIRC, at least one of the  
presentation topics was given at ApacheCon, last year. So, I'd want it  
to be more focused.




Session 2 - Blueprint Container Spec and Geronimo

Session 3 - Geronimo 3.0 and Java EE 6 (futures)
Geronimo 3.0 based on OSGi
Current milestone features
Present how much of Web Profile is available
JPA 2.0, EJB 3.1, Servlet 3.0, ...
How to start using 3.0 builds


Certainly possible. I currently tend towards my initial thoughts. But  
would like to hear other's thoughts.


--kevan

[BUILD] branches/2.1: Failed for Revision: 796376

Geronimo Revision: 796376 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090721/build-1400.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090721
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 38 minutes 18 seconds
[INFO] Finished at: Tue Jul 21 14:43:11 EDT 2009
[INFO] Final Memory: 316M/925M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090721/logs-1400-tomcat/
 
[INFO] Running corba-testsuite.corba-mytime
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.451 
sec  FAILURE!
--
[INFO] Running sec-testsuite.security
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.714 
sec  FAILURE!
[INFO] Running web-testsuite.jsps
[INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 1.153 
sec  FAILURE!
--
[INFO] Running web-testsuite.myfaces
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.305 
sec  FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
[INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.8 sec 
 FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.47 sec 
 FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.209 
sec  FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.203 
sec  FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.217 
sec  FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090721/logs-1400-jetty/
 
[INFO] Running corba-testsuite.corba-mytime
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.496 
sec  FAILURE!
--
[INFO] Running sec-testsuite.security
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.719 
sec  FAILURE!
[INFO] Running web-testsuite.jsps
[INFO] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 1.215 
sec  FAILURE!
--
[INFO] Running web-testsuite.myfaces
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.351 
sec  FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest
[INFO] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.695 
sec  FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXRTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.183 
sec  FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebStaxTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.216 
sec  FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebJAXBTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.204 
sec  FAILURE!
--
[INFO] Running org.apache.geronimo.testsuite.testset.WebSAAJTest
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.234 
sec  FAILURE!
 
Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090721/samples-1400.log
 
Build status: OK

[BUILD] trunk: Failed for Revision: 796422

Geronimo Revision: 796422 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 42 minutes 5 seconds
[INFO] Finished at: Tue Jul 21 15:46:51 EDT 2009
[INFO] Final Memory: 399M/994M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090721/logs-1500-tomcat/
 
 
[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.735
[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.491) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:35.476) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:39.632) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.230) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  FAILURE (0:00:52.380) Java 
returned: 1
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.930) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:02.772) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:56.475) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:55.450) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:48.386) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:34.096) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:32.684) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:35.172) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:06.366) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:03.453) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.122) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.096) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:37.396) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:44.016) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.042) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:30.733) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.673) 
[INFO] web-testsuite/test-tomcat  RUNNING
[INFO] web-testsuite/test-tomcat  SUCCESS (0:00:24.311) 
[INFO] web-testsuite/test-web-forward RUNNING
[INFO] web-testsuite/test-web-forward SUCCESS (0:00:38.352) 
[INFO] web-testsuite/test-web-references

[BUILD] trunk: Failed for Revision: 796590