Re: [BUILD] trunk: Failed for Revision: 1027790
I just deployed the latest openejb snapshot, hope it works. 2010/10/27 Shawn Jiang genspr...@gmail.com 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
Re: [BUILD] branches/2.2: Failed for Revision: 1026529
On Tue, Oct 26, 2010 at 10:27 PM, Kevan Miller kevan.mil...@gmail.comwrote:
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
I can't recreate the failures from build server as well as the failures
above in my local ubuntu.
cd testsuite
mvn clean install -Pit,headless
IIUC, the automated tests are running with:
-Pit,all-subprojects,headless
I can't get all-subprojects to work. It fails with:
IIRC, all-subprojects profile is only used for release.
[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
--
Shawn
[BUILD] trunk: Failed for Revision: 1027840
Geronimo Revision: 1027840 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 18 seconds
[INFO] Finished at: Wed Oct 27 03:39:28 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/20101027/logs-0300-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
[jira] Updated: (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 updated GERONIMO-5661: --- Attachment: G5661.patch pls review it, thanks 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 Attachments: G5661.patch 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] Created: (GERONIMO-5663) Geronimo compatibility with windows 2008
Geronimo compatibility with windows 2008 Key: GERONIMO-5663 URL: https://issues.apache.org/jira/browse/GERONIMO-5663 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: general Affects Versions: 2.0 Reporter: Jean-Jacques Parent Priority: Minor Not a bug but a question Can't find in any documentation if Geronimo 2.0 is compatible with windows 2008- 64 bits. I have already see some issue describing a 64 bit OS but I need to have a confirmation Thanks in advance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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=12925298#action_12925298 ] Shawn Jiang commented on GERONIMO-5661: --- Patch applied to tr...@r1027852. Thanks Viola. Chi RunHua, Could you please verify if this JIRA could be closed ? 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 Attachments: G5661.patch 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] Created: (GERONIMO-5664) Add auto-test to verify Generic Header based authentication support in Geronimo
Add auto-test to verify Generic Header based authentication support in Geronimo --- Key: GERONIMO-5664 URL: https://issues.apache.org/jira/browse/GERONIMO-5664 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: testsuite Affects Versions: 2.1.7 Reporter: LiWenQin Auto test contains properties File Realm and SQL Realm login module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5664) Add auto-test to verify Generic Header based authentication support in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiWenQin updated GERONIMO-5664: --- Attachment: propFileLogin-test.zip Add auto-test to verify Generic Header based authentication support in Geronimo --- Key: GERONIMO-5664 URL: https://issues.apache.org/jira/browse/GERONIMO-5664 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: testsuite Affects Versions: 2.1.7 Reporter: LiWenQin Attachments: propFileLogin-test.zip Auto test contains properties File Realm and SQL Realm login module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: slow jetty shutdown
Many thanks to both of you!
I tried to apply Shawn's trick, but it gives me a nullpointer:
# java.lang.NullPointerException
#at
org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:447)
#at
org.eclipse.jetty.io.nio.SelectorManager.doStop(SelectorManager.java:254)
I tried to return before this happens, but that results in the same slow
shutdown. The same goes for calling doSelect() before stop().
I've noticed that Jetty logs the following warning on startup:
# Acceptors should be =2*availableProcessors
Geronimo applies the maxThreads parameter as the number of acceptor threads
in Jetty, and I believe the default value of 50 is way too high. I've tried
using 4 on my system, and this makes shutdowns much faster (12 seconds vs.
104 seconds with Maven). This is still slow though.
I've noticed that the Jetty Acceptor thread calls the same close method in
SelectChannelConnector that is already called from the doStop method in
AbstractConnector when the server is stopping. This seems strange to me, but
disabling it had no effect.
Trygve
On Wed, Oct 27, 2010 at 7:15 AM, Shawn Jiang genspr...@gmail.com wrote:
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.commailto:
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
[BUILD] trunk: Failed for Revision: 1027950
Geronimo Revision: 1027950 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 42 seconds
[INFO] Finished at: Wed Oct 27 09:42:09 EDT 2010
[INFO] Final Memory: 477M/1009M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027/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 Wed, Oct 27, 2010 at 3:22 PM, Trygve Sanne Hardersen wrote: I've noticed that Jetty logs the following warning on startup: # Acceptors should be =2*availableProcessors Geronimo applies the maxThreads parameter as the number of acceptor threads in Jetty, and I believe the default value of 50 is way too high. I've tried using 4 on my system, and this makes shutdowns much faster (12 seconds vs. 104 seconds with Maven). This is still slow though. I have attached a patch that sets the number of acceptor threads to 2 per connector, and exposes this as well as the acceptor queue size to the config-substitutions.properties file. Jetty standalone uses 2 acceptor threads by default, and with these settings the server shutdown is pretty fast. I also believe they are more correct, and they remove the startup warning mentioned above. I did not find a way to use separate settings for the HTTP, HTTPS and AJP connectors. I believe that requires separate parameter names. Thanks! Trygve geronimo-2.2-1027647-jetty-acceptors.patch Description: Binary data
[BUILD] trunk: Failed for Revision: 1028073
Geronimo Revision: 1028073 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027/unit-test-reports codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=3.0-SNAPSHOT -Dpackaging=maven-plugin -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.buildsupport -DartifactId=car-maven-plugin -Dversion=3.0-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:178) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=3.0-SNAPSHOT -Dpackaging=maven-plugin -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.buildsupport -DartifactId=car-maven-plugin -Dversion=3.0-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:253) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184) at org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1626
[BUILD] branches/2.2: Failed for Revision: 1028050
Geronimo Revision: 1028050 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101027/build-1400.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20101027 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 37 minutes 31 seconds [INFO] Finished at: Wed Oct 27 14:44:55 EDT 2010 [INFO] Final Memory: 307M/968M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101027/logs-1400-tomcat/ [INFO] Running TestSuite [INFO] Tests run: 40, Failures: 16, Errors: 0, Skipped: 0, Time elapsed: 233.052 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 67.516 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 69.386 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101027/logs-1400-jetty/ [INFO] Running TestSuite [INFO] Tests run: 116, Failures: 3, Errors: 0, Skipped: 113, Time elapsed: 15.874 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 8, Errors: 0, Skipped: 0, Time elapsed: 93.911 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.672 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.833 sec FAILURE! Samples: branches/2.2 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.2/20101027/samples-1400.log Build status: FAILED
jcdi/owb progress
I've been working steadily on the OWB integration. I just found what appears to be the current exclusion list at http://fisheye.jboss.org/browse/~raw,r=7045/weld/cdi-tck/branches/1.0/impl/src/main/resources/tck-tests-released.xml and copied it into our jcdi tck-tests.xml. Running with my patched OWB and current openejb and geronimo I get 9 failures. 5 of these appear to be EL related, and at least one is because we aren't binding BeanManager into jndi yet. Hopefully I've opened jiras w/patches for all the OWB changes... thanks david jencks
[jira] Created: (GERONIMO-5665) destoryInternal method is called twice while destorying the children directly
destoryInternal method is called twice while destorying the children directly - Key: GERONIMO-5665 URL: https://issues.apache.org/jira/browse/GERONIMO-5665 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 This is a bug in Tomcat, it called the destoryInternal method twice while destorying the children directly, which causes some exceptions while shutdowning the server, e.g. the mbean is not found. -- 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: 1028157
Geronimo Revision: 1028157 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 39 minutes 58 seconds
[INFO] Finished at: Wed Oct 27 21:41:12 EDT 2010
[INFO] Final Memory: 479M/1006M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101027/logs-2100-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
[jira] Assigned: (GERONIMO-5302) A successfully deployed war package(contained in a ear package) is not listed on admin console.
[ https://issues.apache.org/jira/browse/GERONIMO-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang reassigned GERONIMO-5302: --- Assignee: Han Hong Fang A successfully deployed war package(contained in a ear package) is not listed on admin console. --- Key: GERONIMO-5302 URL: https://issues.apache.org/jira/browse/GERONIMO-5302 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: OS:WIN XP GERONIMO Build:3.0 SNAPSHOT 2010.5.6 build JDK:1.6 Reporter: Lu Jiang Assignee: Han Hong Fang Attachments: sendmail-ear-2.1.1.4.ear Sendmail-ear.ear can be successfully deployed on geronimo 3.0 snapshot. Open http://localhost:8080/sendmail/ in a web browser ,this application works fine. But As far as I can remember if the ear contains a war package and this war package is specifiled in application .xml like: module web web-urisendmail-war-2.1.1.4.war/web-uri context-root/sendmail/context-root /web /module Then on admin console,under Console Navigation/Applicatios,click web App Wars,it/s expected to see an item like this: org.apache.geronimo.samples/sendmail-ear_sendmail-war-2.1.1.4.war/2.1.1/car /sendmail running StopRestart Uninstall then we can get access to the application via the link /sendmail. But currently on 3.0 snapshot console,the deployed war will not be listed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5582) No Ｗeb Access URL Displayed next to applications after depploy an EBA
[ https://issues.apache.org/jira/browse/GERONIMO-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang reassigned GERONIMO-5582: --- Assignee: Han Hong Fang No Ｗeb Access URL Displayed next to applications after depploy an EBA - Key: GERONIMO-5582 URL: https://issues.apache.org/jira/browse/GERONIMO-5582 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: OS: WinXp JDK: 1.6.0_21 Reporter: viola.lu Assignee: Han Hong Fang Fix For: 3.0 1.Deploy Aries Sample JPA EBA in testsuite/Aries-Testsuite/JPA or blog sample org.apache.aries.samples.blog.jdbc.eba-0.2-incubating-SNAPSHOT.eba from Aries source code 2.It's successfully deployed, but no Access URL is display next to application, have to open web jar file, open its manifest file, getting Web-ContextPath: /blog, and then access this application:http://localhost:8080/blog/ViewBlog or http://localhost:8080/jpa -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5665) destoryInternal method is called twice while destorying the children directly
[ https://issues.apache.org/jira/browse/GERONIMO-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12925663#action_12925663 ] Ivan commented on GERONIMO-5665: Open a Bugzilla entry https://issues.apache.org/bugzilla/show_bug.cgi?id=50168 destoryInternal method is called twice while destorying the children directly - Key: GERONIMO-5665 URL: https://issues.apache.org/jira/browse/GERONIMO-5665 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 This is a bug in Tomcat, it called the destoryInternal method twice while destorying the children directly, which causes some exceptions while shutdowning the server, e.g. the mbean is not found. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (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 updated GERONIMO-5661: --- Attachment: G5661_ALL.patch I find out that deploy, client have the same problem, so update all files. Pls apply it.Thanks. 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 Attachments: G5661.patch, G5661_ALL.patch 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] 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=12925679#action_12925679 ] Shawn Jiang commented on GERONIMO-5661: --- Thanks Viola, the additional patch was applied in tr...@r1028173 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 Attachments: G5661.patch, G5661_ALL.patch 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] Created: (GERONIMO-5666) Add test cases for Restful Web Service new features into the testsuite.
Add test cases for Restful Web Service new features into the testsuite. --- Key: GERONIMO-5666 URL: https://issues.apache.org/jira/browse/GERONIMO-5666 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: testsuite Affects Versions: 3.0 Reporter: Wang Guang Zhe Fix For: 3.0 Java API for RESTful Web Services (JAX-RS) 1.1, which is JSR-311,is a new part in Java EE 6.This testsuite includes its basic functions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5561) Scan ManagedBean in the application to support EJB injection
[ https://issues.apache.org/jira/browse/GERONIMO-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12925696#action_12925696 ] Ivan commented on GERONIMO-5561: Commit first step changes to trunk at revision: 1028188, need to update once we begun to use 2.0.3-SNAPSHOT. Scan ManagedBean in the application to support EJB injection Key: GERONIMO-5561 URL: https://issues.apache.org/jira/browse/GERONIMO-5561 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: myfaces Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 In JSF 2.0, we could use ManagedBean annotation to create a JSF managed bean, so we need to scan all the managed beans in the deployment process, then we could create local naming context for the target bean. In the meanwhile, we could avoid annotation scan in the starting time. -- 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 Wed, Oct 27, 2010 at 7:58 AM, Jay D. McHugh jaydmch...@gmail.com wrote: 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 -- Best Regards, Delos
