[jira] Updated: (GERONIMO-5662) fail to replace default Security Realm
[ https://issues.apache.org/jira/browse/GERONIMO-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang updated GERONIMO-5662: - Description: setps to recur: 1. start the Geronimo server, and then open the admin console. 2.In security realms portlet, click on Add new security realm link. 3.Select realm name and use test-prop-file-realm for realm-name, and then select Properties File Realm and click on Next button. 4.Enter Users File URI (var/security/users.properties) and Groups File URI ( var/security/groups.properties) and click on Next button. 5.Click on Skip Test and Deploy button. 6. Check the realm named test-prop-file-realm should be listed in the security realms portlet. 7.Deploy geronimo-ldap-demo-1.1.war using plan file prop-file-realm-tester.xml and access the application at http://localhost:8080/prop-file-realm-test 8.Access Protect link to verify that the realm is functional. 9.Login should succeed for uid=system, pwd=manager 10.In Security Realms portlet,click on edit link next to the security realm to be edited. 11.Modify the properties and click on Save button. 12.The new properties should take effect at the next time when the realm is used. was: setps to recur: 1. start the Geronimo server, and then open the admin console. 2.In security realms portlet, click on Add new security realm link. 3.Select realm name and use test-prop-file-realm for realm-name, and then select Properties File Realm and click on Next button. 4.Enter Users File URI (var/security/users.properties) and Groups File URI ( var/security/groups.properties) and click on Next button. 5.Click on Skip Test and Deploy button. 6. Check the realm named test-prop-file-realm should be listed in the security realms portlet. 7.Deploy geronimo-ldap-demo-1.1.war using plan file prop-file-realm-tester.xml and access the application at http://localhost:8080/prop-file-realm-test 8.Access Protect link to verify that the realm is functional. 9.Login should succeed for uid=system, pwd=manager 10.In Security Realms portlet,click on edit link next to the security realm to be edited. 11.Modify the properties and click on Save button. 12.The new properties should be effective the next time the realm is used. fail to replace default Security Realm -- Key: GERONIMO-5662 URL: https://issues.apache.org/jira/browse/GERONIMO-5662 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Assignee: viola.lu Priority: Minor Fix For: 3.0 Attachments: VerifyReplaceDefaultSecurityRealm-SEC001.zip setps to recur: 1. start the Geronimo server, and then open the admin console. 2.In security realms portlet, click on Add new security realm link. 3.Select realm name and use test-prop-file-realm for realm-name, and then select Properties File Realm and click on Next button. 4.Enter Users File URI (var/security/users.properties) and Groups File URI ( var/security/groups.properties) and click on Next button. 5.Click on Skip Test and Deploy button. 6. Check the realm named test-prop-file-realm should be listed in the security realms portlet. 7.Deploy geronimo-ldap-demo-1.1.war using plan file prop-file-realm-tester.xml and access the application at http://localhost:8080/prop-file-realm-test 8.Access Protect link to verify that the realm is functional. 9.Login should succeed for uid=system, pwd=manager 10.In Security Realms portlet,click on edit link next to the security realm to be edited. 11.Modify the properties and click on Save button. 12.The new properties should take effect at the next time when the realm is used. -- 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: 1027388
Geronimo Revision: 1027388 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 40 minutes 32 seconds
[INFO] Finished at: Tue Oct 26 03:53:57 EDT 2010
[INFO] Final Memory: 478M/1007M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/logs-0300-tomcat/
[INFO] snapshot org.apache.geronimo.framework:framework:3.0-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-selenium:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-selenium:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.testsupport:testsupport:3.0-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.testsupport:testsupport:3.0-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from jetty.oss.sonatype.org
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from openqa-snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from jetty.oss.sonatype.org
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from openqa-snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/3.0-SNAPSHOT/testsuite-3.0-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo TestSuite :: Commands TestSuite
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/commands-testsuite/3.0-SNAPSHOT/commands-testsuite-3.0-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo TestSuite :: Commands Testsuite :: Deployer
[INFO]task-segment: [install]
[INFO]
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/plugins/maven-failsafe-plugin/2.5/maven-failsafe-plugin-2.5.pom
9K downloaded (maven-failsafe-plugin-2.5.pom)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire
Failed to resolve artifact: xmlpull:xmlpull:jar:1.1.3.4d_b4_min
I found that a xmlpull dependency is missing from central repo. Does anyone know how to report this kind of issues ? * [INFO] * * [ERROR] BUILD ERROR* * [INFO] * * [INFO] Failed to resolve artifact.* * * * Missing:* * --* * 1) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * Try downloading the file manually from the project website.* * * * Then, install it using the command: * * mvn install:install-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file* * * * Alternatively, if you host your own repository you can deploy the file there: * * mvn deploy:deploy-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]* * * * Path to dependency: * * 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * 2) org.apache.activemq:activemq-web:jar:5.4.1* * 3) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * --* * 1 required artifact is missing.* * * * for artifact: * * org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * * * from the specified remote repositories:* * central (http://repo1.maven.org/maven2),* * codehaus.snapshots (http://snapshots.repository.codehaus.org),* * apache.snapshots (http://repository.apache.org/snapshots),* -- Shawn
[BUILD] branches/2.1: Failed for Revision: 1027368
Geronimo Revision: 1027368 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20101026/build-0200.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.1/20101026 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 32 minutes 40 seconds [INFO] Finished at: Tue Oct 26 02:45:50 EDT 2010 [INFO] Final Memory: 270M/1014M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.1/20101026/logs-0200-tomcat/ [INFO] Running console-testsuite.basic-console [INFO] Tests run: 49, Failures: 19, Errors: 0, Skipped: 15, Time elapsed: 60.571 sec FAILURE! -- [INFO] Running security-testsuite.security [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 61.557 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.1/20101026/logs-0200-jetty/ Samples: branches/2.1 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.1/20101026/samples-0200.log Build status: FAILED
[jira] Commented: (GERONIMO-5661) Geronimo fails to start when there is a whitespace in Geronimo_HOME
[ https://issues.apache.org/jira/browse/GERONIMO-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924909#action_12924909 ] Shawn Jiang commented on GERONIMO-5661: --- There's a similar issue that was fixed in 22 branch before. I guess the fix there could also fix this problem. https://issues.apache.org/jira/browse/GERONIMO-4389 Geronimo fails to start when there is a whitespace in Geronimo_HOME --- Key: GERONIMO-5661 URL: https://issues.apache.org/jira/browse/GERONIMO-5661 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Environment: Ubuntu 9.04+Sun JDK 1.6.0_18 Reporter: Chi Runhua Geronimo 2.2.1 works fine when there is a whitespace within GERONIMO_HOME while G3.0 fails to start. + jeff...@ubuntu:~/Documents/Geronimo/test/Document and setting/g30/bin$ ./geronimo run Using GERONIMO_HOME: /home/jeffchi/Documents/Geronimo/test/Document and setting/g30 Using GERONIMO_TMPDIR: var/temp Using JRE_HOME:/opt/sun/jdk1.6.0_18/jre Exception in thread main java.lang.NoClassDefFoundError: and Caused by: java.lang.ClassNotFoundException: and at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Could not find the main class: and. Program will exit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Failed to resolve artifact: xmlpull:xmlpull:jar:1.1.3.4d_b4_min
Hi, this is fixed on the trunk, so instead of xmlpull we now use xpp3 version 1.1.4c. If you need to build the older version, you can use a bit older version 1.1.3.4a of xmlpull, just change xmlpull-version in pom.xml Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Oct 26, 2010 at 10:40 AM, Shawn Jiang genspr...@gmail.com wrote: I found that a xmlpull dependency is missing from central repo. Does anyone know how to report this kind of issues ? * [INFO] * * [ERROR] BUILD ERROR* * [INFO] * * [INFO] Failed to resolve artifact.* * * * Missing:* * --* * 1) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * Try downloading the file manually from the project website.* * * * Then, install it using the command: * * mvn install:install-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file* * * * Alternatively, if you host your own repository you can deploy the file there: * * mvn deploy:deploy-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]* * * * Path to dependency: * * 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * 2) org.apache.activemq:activemq-web:jar:5.4.1* * 3) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * --* * 1 required artifact is missing.* * * * for artifact: * * org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * * * from the specified remote repositories:* * central (http://repo1.maven.org/maven2),* * codehaus.snapshots (http://snapshots.repository.codehaus.org),* * apache.snapshots (http://repository.apache.org/snapshots),* -- Shawn
[jira] Closed: (GERONIMO-5562) Filter error from console application deployer/uninstall operations.
[ https://issues.apache.org/jira/browse/GERONIMO-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-5562. - Resolution: Cannot Reproduce Should be fixed. Filter error from console application deployer/uninstall operations. - Key: GERONIMO-5562 URL: https://issues.apache.org/jira/browse/GERONIMO-5562 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Rick McGuire Assignee: Shawn Jiang Using the console deployer to install a simple war file (in this case, the sample app attached to GERONIMO-5553) the following error results: HTTP ERROR 400 Problem accessing /console/portal/2-2-1/Applications/User%20Assets/Web%20App%20WARs/__pmconsole-base0x2WARModules!2015881605%7C0_view/__wsconsole-base0x2WARModules!2015881605%7C0_normal. Reason: XSSXSRFFilter blocked HttpServletRequest due to invalid FORM content. The application appears to have been installed correctly. If the application is uninstalled using the console, this error occurs again (also with the operation completing successfully). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Welcome Janet Hong Fang Han as a new committer
Congrats Janet. On Fri, Oct 22, 2010 at 10:34 AM, viola lu viola...@gmail.com wrote: Congrats! On Fri, Oct 22, 2010 at 9:37 AM, han hongfang hanhongf...@gmail.comwrote: Thank you all for the congratulations. I'm excited and glad to work with all of you~ On Thu, Oct 21, 2010 at 8:40 PM, Ted Kirby ted.ki...@gmail.com wrote: Congratulations Janet! Welcome aboard! Ted On Wed, Oct 20, 2010 at 9:11 PM, Ivan xhh...@gmail.com wrote: I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan -- Best regards, Han Hong Fang -- viola
[VOTE] release geronimo txmanager and connector components 2.2.1
This is a bug-fix release that will be used for the Geronimo server 2.2.1 and 2.1.7 releases. The following Jiras included in this update. GERONIMO-5649 txmanager could try to replace dead XAResources in commit and rollback tasks The components up for vote are: org/apache/geronimo/components/geronimo-txmanager-parent/2.2.1/geronimo-txmanager-parent-2.2.1-source-release.tar.gz org/apache/geronimo/components/geronimo-txmanager-parent/2.2.1/geronimo-txmanager-parent-2.2.1-source-release.zip from the staging repository at: https://repository.apache.org/content/repositories/orgapachegeronimo-006/ The source repo is: https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.2.1 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Rick
slow jetty shutdown
Hi, I have been playing with a newer Jetty version for Geronimo 2.2 lately, and I'm happy to see that the branch has been updated to 7.2.0.v20101020. However the server shutdown is terribly slow now (takes more than a minute). Any idea what might be causing this? I have checked that the standalone Jetty distribution does not have the same problem, nor does Geronimo 2.2 r1027366. I'm on OS X 10.6 with Java 6. Thanks Trygve
[BUILD] branches/2.2: Failed for Revision: 1027482
Geronimo Revision: 1027482 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026/build-0800.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 38 minutes 6 seconds [INFO] Finished at: Tue Oct 26 08:45:13 EDT 2010 [INFO] Final Memory: 307M/998M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026/logs-0800-tomcat/ [INFO] Running TestSuite [INFO] Tests run: 40, Failures: 23, Errors: 0, Skipped: 0, Time elapsed: 219.164 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 85.544 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 68.55 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026/logs-0800-jetty/ Booting Geronimo Kernel (in Java 1.5.0_18)... Module 1/74 org.apache.geronimo.framework/j2ee-system/2.2.1-SNAPSHOT/car started in .000s Module 2/74 org.apache.geronimo.framework/jee-specs/2.2.1-SNAPSHOT/car started in .001s Module 3/74 org.apache.geronimo.plugins.classloaders/xbean-finder/2.2.1-SNAPSHOT/car started in .000s Module 4/74 org.apache.geronimo.framework/xmlbeans/2.2.1-SNAPSHOT/car started in .000s Module 5/74 org.apache.geronimo.framework/rmi-naming/2.2.1-SNAPSHOT/car started in .248s Module 6/74 org.apache.geronimo.plugins.classloaders/geronimo-javaee-deployment_1.1MR3_spec/2.2.1-SNAPSHOT/car started in .001s Module 7/74 org.apache.geronimo.framework/plugin/2.2.1-SNAPSHOT/car started in .972s Module 8/74 org.apache.geronimo.framework/geronimo-gbean-deployer/2.2.1-SNAPSHOT/car started in .587s Module 9/74 org.apache.geronimo.configs/j2ee-server/2.2.1-SNAPSHOT/car started in .107s Module 10/74 org.apache.geronimo.framework/j2ee-security/2.2.1-SNAPSHOT/car started in .380s Module 11/74 org.apache.geronimo.framework/server-security-config/2.2.1-SNAPSHOT/car started in .053s Module 12/74 org.apache.geronimo.plugins.classloaders/geronimo-schema-jee_5/2.2.1-SNAPSHOT/car started in .001s Module 13/74 org.apache.geronimo.configs/j2ee-deployer/2.2.1-SNAPSHOT/car started in .255s Module 14/74 org.apache.geronimo.configs/client-deployer/2.2.1-SNAPSHOT/car started in .101s Module 15/74 org.apache.geronimo.configs/aspectj/2.2.1-SNAPSHOT/car started in .050s Module 16/74 org.apache.geronimo.configs/clustering/2.2.1-SNAPSHOT/car started in .191s Module 17/74 org.apache.geronimo.configs/transaction/2.2.1-SNAPSHOT/car started in .289s Module 18/74 org.apache.geronimo.configs/connector-deployer/2.2.1-SNAPSHOT/car started in .179s Module 19/74 org.apache.geronimo.configs/derby/2.2.1-SNAPSHOT/car started in .000s Module 20/74 org.apache.geronimo.configs/system-database/2.2.1-SNAPSHOT/car started in 4.224s Module 21/74 org.apache.geronimo.configs/openjpa/2.2.1-SNAPSHOT/car started in .014s Module 22/74 org.apache.geronimo.configs/webservices-common/2.2.1-SNAPSHOT/car started in .000s Module 23/74 org.apache.geronimo.configs/openejb/2.2.1-SNAPSHOT/car started in 1.389s Module 24/74 org.apache.geronimo.configs/openejb-deployer/2.2.1-SNAPSHOT/car started in .207s Module 25/74 org.apache.geronimo.configs/openejb-clustering-builder-wadi/2.2.1-SNAPSHOT/car started in 1.144s Module 26/74 org.apache.geronimo.configs/jetty7/2.2.1-SNAPSHOT/car 2010-10-26 10:06:14,766 WARN [log] Acceptors should be =2*availableProcessors: selectchannelconnec...@0.0.0.0:8080 2010-10-26 10:06:14,819 WARN [log] Acceptors
[BUILD] trunk: Failed for Revision: 1027536
Geronimo Revision: 1027536 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 44 minutes 52 seconds
[INFO] Finished at: Tue Oct 26 09:48:29 EDT 2010
[INFO] Final Memory: 478M/1007M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/logs-0900-tomcat/
[INFO] snapshot org.apache.geronimo.framework:framework:3.0-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:framework:3.0-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-selenium:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-selenium:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.testsupport:testsupport:3.0-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.testsupport:testsupport:3.0-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from jetty.oss.sonatype.org
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from openqa-snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from jetty.oss.sonatype.org
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from openqa-snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/3.0-SNAPSHOT/testsuite-3.0-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo TestSuite :: Commands TestSuite
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/commands-testsuite/3.0-SNAPSHOT/commands-testsuite-3.0-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo TestSuite :: Commands Testsuite :: Deployer
[INFO]task-segment: [install]
[INFO]
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/plugins/maven-failsafe-plugin/2.5/maven-failsafe-plugin-2.5.pom
9K downloaded (maven
Re: slow jetty shutdown
On Oct 26, 2010, at 9:15 AM, Trygve Sanne Hardersen wrote: Hi, I have been playing with a newer Jetty version for Geronimo 2.2 lately, and I'm happy to see that the branch has been updated to 7.2.0.v20101020. However the server shutdown is terribly slow now (takes more than a minute). Any idea what might be causing this? I have checked that the standalone Jetty distribution does not have the same problem, nor does Geronimo 2.2 r1027366. I'm on OS X 10.6 with Java 6. I haven't run with the newer jetty. Can you send a kill -3 to the server process during server shutdown to capture the java thread stack traces? Should give some indication about what's happening during your slow shutdown... --kevan
Re: [BUILD] branches/2.2: Failed for Revision: 1026529
On Oct 25, 2010, at 4:20 PM, Jarek Gawor wrote:
I haven't had a chance to but make sure to test it in headless mode.
That's what the automatic tests are doing.
Running on a Mac (-Pit,all-subprojects,headless in headless or non-headless
mode, I get the following:
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running TestSuite
[INFO] Tests run: 8, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 2.238
sec FAILURE!
[INFO]
[INFO] Results :
[INFO]
[INFO] Failed tests:
[INFO]
testEchoImageWithMTOMSupport(org.apache.geronimo.jaxws.mtom.WebMTOMTest)
[INFO]
testEchoImageWithoutMTOMSupport(org.apache.geronimo.jaxws.mtom.WebMTOMTest)
[INFO]
testEchoImageWithMTOMSupport(org.apache.geronimo.jaxws.mtom.EJBMTOMTest)
[INFO]
testEchoImageWithoutMTOMSupport(org.apache.geronimo.jaxws.mtom.EJBMTOMTest)
[INFO]
[INFO] Tests run: 8, Failures: 4, Errors: 0, Skipped: 0
IIUC, the automated tests are running with:
-Pit,all-subprojects,headless
I can't get all-subprojects to work. It fails with:
[INFO]
[INFO] Building Geronimo TestSuite :: Commands Testsuite :: Deployer
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set:
/Users/kevan/geronimo/server/branches/2.2/testsuite/commands-testsuite/deploy/target
(included: [**], exc\
luded: [])
[INFO] [:invoke {execution: clean}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] At least one pom file must be included
--kevan
Re: Server startup failure - geronimo-tomcat7-javaee6-3.0-SNAPSHOT
After patch and rebuild OWB locally, the server is started OK, but when shutdown, the console show this exception: 2010-10-26 22:38:07,822 WARN [LifecycleMBeanBase] Failed to unregister MBean with name [Catalina:j2eeType=WebModule,name=// 0.0.0.0/,J2EEApplication=null,J2EEServer=geronimo] during component destruction javax.management.InstanceNotFoundException: Catalina:j2eeType=WebModule,name=// 0.0.0.0/,J2EEApplication=null,J2EEServer=geronimo at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:415) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:403) at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:506) at org.apache.catalina.util.LifecycleMBeanBase.unregister(LifecycleMBeanBase.java:191) at org.apache.catalina.util.LifecycleMBeanBase.destroyInternal(LifecycleMBeanBase.java:73) at org.apache.catalina.core.ContainerBase.destroyInternal(ContainerBase.java:1109) at org.apache.catalina.core.StandardContext.destroyInternal(StandardContext.java:5114) at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:271) at org.apache.geronimo.tomcat.GeronimoStandardContext.kill(GeronimoStandardContext.java:423) at org.apache.geronimo.tomcat.TomcatContainer.removeContext(TomcatContainer.java:336) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStop(TomcatWebAppContext.java:575) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1164) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:346) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:191) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:568) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:430) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:183) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:568) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:430) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:183) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:568) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:430) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:183) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:568) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:430) at org.apache.geronimo.kernel.osgi.ConfigurationActivator.stop(ConfigurationActivator.java:93) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:843) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:836) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:474) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:546) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1098) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:593) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:261) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:216) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:266) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:685) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:583) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle$1.run(InternalSystemBundle.java:243) at java.lang.Thread.run(Thread.java:619) Forrest
Re: slow jetty shutdown
On 10/26/2010 10:21 AM, Kevan Miller wrote: On Oct 26, 2010, at 9:15 AM, Trygve Sanne Hardersen wrote: Hi, I have been playing with a newer Jetty version for Geronimo 2.2 lately, and I'm happy to see that the branch has been updated to 7.2.0.v20101020. However the server shutdown is terribly slow now (takes more than a minute). Any idea what might be causing this? I have checked that the standalone Jetty distribution does not have the same problem, nor does Geronimo 2.2 r1027366. I'm on OS X 10.6 with Java 6. I haven't run with the newer jetty. Can you send a kill -3 to the server process during server shutdown to capture the java thread stack traces? Should give some indication about what's happening during your slow shutdown... I can't even get the server to start up with the new Jetty. There appear to be some interface changes that still need to be accounted for (working on a potential fix). Not much has been done with the new version yet...the switch was done less than 24 hours ago primarily to see if there are any issues with making the switch. Rick --kevan
Re: Server startup failure - geronimo-tomcat7-javaee6-3.0-SNAPSHOT
Not sure whether it is caused by using the latest Tomcat codes, might be some integration codes are required to update. I will check it later this week. 2010/10/26 Forrest Xia forres...@gmail.com After patch and rebuild OWB locally, the server is started OK, but when shutdown, the console show this exception: 2010-10-26 22:38:07,822 WARN [LifecycleMBeanBase] Failed to unregister MBean with name [Catalina:j2eeType=WebModule,name=// 0.0.0.0/,J2EEApplication=null,J2EEServer=geronimo] during component destruction javax.management.InstanceNotFoundException: Catalina:j2eeType=WebModule,name=// 0.0.0.0/,J2EEApplication=null,J2EEServer=geronimo at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:415) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:403) at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:506) at org.apache.catalina.util.LifecycleMBeanBase.unregister(LifecycleMBeanBase.java:191) at org.apache.catalina.util.LifecycleMBeanBase.destroyInternal(LifecycleMBeanBase.java:73) at org.apache.catalina.core.ContainerBase.destroyInternal(ContainerBase.java:1109) at org.apache.catalina.core.StandardContext.destroyInternal(StandardContext.java:5114) at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:271) at org.apache.geronimo.tomcat.GeronimoStandardContext.kill(GeronimoStandardContext.java:423) at org.apache.geronimo.tomcat.TomcatContainer.removeContext(TomcatContainer.java:336) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStop(TomcatWebAppContext.java:575) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1164) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:346) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:191) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:568) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:430) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:183) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:568) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:430) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:183) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:568) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:430) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:183) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:568) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:430) at org.apache.geronimo.kernel.osgi.ConfigurationActivator.stop(ConfigurationActivator.java:93) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:843) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:836) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:474) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:546) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1098) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:593) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:261) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:216) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:266) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:685) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:583) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle$1.run(InternalSystemBundle.java:243) at java.lang.Thread.run(Thread.java:619) Forrest -- Ivan
Re: slow jetty shutdown
Thanks for you suggestions. I have been using Jetty trunk internally for a couple of weeks, and did my own changes to the Geronimo codebase to make them work. These are much the same as the ones that have been added to Geronimo now, so I have replaced them with your changes. I haven't had any problems running the new Jetty once the changes to Geronimo were in place, but I'll try to debug/kill the server during shutdown and let you know what I find. Trygve On Tue, Oct 26, 2010 at 4:47 PM, Rick McGuire rick...@gmail.com wrote: On 10/26/2010 10:21 AM, Kevan Miller wrote: On Oct 26, 2010, at 9:15 AM, Trygve Sanne Hardersen wrote: Hi, I have been playing with a newer Jetty version for Geronimo 2.2 lately, and I'm happy to see that the branch has been updated to 7.2.0.v20101020. However the server shutdown is terribly slow now (takes more than a minute). Any idea what might be causing this? I have checked that the standalone Jetty distribution does not have the same problem, nor does Geronimo 2.2 r1027366. I'm on OS X 10.6 with Java 6. I haven't run with the newer jetty. Can you send a kill -3 to the server process during server shutdown to capture the java thread stack traces? Should give some indication about what's happening during your slow shutdown... I can't even get the server to start up with the new Jetty. There appear to be some interface changes that still need to be accounted for (working on a potential fix). Not much has been done with the new version yet...the switch was done less than 24 hours ago primarily to see if there are any issues with making the switch. Rick --kevan
Re: slow jetty shutdown
On 10/26/2010 12:10 PM, Trygve Sanne Hardersen wrote: Thanks for you suggestions. I have been using Jetty trunk internally for a couple of weeks, and did my own changes to the Geronimo codebase to make them work. These are much the same as the ones that have been added to Geronimo now, so I have replaced them with your changes. I haven't had any problems running the new Jetty once the changes to Geronimo were in place, but I'll try to debug/kill the server during shutdown and let you know what I find. I just committed some fixes that finally allow the server to start and I'm seeing some exceptions and a very slow shutdown time now. From the exceptions, I have a feeling that there have been some lifecycle changes in jetty that are resulting in somethings getting restarted every time a filter is removed. This will probably take a little more work to sort out. Rick Trygve On Tue, Oct 26, 2010 at 4:47 PM, Rick McGuire rick...@gmail.com mailto:rick...@gmail.com wrote: On 10/26/2010 10:21 AM, Kevan Miller wrote: On Oct 26, 2010, at 9:15 AM, Trygve Sanne Hardersen wrote: Hi, I have been playing with a newer Jetty version for Geronimo 2.2 lately, and I'm happy to see that the branch has been updated to 7.2.0.v20101020. However the server shutdown is terribly slow now (takes more than a minute). Any idea what might be causing this? I have checked that the standalone Jetty distribution does not have the same problem, nor does Geronimo 2.2 r1027366. I'm on OS X 10.6 with Java 6. I haven't run with the newer jetty. Can you send a kill -3 to the server process during server shutdown to capture the java thread stack traces? Should give some indication about what's happening during your slow shutdown... I can't even get the server to start up with the new Jetty. There appear to be some interface changes that still need to be accounted for (working on a potential fix). Not much has been done with the new version yet...the switch was done less than 24 hours ago primarily to see if there are any issues with making the switch. Rick --kevan
Re: slow jetty shutdown
I've debugged the server shutdown and it hangs here; org.eclipse.jetty.server.nio.SelectChannelConnector # close , on the synchronized(this) call on line #127. Eventually it enters the synchronized block, but it takes long. Both the HTTP and HTTPS connectors are effected, but not the AJP connector. On the jetty-minimal server I only see warnings. Trygve On Tue, Oct 26, 2010 at 7:01 PM, Rick McGuire rick...@gmail.com wrote: On 10/26/2010 12:10 PM, Trygve Sanne Hardersen wrote: Thanks for you suggestions. I have been using Jetty trunk internally for a couple of weeks, and did my own changes to the Geronimo codebase to make them work. These are much the same as the ones that have been added to Geronimo now, so I have replaced them with your changes. I haven't had any problems running the new Jetty once the changes to Geronimo were in place, but I'll try to debug/kill the server during shutdown and let you know what I find. I just committed some fixes that finally allow the server to start and I'm seeing some exceptions and a very slow shutdown time now. From the exceptions, I have a feeling that there have been some lifecycle changes in jetty that are resulting in somethings getting restarted every time a filter is removed. This will probably take a little more work to sort out. Rick Trygve On Tue, Oct 26, 2010 at 4:47 PM, Rick McGuire rick...@gmail.com mailto: rick...@gmail.com wrote: On 10/26/2010 10:21 AM, Kevan Miller wrote: On Oct 26, 2010, at 9:15 AM, Trygve Sanne Hardersen wrote: Hi, I have been playing with a newer Jetty version for Geronimo 2.2 lately, and I'm happy to see that the branch has been updated to 7.2.0.v20101020. However the server shutdown is terribly slow now (takes more than a minute). Any idea what might be causing this? I have checked that the standalone Jetty distribution does not have the same problem, nor does Geronimo 2.2 r1027366. I'm on OS X 10.6 with Java 6. I haven't run with the newer jetty. Can you send a kill -3 to the server process during server shutdown to capture the java thread stack traces? Should give some indication about what's happening during your slow shutdown... I can't even get the server to start up with the new Jetty. There appear to be some interface changes that still need to be accounted for (working on a potential fix). Not much has been done with the new version yet...the switch was done less than 24 hours ago primarily to see if there are any issues with making the switch. Rick --kevan
Fwd: reviewboard instance at the ASF
FYI. I've requested that the geronimo repository be added to review board. Can see if we like it... --kevan Begin forwarded message: From: Gav... ga...@16degrees.com.au Date: October 26, 2010 12:02:48 AM EDT To: infrastruct...@apache.org Cc: committ...@apache.org Subject: reviewboard instance at the ASF Hi All, Infra has a reviewboard instance for all projects to use: https://blogs.apache.org/infra/entry/reviewboard_instance_running_at_the https://reviews.apache.org enjoy! Gav...
[BUILD] trunk: Failed for Revision: 1027688
Geronimo Revision: 1027688 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 37 seconds
[INFO] Finished at: Tue Oct 26 15:42:08 EDT 2010
[INFO] Final Memory: 477M/999M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/logs-1500-tomcat/
[INFO] snapshot org.apache.geronimo.framework:framework:3.0-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:framework:3.0-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-selenium:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-selenium:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.testsupport:testsupport:3.0-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.testsupport:testsupport:3.0-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from jetty.oss.sonatype.org
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from openqa-snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from jetty.oss.sonatype.org
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from openqa-snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/3.0-SNAPSHOT/testsuite-3.0-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo TestSuite :: Commands TestSuite
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/commands-testsuite/3.0-SNAPSHOT/commands-testsuite-3.0-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo TestSuite :: Commands Testsuite :: Deployer
[INFO]task-segment: [install]
[INFO]
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/plugins/maven-failsafe-plugin/2.5/maven-failsafe-plugin-2.5.pom
9K downloaded (maven
Re: Welcome Janet Hong Fang Han as a new committer
Congratulations Janet! Jay On 10/20/2010 08:11 PM, Ivan wrote: I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan
[BUILD] trunk: Failed for Revision: 1027790
Geronimo Revision: 1027790 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/build-2100.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/unit-test-reports
[INFO] Unable to find resource
'org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar:1.0.1' in repository JBoss
Repository (https://repository.jboss.org/nexus/content/groups/public-jboss/)
Downloading:
http://svn.apache.org/repos/asf/openejb/repo//org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0.1/geronimo-ejb_3.0_spec-1.0.1.jar
Downloading:
http://repository.apache.org/snapshots//org/apache/openwebbeans/openwebbeans-ee/1.1.0-SNAPSHOT/openwebbeans-ee-1.1.0-20101020.115827-1.jar
[INFO] Unable to find resource 'org.codehaus.swizzle:swizzle-stream:jar:1.0.2'
in repository openejb-3rdparty-builds
(http://svn.apache.org/repos/asf/openejb/repo/)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/swizzle/swizzle-stream/1.0.2/swizzle-stream-1.0.2.jar
[INFO] Unable to find resource
'org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar:1.0.1' in repository
openejb-3rdparty-builds (http://svn.apache.org/repos/asf/openejb/repo/)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0.1/geronimo-ejb_3.0_spec-1.0.1.jar
42K downloaded (swizzle-stream-1.0.2.jar)
17K downloaded (openwebbeans-ee-1.1.0-20101020.115827-1.jar)
[INFO] snapshot org.apache.geronimo.modules:geronimo-openwebbeans:3.0-SNAPSHOT:
checking for updates from jetty.oss.sonatype.org
1826K downloaded (openejb-core-3.2-20101022.020029-47.jar)
[INFO] snapshot org.apache.geronimo.modules:geronimo-openwebbeans:3.0-SNAPSHOT:
checking for updates from openqa-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-openwebbeans:3.0-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-openwebbeans:3.0-SNAPSHOT:
checking for updates from apache.snapshots
Downloading:
http://repository.apache.org/snapshots//org/apache/openwebbeans/openwebbeans-ee-common/1.1.0-SNAPSHOT/openwebbeans-ee-common-1.1.0-20101020.115827-1.jar
Downloading:
http://repository.apache.org/snapshots//org/apache/openejb/openejb-api/3.2-SNAPSHOT/openejb-api-3.2-20101022.020029-53.jar
11K downloaded (openwebbeans-ee-common-1.1.0-20101020.115827-1.jar)
31K downloaded (geronimo-ejb_3.0_spec-1.0.1.jar)
8K downloaded (openejb-api-3.2-20101022.020029-53.jar)
Downloading:
http://repository.apache.org/snapshots/org/apache/openejb/openejb-loader/3.2-SNAPSHOT/openejb-loader-3.2-20101022.020029-53.jar
43K downloaded (openejb-loader-3.2-20101022.020029-53.jar)
Downloading:
http://repository.apache.org/snapshots/org/apache/openejb/openejb-javaagent/3.2-SNAPSHOT/openejb-javaagent-3.2-20101022.020029-53.jar
12K downloaded (openejb-javaagent-3.2-20101022.020029-53.jar)
Downloading:
http://repository.apache.org/snapshots/org/apache/openejb/openejb-ejbd/3.2-SNAPSHOT/openejb-ejbd-3.2-20101022.020029-44.jar
59K downloaded (openejb-ejbd-3.2-20101022.020029-44.jar)
Downloading:
http://repository.apache.org/snapshots/org/apache/openejb/openejb-server/3.2-SNAPSHOT/openejb-server-3.2-20101022.020029-46.jar
86K downloaded (openejb-server-3.2-20101022.020029-46.jar)
Downloading:
http://repository.apache.org/snapshots/org/apache/openejb/openejb-client/3.2-SNAPSHOT/openejb-client-3.2-20101022.020029-46.jar
229K downloaded (openejb-client-3.2-20101022.020029-46.jar)
Downloading:
http://repository.apache.org/snapshots/org/apache/openejb/openejb-multicast/3.2-SNAPSHOT/openejb-multicast-3.2-20101022.020029-46.jar
50K downloaded (openejb-multicast-3.2-20101022.020029-46.jar)
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/openejb/geronimo-openejb/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 35 source files to
/home/geronimo/geronimo/trunk/plugins/openejb/geronimo-openejb/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/home/geronimo/geronimo/trunk/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/ThreadSingletonServiceAdapter.java:[32,29]
cannot find symbol
symbol : class OpenEJBLifecycle
location: package org.apache.openejb.cdi
/home/geronimo/geronimo/trunk/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/ThreadSingletonServiceAdapter.java:[33,29]
cannot find symbol
symbol
[BUILD] branches/2.2: Failed for Revision: 1027663
Geronimo Revision: 1027663 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026/build-1400.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 396 minutes 18 seconds [INFO] Finished at: Tue Oct 26 20:41:45 EDT 2010 [INFO] Final Memory: 341M/856M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026/logs-1400-tomcat/ [INFO] Running TestSuite [INFO] Tests run: 40, Failures: 21, Errors: 0, Skipped: 0, Time elapsed: 224.513 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 8, Errors: 0, Skipped: 0, Time elapsed: 65.396 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 69.75 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026/logs-1400-jetty/ [INFO] Running TestSuite [INFO] Tests run: 116, Failures: 3, Errors: 0, Skipped: 113, Time elapsed: 16.677 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 97.431 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.761 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.729 sec FAILURE! Samples: branches/2.2 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.2/20101026/samples-1400.log Build status: FAILED
Re: [jira] Commented: (GERONIMO-5661) Geronimo fails to start when there is a whitespace in Geronimo_HOME
The patch was applied to G30 cause JAVA_AGENT is quoted in the geronimo script. And the exec statement is as followed:. /opt/sun/jdk1.6.0_18/jre/bin/java -Xmx256m -XX:MaxPermSize=128m -javaagent:/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/agent/transformer.jar -Dkaraf.startLocalConsole=true -Dkaraf.startRemoteShell=false -Dorg.apache.geronimo.home.dir=/home/jeffchi/Documents/Geronimo/test/Document and setting/g30 -Dkaraf.home=/home/jeffchi/Documents/Geronimo/test/Document and setting/g30 -Dkaraf.base=/home/jeffchi/Documents/Geronimo/test/Document and setting/g30 -Djava.util.logging.config.file=/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/etc/java.util.logging.properties -Djava.endorsed.dirs=/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/endorsed:/opt/sun/jdk1.6.0_18/jre/lib/endorsed -Djava.ext.dirs=/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/ext:/opt/sun/jdk1.6.0_18/jre/lib/ext -Djava.io.tmpdir=var/temp -classpath /home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/commons-cli.jar:/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/geronimo-cli.jar:/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/geronimo-hook.jar:/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/geronimo-main.jar:/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/geronimo-rmi-loader.jar:/home/jeffchi/Documents/Geronimo/test/Document and setting/g30/lib/karaf-jaas-boot.jar org.apache.geronimo.cli.daemon.DaemonCLI If I put quotation marks over each argument, the server starts up successfully. However, each of variables in geronimo script is written as $GERONIMO_HOME or so. Could anyone shed any light on me? Jeff And I found out another problem in the geronimo script is On Tue, Oct 26, 2010 at 5:49 PM, Shawn Jiang (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/GERONIMO-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924909#action_12924909] Shawn Jiang commented on GERONIMO-5661: --- There's a similar issue that was fixed in 22 branch before. I guess the fix there could also fix this problem. https://issues.apache.org/jira/browse/GERONIMO-4389 Geronimo fails to start when there is a whitespace in Geronimo_HOME --- Key: GERONIMO-5661 URL: https://issues.apache.org/jira/browse/GERONIMO-5661 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Environment: Ubuntu 9.04+Sun JDK 1.6.0_18 Reporter: Chi Runhua Geronimo 2.2.1 works fine when there is a whitespace within GERONIMO_HOME while G3.0 fails to start. + jeff...@ubuntu:~/Documents/Geronimo/test/Document and setting/g30/bin$ ./geronimo run Using GERONIMO_HOME: /home/jeffchi/Documents/Geronimo/test/Document and setting/g30 Using GERONIMO_TMPDIR: var/temp Using JRE_HOME:/opt/sun/jdk1.6.0_18/jre Exception in thread main java.lang.NoClassDefFoundError: and Caused by: java.lang.ClassNotFoundException: and at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Could not find the main class: and. Program will exit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5661) Geronimo fails to start when there is a whitespace in Geronimo_HOME
[ https://issues.apache.org/jira/browse/GERONIMO-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu reassigned GERONIMO-5661: -- Assignee: viola.lu Geronimo fails to start when there is a whitespace in Geronimo_HOME --- Key: GERONIMO-5661 URL: https://issues.apache.org/jira/browse/GERONIMO-5661 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Environment: Ubuntu 9.04+Sun JDK 1.6.0_18 Reporter: Chi Runhua Assignee: viola.lu Geronimo 2.2.1 works fine when there is a whitespace within GERONIMO_HOME while G3.0 fails to start. + jeff...@ubuntu:~/Documents/Geronimo/test/Document and setting/g30/bin$ ./geronimo run Using GERONIMO_HOME: /home/jeffchi/Documents/Geronimo/test/Document and setting/g30 Using GERONIMO_TMPDIR: var/temp Using JRE_HOME:/opt/sun/jdk1.6.0_18/jre Exception in thread main java.lang.NoClassDefFoundError: and Caused by: java.lang.ClassNotFoundException: and at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Could not find the main class: and. Program will exit. -- 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: 1027790
3.0 failed to build because of openejb changes ? On Wed, Oct 27, 2010 at 9:39 AM, ga...@apache.org wrote: Geronimo Revision: 1027790 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101026/unit-test-reports [INFO] Unable to find resource 'org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar:1.0.1' in repository JBoss Repository ( https://repository.jboss.org/nexus/content/groups/public-jboss/) Downloading: http://svn.apache.org/repos/asf/openejb/repo//org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0.1/geronimo-ejb_3.0_spec-1.0.1.jar Downloading: http://repository.apache.org/snapshots//org/apache/openwebbeans/openwebbeans-ee/1.1.0-SNAPSHOT/openwebbeans-ee-1.1.0-20101020.115827-1.jar [INFO] Unable to find resource 'org.codehaus.swizzle:swizzle-stream:jar:1.0.2' in repository openejb-3rdparty-builds (http://svn.apache.org/repos/asf/openejb/repo/) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/swizzle/swizzle-stream/1.0.2/swizzle-stream-1.0.2.jar [INFO] Unable to find resource 'org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar:1.0.1' in repository openejb-3rdparty-builds (http://svn.apache.org/repos/asf/openejb/repo/) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0.1/geronimo-ejb_3.0_spec-1.0.1.jar 42Khttp://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0.1/geronimo-ejb_3.0_spec-1.0.1.jar%0A42Kdownloaded (swizzle-stream-1.0.2.jar) 17K downloaded (openwebbeans-ee-1.1.0-20101020.115827-1.jar) [INFO] snapshot org.apache.geronimo.modules:geronimo-openwebbeans:3.0-SNAPSHOT: checking for updates from jetty.oss.sonatype.org 1826K downloaded (openejb-core-3.2-20101022.020029-47.jar) [INFO] snapshot org.apache.geronimo.modules:geronimo-openwebbeans:3.0-SNAPSHOT: checking for updates from openqa-snapshots [INFO] snapshot org.apache.geronimo.modules:geronimo-openwebbeans:3.0-SNAPSHOT: checking for updates from codehaus.snapshots [INFO] snapshot org.apache.geronimo.modules:geronimo-openwebbeans:3.0-SNAPSHOT: checking for updates from apache.snapshots Downloading: http://repository.apache.org/snapshots//org/apache/openwebbeans/openwebbeans-ee-common/1.1.0-SNAPSHOT/openwebbeans-ee-common-1.1.0-20101020.115827-1.jar Downloading: http://repository.apache.org/snapshots//org/apache/openejb/openejb-api/3.2-SNAPSHOT/openejb-api-3.2-20101022.020029-53.jar 11Khttp://repository.apache.org/snapshots//org/apache/openejb/openejb-api/3.2-SNAPSHOT/openejb-api-3.2-20101022.020029-53.jar%0A11Kdownloaded (openwebbeans-ee-common-1.1.0-20101020.115827-1.jar) 31K downloaded (geronimo-ejb_3.0_spec-1.0.1.jar) 8K downloaded (openejb-api-3.2-20101022.020029-53.jar) Downloading: http://repository.apache.org/snapshots/org/apache/openejb/openejb-loader/3.2-SNAPSHOT/openejb-loader-3.2-20101022.020029-53.jar 43Khttp://repository.apache.org/snapshots/org/apache/openejb/openejb-loader/3.2-SNAPSHOT/openejb-loader-3.2-20101022.020029-53.jar%0A43Kdownloaded (openejb-loader-3.2-20101022.020029-53.jar) Downloading: http://repository.apache.org/snapshots/org/apache/openejb/openejb-javaagent/3.2-SNAPSHOT/openejb-javaagent-3.2-20101022.020029-53.jar 12Khttp://repository.apache.org/snapshots/org/apache/openejb/openejb-javaagent/3.2-SNAPSHOT/openejb-javaagent-3.2-20101022.020029-53.jar%0A12Kdownloaded (openejb-javaagent-3.2-20101022.020029-53.jar) Downloading: http://repository.apache.org/snapshots/org/apache/openejb/openejb-ejbd/3.2-SNAPSHOT/openejb-ejbd-3.2-20101022.020029-44.jar 59Khttp://repository.apache.org/snapshots/org/apache/openejb/openejb-ejbd/3.2-SNAPSHOT/openejb-ejbd-3.2-20101022.020029-44.jar%0A59Kdownloaded (openejb-ejbd-3.2-20101022.020029-44.jar) Downloading: http://repository.apache.org/snapshots/org/apache/openejb/openejb-server/3.2-SNAPSHOT/openejb-server-3.2-20101022.020029-46.jar 86Khttp://repository.apache.org/snapshots/org/apache/openejb/openejb-server/3.2-SNAPSHOT/openejb-server-3.2-20101022.020029-46.jar%0A86Kdownloaded (openejb-server-3.2-20101022.020029-46.jar) Downloading: http://repository.apache.org/snapshots/org/apache/openejb/openejb-client/3.2-SNAPSHOT/openejb-client-3.2-20101022.020029-46.jar 229Khttp://repository.apache.org/snapshots/org/apache/openejb/openejb-client/3.2-SNAPSHOT/openejb-client-3.2-20101022.020029-46.jar%0A229Kdownloaded (openejb-client-3.2-20101022.020029-46.jar) Downloading: http://repository.apache.org/snapshots/org/apache/openejb/openejb-multicast/3.2-SNAPSHOT/openejb-multicast-3.2-20101022.020029-46.jar 50Khttp://repository.apache.org/snapshots/org/apache/openejb/openejb-multicast/3.2-SNAPSHOT/openejb-multicast-3.2-20101022.020029-46.jar%0A50Kdownloaded (openejb-multicast-3.2
Re: slow jetty shutdown
Thanks Rick !
I just took a look at this problem, In method [1], there are about 50
SelectSet to close in the loop. Each one takes 1 second to complete
because SelectSet.stop() uses a Closer to do the closing job asynchronously
and wait for the closing for 1 second before closing it directly. The
asynchronous closing logic only get executed after SelectSet.select() is
called.
Adding set.doSelect() after set.stop() at method [1] did the trick. I did
not find a good way in geronimo side to fix this problem.
[1] org.eclipse.jetty.io.nio.SelectorManager.doStop()
protected void doStop() throws Exception
{
SelectSet[] sets= _selectSet;
_selectSet=null;
if (sets!=null)
{
for (SelectSet set : sets)
{
if (set!=null)
set.stop();
if (set!=null)
set.doSelect();
}
}
super.doStop();
}
On Wed, Oct 27, 2010 at 1:01 AM, Rick McGuire rick...@gmail.com wrote:
On 10/26/2010 12:10 PM, Trygve Sanne Hardersen wrote:
Thanks for you suggestions.
I have been using Jetty trunk internally for a couple of weeks, and did my
own changes to the Geronimo codebase to make them work. These are much the
same as the ones that have been added to Geronimo now, so I have replaced
them with your changes.
I haven't had any problems running the new Jetty once the changes to
Geronimo were in place, but I'll try to debug/kill the server during
shutdown and let you know what I find.
I just committed some fixes that finally allow the server to start and I'm
seeing some exceptions and a very slow shutdown time now. From the
exceptions, I have a feeling that there have been some lifecycle changes in
jetty that are resulting in somethings getting restarted every time a filter
is removed. This will probably take a little more work to sort out.
Rick
Trygve
On Tue, Oct 26, 2010 at 4:47 PM, Rick McGuire rick...@gmail.com mailto:
rick...@gmail.com wrote:
On 10/26/2010 10:21 AM, Kevan Miller wrote:
On Oct 26, 2010, at 9:15 AM, Trygve Sanne Hardersen wrote:
Hi, I have been playing with a newer Jetty version for
Geronimo 2.2 lately, and I'm happy to see that the branch
has been updated to 7.2.0.v20101020. However the server
shutdown is terribly slow now (takes more than a minute).
Any idea what might be causing this? I have checked that
the standalone Jetty distribution does not have the same
problem, nor does Geronimo 2.2 r1027366. I'm on OS X 10.6
with Java 6.
I haven't run with the newer jetty. Can you send a kill -3 to
the server process during server shutdown to capture the java
thread stack traces? Should give some indication about what's
happening during your slow shutdown...
I can't even get the server to start up with the new Jetty. There
appear to be some interface changes that still need to be
accounted for (working on a potential fix). Not much has been
done with the new version yet...the switch was done less than 24
hours ago primarily to see if there are any issues with making the
switch.
Rick
--kevan
--
Shawn
