date:20091012

Geronimo Revision: 824545 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091012/build-2000.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091012/unit-test-reports
 
190K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//commons-pool/commons-pool/1.4/commons-pool-1.4.jar
Downloading: 
http://oss.sonatype.org/content/repositories/jetty-with-staging//commons-pool/commons-pool/1.4/commons-pool-1.4.jar
Downloading: 
http://repo.exist.com/maven2/commons-pool/commons-pool/1.4/commons-pool-1.4.jar
85K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//org/springframework/spring-context-support/2.5.6/spring-context-support-2.5.6.jar
Downloading: 
http://oss.sonatype.org/content/repositories/jetty-with-staging//org/springframework/spring-context-support/2.5.6/spring-context-support-2.5.6.jar
Downloading: 
http://repo.exist.com/maven2/org/springframework/spring-context-support/2.5.6/spring-context-support-2.5.6.jar
94K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//org/apache/activemq/activemq-pool/5.3.0/activemq-pool-5.3.0.jar
37K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//rome/rome/0.8/rome-0.8.jar
Downloading: 
http://oss.sonatype.org/content/repositories/jetty-with-staging//rome/rome/0.8/rome-0.8.jar
Downloading: http://repo.exist.com/maven2/rome/rome/0.8/rome-0.8.jar
192K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//org/springframework/spring-webmvc/2.5.6/spring-webmvc-2.5.6.jar
Downloading: 
http://oss.sonatype.org/content/repositories/jetty-with-staging//org/springframework/spring-webmvc/2.5.6/spring-webmvc-2.5.6.jar
Downloading: 
http://repo.exist.com/maven2/org/springframework/spring-webmvc/2.5.6/spring-webmvc-2.5.6.jar
392K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//xmlpull/xmlpull/1.1.3.4d_b4_min/xmlpull-1.1.3.4d_b4_min.jar
Downloading: 
http://oss.sonatype.org/content/repositories/jetty-with-staging//xmlpull/xmlpull/1.1.3.4d_b4_min/xmlpull-1.1.3.4d_b4_min.jar
Downloading: 
http://repo.exist.com/maven2/xmlpull/xmlpull/1.1.3.4d_b4_min/xmlpull-1.1.3.4d_b4_min.jar
23K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//org/apache/activemq/activemq-xmpp/5.3.0/activemq-xmpp-5.3.0.jar
171K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
Downloading: 
http://oss.sonatype.org/content/repositories/jetty-with-staging//jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
Downloading: 
http://download.java.net/maven/2/jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
Downloading: 
http://repository.codehaus.org//jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
Downloading: 
http://repo.exist.com/maven2/jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
502K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//jivesoftware/smack/3.1.0/smack-3.1.0.jar
Downloading: 
http://oss.sonatype.org/content/repositories/jetty-with-staging//jivesoftware/smack/3.1.0/smack-3.1.0.jar
Downloading: 
http://repo.exist.com/maven2/jivesoftware/smack/3.1.0/smack-3.1.0.jar
278K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//org/apache/activemq/activemq-console/5.3.0/activemq-console-5.3.0.jar
85K downloaded
Downloading: 
https://repository.apache.org/content/repositories/releases//opensymphony/sitemesh/2.2.1/sitemesh-2.2.1.jar
Downloading: 
http://oss.sonatype.org/content/repositories/jetty-with-staging//opensymphony/sitemesh/2.2.1/sitemesh-2.2.1.jar
Downloading: 
http://repo.exist.com/maven2/opensymphony/sitemesh/2.2.1/sitemesh-2.2.1.jar
130K downloaded
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/activemq/activemq-webconsole-jetty/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/activemq/activemq-webconsole-jetty/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@efe0efe
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@efe0efe
[INFO] Generated: 
/home/geronimo/geronimo/2.2/plugins/activemq/activemq-webconsole-jetty/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[WARNING] Component returned which is not the same manager. Ignored.

[BUILD] trunk: Failed for Revision: 824456

Geronimo Revision: 824456 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012/unit-test-reports
 

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-008/)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-008/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java: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.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-008/)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java

More OSGi progress

Time to start a new thread, I think.  I'm getting further now.  The 
framework builds, but I'm getting errors trying to build the configs.  I 
get an IOException attempting to build the J2EE System config (see 
below).  The file in question is


java.io.IOException: Referenced file does not exist: 
C:\jencks\g\framework\confi

gs\j2ee-system\target\repository\org\apache\geronimo\framework\j2ee-system\3.0-S
NAPSHOT\j2ee-system-3.0-SNAPSHOT.car

which actually does exist.  Strangely, this does not kill the build, but 
it then dies trying to build the rmi-naming config with a similar error 
trying to load the rmi-naming car file.  This one does kill the build.  
Both exceptions occur when starting the Felix framework, but I'm not 
sure where the reference to that file is coming from.  Any suggestions 
on where I might start debugging this problem?


Rick

[INFO] [car:update-pluginlist]
[INFO] 


[INFO] Building Geronimo Framework, Configs :: J2EE System
[INFO]task-segment: [install]
[INFO] 


[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 
C:\jencks\g\framework\configs\j2ee-sy

stem\src\main\filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated: 
C:\jencks\g\framework\configs\j2ee-system\target\work\plan.xml


[INFO] [car:verify-no-dependency-change]
[INFO] [car:prepare-metadata]
[INFO] [car:package]
[INFO] Packaging module configuration: 
C:\jencks\g\framework\configs\j2ee-system

\target\work\plan.xml
ERROR: Error creating archive. (java.io.IOException: Referenced file 
does not ex
ist: 
C:\jencks\g\framework\configs\j2ee-system\target\repository\org\apache\gero

nimo\framework\j2ee-system\3.0-SNAPSHOT\j2ee-system-3.0-SNAPSHOT.car)
java.io.IOException: Referenced file does not exist: 
C:\jencks\g\framework\confi

gs\j2ee-system\target\repository\org\apache\geronimo\framework\j2ee-system\3.0-S
NAPSHOT\j2ee-system-3.0-SNAPSHOT.car
   at 
org.apache.felix.framework.cache.BundleArchive.createRevisionFromLoca

tion(BundleArchive.java:994)
   at 
org.apache.felix.framework.cache.BundleArchive.revise(BundleArchive.j

ava:631)
   at 
org.apache.felix.framework.cache.BundleArchive.(BundleArchive.j

ava:206)
   at 
org.apache.felix.framework.cache.BundleCache.getArchives(BundleCache.

java:149)
   at org.apache.felix.framework.Felix.init(Felix.java:558)
   at org.apache.felix.framework.Felix.start(Felix.java:683)
   at 
org.apache.geronimo.mavenplugins.car.AbstractCarMojo.getFramework(Abs

tractCarMojo.java:771)
   at 
org.apache.geronimo.mavenplugins.car.PackageMojo.createKernel(Package

Mojo.java:360)
   at 
org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(Package

Mojo.java:294)
   at 
org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.

java:234)
   at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi

nManager.java:453)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa

ultLifecycleExecutor.java:559)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi

fecycle(DefaultLifecycleExecutor.java:500)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau

ltLifecycleExecutor.java:479)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan

dleFailures(DefaultLifecycleExecutor.java:331)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen

ts(DefaultLifecycleExecutor.java:292)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi

fecycleExecutor.java:142)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.

java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

sorImpl.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)
ERROR: Error starting 
reference:file://c:\.m2\repository\org\apache\geronimo\fra

mework\geronimo-gbean-deployer

[BUILD] trunk: Failed for Revision: 824322

Geronimo Revision: 824322 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 320 minutes 18 seconds
[INFO] Finished at: Mon Oct 12 14:23:16 EDT 2009
[INFO] Final Memory: 1343M/1536M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012/logs-0900-tomcat/
 
 
[INFO] Scanning for projects...
[INFO] 
[INFO] Building Geronimo TestSuite
[INFO]task-segment: [install]
[INFO] 
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/selenium-maven-plugin/1.0-rc-1/selenium-maven-plugin-1.0-rc-1.pom
21K downloaded
Downloading: 
http://nexus.openqa.org/content/repositories/releases/org/codehaus/mojo/mojo-parent/19/mojo-parent-19.pom
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/mojo-parent/19/mojo-parent-19.pom
17K downloaded
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/selenium-maven-plugin/1.0-rc-1/selenium-maven-plugin-1.0-rc-1.jar
60K downloaded
[INFO] snapshot org.apache.geronimo.buildsupport:buildsupport:3.0-SNAPSHOT: 
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.buildsupport:buildsupport:3.0-SNAPSHOT: 
checking for updates from codehaus.snapshots
[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
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/shitty-maven-plugin/1.0-alpha-3/shitty-maven-plugin-1.0-alpha-3.pom
16K downloaded
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/shitty-maven-plugin/1.0-alpha-3/shitty-maven-plugin-1.0-alpha-3.jar
106K downloaded
[INFO] [genesis:validate-configuration {execution: default}]
[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 openqa-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 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 openqa-snapshots
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion failed 
with message:
Detected JDK Version: 1.5.0-18 is not in the allowed range [1.6,).
[INFO] 
[ERROR] BUILD ERROR
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012/logs-0900-jetty/
 
 
[INFO] Scanning for projects...
[INFO] 
[INFO] Building Geronimo TestSuite
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion failed 
with message:
Detected JDK Version: 1.5.0-18 is not in the allowed range [1.6,).
[INFO] 
[ERROR] BUILD ERROR
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries

[BUILD] branches/2.2: Failed for Revision: 824442

Geronimo Revision: 824442 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091012/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091012/unit-test-reports
 

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-008/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  jetty-staging 
(http://oss.sonatype.org/content/repositories/jetty-with-staging/)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-008/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  jetty-staging 
(http://oss.sonatype.org/content/repositories/jetty-with-staging/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-008/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  jetty-staging 
(http://oss.sonatype.org/content/repositories/jetty-with-staging/)


at

Re: Building only an assembly and what changed

2009-10-12 Thread Quintin Beukes

Hey,

Yes. I do build the kernel before the boilerplate, and that does help
get it into the boilerplate. Thanks.

Though, let me rephrase. I'm missing what step is needed to get the
assembly to use the new geronimo-kernel.jar, because it doesn't seem
to take it even if the boilerplate's .car file has my changes in it
(ie. 
framework/configs/geronimo-boilerplate/target/geronimo-boilerplate-2.2-SNAPSHOT.car
or something). I can get this right with an "mvn clean install",
though that seem redundant as well since there has to be a way to do
an incremental build when changing only certain parts of the code.

Quintin Beukes



On Mon, Oct 12, 2009 at 8:42 AM, Ivan  wrote:
> While compiling the geronimo-kernel module, do you run it with "mvn
> install", so that the geronimo-kernel jar file could be installed to the
> local repository. Or geronimo-boilerplate module could not package the
> latest jar file.
> Wish it helps !
>
> 2009/10/11 Quintin Beukes 
>>
>> I eventually settled on copying the geronimo-kernel JAR to an
>> extracted assembly.
>>
>> When I check the boilerplate/target/contents/lib/geronimo-kernel JAR,
>> it DOES have my code, in fact, that's the one I copied into my
>> extracted assembly.
>>
>> But I looked throughout the documentation, and tried reading the POMs
>> but can't find a way to build it other than a complete "mvn clean
>> install", which takes ages.
>>
>> I also tried doing a a -Dstage=assembly, which didn't help either.
>>
>> Would still like to know of a way to construct a clean assembly after
>> making change to the kernel.
>>
>> Quintin Beukes
>>
>>
>>
>> On Sun, Oct 11, 2009 at 1:25 PM, Quintin Beukes 
>> wrote:
>> > I'm doing something wrong, or there is another step.
>> >
>> > I rebuild the boilerplate config, and check in it's target/ directory
>> > inside the boilerplate car archive. My changed class is there, with
>> > the changes.
>> >
>> > Then I "cd {buildroot}/assemblies/geronimo-jetty7-javaee" and do "mvn
>> > install". It builds the assembly, but the ZIP it builds doesn't
>> > contain the boilerplate I just build.
>> >
>> > Quintin Beukes
>> >
>> >
>> >
>> > On Fri, Oct 9, 2009 at 7:06 PM, David Jencks 
>> > wrote:
>> >>
>> >> On Oct 9, 2009, at 7:55 AM, Quintin Beukes wrote:
>> >>
>> >>> Hey,
>> >>>
>> >>> Assume I change a .java file in the framework/modules/geronimo-kernel
>> >>> project, how can I easily only build what was changed and reassemble
>> >>> the zip for installing+running?
>> >>
>> >> There a few modules that are not put into the geronimo repository
>> >> structure
>> >> -- geronimo-kernel, geronimo-system, and a few others.  For these you
>> >> have
>> >> to rebuild the framework/configs/geronimo-boilerplate config before
>> >> rebuilding the assembly you want.
>> >>
>> >> Also, if you change anything related to a GBeanInfo -- for instance
>> >> attributes, operations, constructor parameters -- you have to rebuild
>> >> any
>> >> configs that might use that gbean.
>> >>
>> >> Otherwise, if you change code you can just rebuild the module and
>> >> rebuild
>> >> the assembly.  Or, if you want to live dangerously, you can just copy
>> >> the
>> >> new jar over the old one in the geronimo repo.
>> >>
>> >> thanks
>> >> david jencks
>> >>
>> >>>
>> >>> Quintin Beukes
>> >>
>> >>
>> >
>
>
>
> --
> Ivan
>

David Jencks wrote:
I think this particular problem is caused by running on windows. In
MockBundleContext just before this line I manipulate the location to
remove cruft from the beginning. I think we need to add some more
tests to remove windows specific cruft. Since I don't have a windows
machine I'm not sure how to find out exactly what needs to be
changed debugging and finding out what is in the locations map
should provide a big hint.
Ok, I've checked in a fix for this. The setup code for the test was
assuming that dir.getAbsolutePath().substring(1) would just chop off the
root dir delimiter. On Windows, that cut off the drive letter,
resulting in a location of ":\yada\yada\" getting stored in
location. The MockBundleContext install() was correctly using
"C:\yada\yada\...", and not finding it. The deployment tests now run
cleanly, on to the next problem :-)

Rick

thanks
david jencks

On Oct 12, 2009, at 5:36 AM, Rick McGuire wrote:

David Jencks wrote:

I only have a minute so can't address anything in detail right now.

Most of the servicemix bundle dependencies can probably be on
released versions. I went for speed and used the ones from my
checked out servicemix trunk in case I needed to patch them.

I don't think we need the geronimo plexus bundles I set up --
although we do need to find some solution for accessing the code or
not using it at all.

What are the testsuite errors you get? It would be useful to find
out if they are windows specific. Similarly it would be great to
find out if anyone else can build on a non-windows system :-)
I took a little deeper look at the deployment test case errors I'm
getting. The root cause of the failure is this exception:

Caused by: java.lang.IllegalArgumentException: id must be in the form
[groupId]/[artifactId]/[version]/[type] :
C:\jencks\g\framework\modules\geronimo-deployment\target\deployTest
at
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:61)
at
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:51)
at
org.apache.geronimo.kernel.osgi.MockBundleContext.installBundle(MockBundleContext.java:106)

at
org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:208)

... 28 more

Since this is failing just calling bundleContext.installBundle() in
the MockBundleContext code, I suspect I'm not running under karaf.
Have I missed some setup step somewhere?

Rick

thanks
david jencks

On Oct 9, 2009, at 4:55 AM, Rick McGuire wrote:

David Jencks wrote:
I changed the url scheme so we always use pax maven urls for
everything in the geronimo repository, and now I can get, with
some work, all the plugin bundles to start as bundles. However
they mostly don't start as plugins (i.e., no gbeans start). I
haven't figured out why yet.

How to get it to "run":

build
This one word is starting to remind me of the famous Sydney Harris
cartoon:

http://www.sciencecartoonsplus.com/pages/gallery.php

I've had a few issues getting this to build, so I thought I'd
capture the notes here for the benefit of others. Some of these we
can fix in the build, others are things that need to be accounted
for before building. A major problem is getting all of the
dependencies into your maven repository so the build can work.

1) servicemix bundles. In addition to the patch that David
provided, you need to checkout and build the servicemix bundles from:

https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk

Unfortunately, the root pom for servicemix does not build all of
the subprojects. Many of the ones that are skipped are required by
Geronimo and need to be built individually. This list includes:

jaxb-impl-2.1.6
xmlbeans-2.4.0 (NOTE: this builds 2.4.0_3-SNAPSHOT, but the
dependency is currently 2.4.0_2-SNAPSHOT. The Geronimo pom needs
to be adjusted).

woodstox-3.2.8
jline-0.9.94

The framework builds additional bundlized versions of dependencies,
but at the moment, they are not included in the build. The
subprojects are located in framework/bundles, but there's no root
pom that builds all of these, so each subproject needs to be built
individually. There are some dependencies between these
subprojects. For example, plexus-archiver depends on plexus-utils,
so plexus-utils needs to be built first. Unfortunately,
plexus-utils is building version 1.5.15_1-SNAPSHOT, and
plexus-archiver has a dependency on 1.4.5_-SNAPSHOT. plexus-utils
exports a 1.4.5 level of the packages, so I'm guessing this was
intended to be 1.4.5_1-SNAPSHOT, so the POM needs adjusting.

Once I've done the steps above, I get some test failures in
geronimo-kernel. If I try to build with tests turned off, then I
get the following failure:

1)
org.apache.geronimo.framework:geronimo-kernel:jar:tests:3.0-SNAPSHOT

Try downloading the file manually from the project website.

Then, install it using the

Re: osgi progress

Ok, I was just in the process of doing that very debugging.

Rick

thanks
david jencks

On Oct 12, 2009, at 5:36 AM, Rick McGuire wrote:

David Jencks wrote:

I only have a minute so can't address anything in detail right now.

Most of the servicemix bundle dependencies can probably be on
released versions. I went for speed and used the ones from my
checked out servicemix trunk in case I needed to patch them.

I don't think we need the geronimo plexus bundles I set up --
although we do need to find some solution for accessing the code or
not using it at all.

at
org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:208)

... 28 more

Since this is failing just calling bundleContext.installBundle() in
the MockBundleContext code, I suspect I'm not running under karaf.
Have I missed some setup step somewhere?

Rick

thanks
david jencks

On Oct 9, 2009, at 4:55 AM, Rick McGuire wrote:

How to get it to "run":

build
This one word is starting to remind me of the famous Sydney Harris
cartoon:

http://www.sciencecartoonsplus.com/pages/gallery.php

1) servicemix bundles. In addition to the patch that David
provided, you need to checkout and build the servicemix bundles from:

https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk

Unfortunately, the root pom for servicemix does not build all of
the subprojects. Many of the ones that are skipped are required by
Geronimo and need to be built individually. This list includes:

jaxb-impl-2.1.6
xmlbeans-2.4.0 (NOTE: this builds 2.4.0_3-SNAPSHOT, but the
dependency is currently 2.4.0_2-SNAPSHOT. The Geronimo pom needs
to be adjusted).

woodstox-3.2.8
jline-0.9.94

Once I've done the steps above, I get some test failures in
geronimo-kernel. If I try to build with tests turned off, then I
get the following failure:

1)
org.apache.geronimo.framework:geronimo-kernel:jar:tests:3.0-SNAPSHOT

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.framework
-Dartifac
tId=geronimo-kernel -Dversion=3.0-SNAPSHOT -Dclassifier=tests
-Dpackaging=jar -D

file=/path/to/file

most likely the result of the test failures. The test failures
don't make much sense to me, but this might be a Windows-specific
problem with normalizing URLs. If I comment out the assert

Re: osgi progress

2009-10-12 Thread David Jencks

I think this particular problem is caused by running on windows.  In  
MockBundleContext just before this line I manipulate the location to  
remove cruft from the beginning.  I think we need to add some more  
tests to remove windows specific cruft.  Since I don't have a windows  
machine I'm not sure how to find out exactly what needs to be  
changed debugging and finding out what is in the locations map  
should provide a big hint.


thanks
david jencks

On Oct 12, 2009, at 5:36 AM, Rick McGuire wrote:


David Jencks wrote:

I only have a minute so can't address anything in detail right now.

Most of the servicemix bundle dependencies can probably be on  
released versions.  I went for speed and used the ones from my  
checked out servicemix trunk in case I needed to patch them.


I don't think we need the geronimo plexus bundles I set up --  
although we do need to find some solution for accessing the code or  
not using it at all.


What are the testsuite errors you get?  It would be useful to find  
out if they are windows specific.  Similarly it would be great to  
find out if anyone else can build on a non-windows system :-)
I took a little deeper look at the deployment test case errors I'm  
getting.  The root cause of the failure is this exception:


Caused by: java.lang.IllegalArgumentException: id must be in the  
form [groupId]/[artifactId]/[version]/[type] : C:\jencks\g\framework 
\modules\geronimo-deployment\target\deployTest
  at  
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java: 
61)
  at  
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java: 
51)
  at  
org 
.apache 
.geronimo 
.kernel.osgi.MockBundleContext.installBundle(MockBundleContext.java: 
106)
  at  
org 
.apache 
.geronimo 
.deployment 
.DeploymentContext.createTempConfiguration(DeploymentContext.java:208)

  ... 28 more


Since this is failing just calling bundleContext.installBundle() in  
the MockBundleContext code, I suspect I'm not running under karaf.   
Have I missed some setup step somewhere?


Rick



thanks
david jencks

On Oct 9, 2009, at 4:55 AM, Rick McGuire wrote:


David Jencks wrote:
I changed the url scheme so we always use pax maven urls for  
everything in the geronimo repository, and now I can get, with  
some work, all the plugin bundles to start as bundles.  However  
they mostly don't start as plugins (i.e., no gbeans start).  I  
haven't figured out why yet.


How to get it to "run":

build
This one word is starting to remind me of the famous Sydney Harris  
cartoon:


http://www.sciencecartoonsplus.com/pages/gallery.php

I've had a few issues getting this to build, so I thought I'd  
capture the notes here for the benefit of others.  Some of these  
we can fix in the build, others are things that need to be  
accounted for before building.  A major problem is getting all of  
the dependencies into your maven repository so the build can work.


1)  servicemix bundles.  In addition to the patch that David  
provided, you need to checkout and build the servicemix bundles  
from:


https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk

Unfortunately, the root pom for servicemix does not build all of  
the subprojects.  Many of the ones that are skipped are required  
by Geronimo and need to be built individually.  This list includes:


jaxb-impl-2.1.6
xmlbeans-2.4.0  (NOTE:  this builds 2.4.0_3-SNAPSHOT, but the  
dependency is currently 2.4.0_2-SNAPSHOT.  The Geronimo pom needs  
to be adjusted).

woodstox-3.2.8
jline-0.9.94

The framework builds additional bundlized versions of  
dependencies, but at the moment, they are not included in the  
build.  The subprojects are located in framework/bundles, but  
there's no root pom that builds all of these, so each subproject  
needs to be built individually.  There are some dependencies  
between these subprojects.  For example, plexus-archiver depends  
on plexus-utils, so plexus-utils needs to be built first.   
Unfortunately, plexus-utils is building version 1.5.15_1-SNAPSHOT,  
and plexus-archiver has a dependency on 1.4.5_-SNAPSHOT.  plexus- 
utils exports a 1.4.5 level of the packages, so I'm guessing this  
was intended to be 1.4.5_1-SNAPSHOT, so the POM needs adjusting.


Once I've done the steps above, I get some test failures in  
geronimo-kernel.  If I try to build with tests turned off, then I  
get the following failure:


1) org.apache.geronimo.framework:geronimo-kernel:jar:tests:3.0- 
SNAPSHOT


Try downloading the file manually from the project website.

Then, install it using the command:
   mvn install:install-file - 
DgroupId=org.apache.geronimo.framework -Dartifac
tId=geronimo-kernel -Dversion=3.0-SNAPSHOT -Dclassifier=tests - 
Dpackaging=jar -D

file=/path/to/file

most likely the result of the test failures.   The test failures  
don't make much sense to me, but this might be a Windows-specific  
problem with normalizing URLs.  If I comment out the assertions  
that are fai

Re: osgi progress

2009-10-12 Thread David Jencks



On Oct 12, 2009, at 5:36 AM, Rick McGuire wrote:


David Jencks wrote:

I only have a minute so can't address anything in detail right now.

Most of the servicemix bundle dependencies can probably be on  
released versions.  I went for speed and used the ones from my  
checked out servicemix trunk in case I needed to patch them.


I don't think we need the geronimo plexus bundles I set up --  
although we do need to find some solution for accessing the code or  
not using it at all.


What are the testsuite errors you get?  It would be useful to find  
out if they are windows specific.  Similarly it would be great to  
find out if anyone else can build on a non-windows system :-)
I took a little deeper look at the deployment test case errors I'm  
getting.  The root cause of the failure is this exception:


Caused by: java.lang.IllegalArgumentException: id must be in the  
form [groupId]/[artifactId]/[version]/[type] : C:\jencks\g\framework 
\modules\geronimo-deployment\target\deployTest
  at  
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java: 
61)
  at  
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java: 
51)
  at  
org 
.apache 
.geronimo 
.kernel.osgi.MockBundleContext.installBundle(MockBundleContext.java: 
106)
  at  
org 
.apache 
.geronimo 
.deployment 
.DeploymentContext.createTempConfiguration(DeploymentContext.java:208)

  ... 28 more


Since this is failing just calling bundleContext.installBundle() in  
the MockBundleContext code, I suspect I'm not running under karaf.   
Have I missed some setup step somewhere?


Karaf is not used during the build: the car-maven-plugin fires up  
felix and attempts to let all the classes known to the maven plugin be  
exposed from the felix framework.


I don't see why this error would be occurring but another task I think  
I forgot to mention would be using the ops4j maven urls in the build  
to load bundles rather than the file system locations I'm  
constructing.  This might sidestep the problem you are seeing.  I  
really don't understand how you could get it and me not see it


thanks
david jencks



Rick



thanks
david jencks

On Oct 9, 2009, at 4:55 AM, Rick McGuire wrote:


David Jencks wrote:
I changed the url scheme so we always use pax maven urls for  
everything in the geronimo repository, and now I can get, with  
some work, all the plugin bundles to start as bundles.  However  
they mostly don't start as plugins (i.e., no gbeans start).  I  
haven't figured out why yet.


How to get it to "run":

build
This one word is starting to remind me of the famous Sydney Harris  
cartoon:


http://www.sciencecartoonsplus.com/pages/gallery.php

I've had a few issues getting this to build, so I thought I'd  
capture the notes here for the benefit of others.  Some of these  
we can fix in the build, others are things that need to be  
accounted for before building.  A major problem is getting all of  
the dependencies into your maven repository so the build can work.


1)  servicemix bundles.  In addition to the patch that David  
provided, you need to checkout and build the servicemix bundles  
from:


https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk

Unfortunately, the root pom for servicemix does not build all of  
the subprojects.  Many of the ones that are skipped are required  
by Geronimo and need to be built individually.  This list includes:


jaxb-impl-2.1.6
xmlbeans-2.4.0  (NOTE:  this builds 2.4.0_3-SNAPSHOT, but the  
dependency is currently 2.4.0_2-SNAPSHOT.  The Geronimo pom needs  
to be adjusted).

woodstox-3.2.8
jline-0.9.94

The framework builds additional bundlized versions of  
dependencies, but at the moment, they are not included in the  
build.  The subprojects are located in framework/bundles, but  
there's no root pom that builds all of these, so each subproject  
needs to be built individually.  There are some dependencies  
between these subprojects.  For example, plexus-archiver depends  
on plexus-utils, so plexus-utils needs to be built first.   
Unfortunately, plexus-utils is building version 1.5.15_1-SNAPSHOT,  
and plexus-archiver has a dependency on 1.4.5_-SNAPSHOT.  plexus- 
utils exports a 1.4.5 level of the packages, so I'm guessing this  
was intended to be 1.4.5_1-SNAPSHOT, so the POM needs adjusting.


Once I've done the steps above, I get some test failures in  
geronimo-kernel.  If I try to build with tests turned off, then I  
get the following failure:


1) org.apache.geronimo.framework:geronimo-kernel:jar:tests:3.0- 
SNAPSHOT


Try downloading the file manually from the project website.

Then, install it using the command:
   mvn install:install-file - 
DgroupId=org.apache.geronimo.framework -Dartifac
tId=geronimo-kernel -Dversion=3.0-SNAPSHOT -Dclassifier=tests - 
Dpackaging=jar -D

file=/path/to/file

most likely the result of the test failures.   The test failures  
don't make much sense to me, but this might be a Windows-specific  
p

[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances


[ 
https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764726#action_12764726
 ] 

Ashish Jain commented on GERONIMO-4795:
---

Please advice if this approach is agreeable.

> Multiple Server Instances: Uninstalling an application does not remove the 
> entry from config.xml of other server instances
> --
>
> Key: GERONIMO-4795
> URL: https://issues.apache.org/jira/browse/GERONIMO-4795
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: commands
>Affects Versions: 2.1.3, 2.1.4
> Environment: Windows XP G 214
>Reporter: Ashish Jain
>Assignee: Ashish Jain
> Fix For: 2.2
>
> Attachments: GERONIMO-4795.patch
>
>
> 1)  Setup another geronimo instance out of the same installation directory.
> 2) Deploy an applicaton to one instance. This will result in entry being 
> created in config.xml for both the instances
> 3) Undeploy the application. This results in entry being removed from 
> config.xml of one instance and other instance 
> still has entry of the application in config.xml.

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

[BUILD] branches/2.2: Failed for Revision: 824305

Geronimo Revision: 824305 built with tests included
 
See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091012/build-0800.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091012
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 57 minutes 27 seconds
[INFO] Finished at: Mon Oct 12 09:03:14 EDT 2009
[INFO] Final Memory: 327M/961M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091012/logs-0800-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091012/logs-0800-jetty/
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/2.2/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:54.026
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:25.223) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:39.551) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:46.200) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:23.722) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:31.669) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:31.702) Java 
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:05.505) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:56.680) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:28.398) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:53.720) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:38.982) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.646) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:40.296) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:54.664) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:22.342) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:49.882) 
[INFO] enterprise-testsuite/sec-client-tests  RUNNING
[INFO] enterprise-testsuite/sec-client-tests  SUCCESS (0:00:35.269) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:58.893) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:59.093) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:37.292) 
[INFO] web-testsuite/test-2.5-servlets

[jira] Updated: (GERONIMO-4903) Jetty Advanced Integration Test Failure

2009-10-12 Thread Donald Woods (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Woods updated GERONIMO-4903:
---

Affects Version/s: 2.2
Fix Version/s: 3.0
 Assignee: Donald Woods

> Jetty Advanced Integration Test Failure
> ---
>
> Key: GERONIMO-4903
> URL: https://issues.apache.org/jira/browse/GERONIMO-4903
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector
>Affects Versions: 2.2
>Reporter: Quintin Beukes
>Assignee: Donald Woods
> Fix For: 2.2, 3.0
>
> Attachments: jetty-advanced-test-failure.patch
>
>
> Hey,
> I found the cause of the test failure.
> In the file: {src
> root}/plugins/jetty7/geronimo-jetty7/./src/main/java/org/apache/geronimo/jetty7/connector/JettyConnector.java
> Line: 289
> It reads: new String[]{"host", "port", "minThreads", "maxThreads",
> "bufferSizeBytes", "headerBufferSizeBytes", "acceptQueueSize",
> "lingerMillis", "protocol", "redirectPort", "connectUrl",
> "maxIdleTimeMs"},
> Change to: new String[]{"host", "port", "minThreads", "maxThreads",
> "bufferSizeBytes", "headerBufferSizeBytes", "acceptQueueSize",
> "lingerMillis", "redirectPort", "maxIdleTimeMs"},
> Basically removing the "protocol" and "connectUrl" attributes from the
> persistent interface attributes fixes the problem.
> "protocol" is static for Jetty BIO connector, so it doesn't need to be
> saved, or can't be specified.
> "connectUrl" is generated on the fly through getConnectUrl(), so can't
> be saved either.
> So unless my understanding of what persistentAttributes are is
> incorrect, this seems to be the correct solution? Please correct me if
> I'm wrong.
> What caused the problem is that the JettyConnector class doesn't have
> a setter for these attributes, so when XBean searches all the
> specified attributes' setters, it fails when it can't find these. This
> caused the test to fail, because the connector doesn't start again
> after being edited (enters the failed state).

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

[jira] Updated: (GERONIMO-4903) Jetty Advanced Integration Test Failure

2009-10-12 Thread Quintin Beukes (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Quintin Beukes updated GERONIMO-4903:
-

Attachment: jetty-advanced-test-failure.patch

attached the patch to fix the issue

> Jetty Advanced Integration Test Failure
> ---
>
> Key: GERONIMO-4903
> URL: https://issues.apache.org/jira/browse/GERONIMO-4903
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector
>Reporter: Quintin Beukes
> Fix For: 2.2
>
> Attachments: jetty-advanced-test-failure.patch
>
>
> Hey,
> I found the cause of the test failure.
> In the file: {src
> root}/plugins/jetty7/geronimo-jetty7/./src/main/java/org/apache/geronimo/jetty7/connector/JettyConnector.java
> Line: 289
> It reads: new String[]{"host", "port", "minThreads", "maxThreads",
> "bufferSizeBytes", "headerBufferSizeBytes", "acceptQueueSize",
> "lingerMillis", "protocol", "redirectPort", "connectUrl",
> "maxIdleTimeMs"},
> Change to: new String[]{"host", "port", "minThreads", "maxThreads",
> "bufferSizeBytes", "headerBufferSizeBytes", "acceptQueueSize",
> "lingerMillis", "redirectPort", "maxIdleTimeMs"},
> Basically removing the "protocol" and "connectUrl" attributes from the
> persistent interface attributes fixes the problem.
> "protocol" is static for Jetty BIO connector, so it doesn't need to be
> saved, or can't be specified.
> "connectUrl" is generated on the fly through getConnectUrl(), so can't
> be saved either.
> So unless my understanding of what persistentAttributes are is
> incorrect, this seems to be the correct solution? Please correct me if
> I'm wrong.
> What caused the problem is that the JettyConnector class doesn't have
> a setter for these attributes, so when XBean searches all the
> specified attributes' setters, it fails when it can't find these. This
> caused the test to fail, because the connector doesn't start again
> after being edited (enters the failed state).

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

[jira] Created: (GERONIMO-4903) Jetty Advanced Integration Test Failure

2009-10-12 Thread Quintin Beukes (JIRA)

Jetty Advanced Integration Test Failure
---

 Key: GERONIMO-4903
 URL: https://issues.apache.org/jira/browse/GERONIMO-4903
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: connector
Reporter: Quintin Beukes
 Fix For: 2.2
 Attachments: jetty-advanced-test-failure.patch

Hey,

I found the cause of the test failure.

In the file: {src
root}/plugins/jetty7/geronimo-jetty7/./src/main/java/org/apache/geronimo/jetty7/connector/JettyConnector.java
Line: 289

It reads: new String[]{"host", "port", "minThreads", "maxThreads",
"bufferSizeBytes", "headerBufferSizeBytes", "acceptQueueSize",
"lingerMillis", "protocol", "redirectPort", "connectUrl",
"maxIdleTimeMs"},
Change to: new String[]{"host", "port", "minThreads", "maxThreads",
"bufferSizeBytes", "headerBufferSizeBytes", "acceptQueueSize",
"lingerMillis", "redirectPort", "maxIdleTimeMs"},

Basically removing the "protocol" and "connectUrl" attributes from the
persistent interface attributes fixes the problem.

"protocol" is static for Jetty BIO connector, so it doesn't need to be
saved, or can't be specified.
"connectUrl" is generated on the fly through getConnectUrl(), so can't
be saved either.

So unless my understanding of what persistentAttributes are is
incorrect, this seems to be the correct solution? Please correct me if
I'm wrong.

What caused the problem is that the JettyConnector class doesn't have
a setter for these attributes, so when XBean searches all the
specified attributes' setters, it fails when it can't find these. This
caused the test to fail, because the connector doesn't start again
after being edited (enters the failed state).


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

Re: using wadi with tomcat & web app in an ear

2009-10-12 Thread Ashish Jain

I think I understand now that the code snippet suggested  by you will help
fix the GBean Not Found exception. Please suggest if this is correct.

However the "Missing Dependency Exception
"org.apache.geronimo.kernel.repository.MissingDependencyException: Missing
dependency: default/ClusterTestEAR/1.0/ear" will be fixed once we are able
to apply the changes as in
 *GERONIMO-4556 *

On Mon, Oct 12, 2009 at 6:58 PM, Ashish Jain  wrote:

> Hi Gianny,
>
> Did you mean that the Missing Dependency Exception will be fixed by the
> code snippet suggested by you. I had build the new jar
> "geronimo-tomcat6-clustering-builder-wadi-2.1.4.jar" and replaced the
> existing one in g214 with this new one. Started two clean instances of g214
> with replaced jars. deployed the application.
>
> The server still throws the Missing Dependency Exception
> "org.apache.geronimo.kernel.repository.MissingDependencyException: Missing
> dependency: default/ClusterTestEAR/1.0/ear".
>
> Please advice.
>
> Thanks
> Ashish
>
>
> On Mon, Oct 12, 2009 at 5:02 PM, Gianny Damour <
> gianny.dam...@optusnet.com.au> wrote:
>
>> Hi Ashish,
>>
>> I added a comment to GERONIMO-4900. This problem should have been fixed as
>> part of 2.1.4; unfortunately, it seems that the fix was applied to trunk
>> after the creation of the 2.1.4 branch. Could you please confirm that this
>> works OK against trunk?
>>
>> Regarding the Tomcat bug reported by this email, the problem is caused by
>> the AbstractNameQuery used to find the name of Tomcat Web app context GBean.
>> When the clustered WAR is within an EAR, the query returned by
>> WADITomcatClusteringBuilder.createTomcatWebAppContextNameQuery does not
>> work.  I am not sure why as I cannot debug (I cannot build the server due to
>> missing a dependency "org.apache.activemq:activemq-core:jar:5.3.0"...).
>> Having said that, I would suggest to substitute
>> WADITomcatClusteringBuilder.extractWebModule.with:
>>
>>protected GBeanData extractWebModule(DeploymentContext moduleContext)
>> throws DeploymentException {
>>Configuration configuration = moduleContext.getConfiguration();
>>try {
>>return
>> configuration.getGBeans().get(moduleContext.getModuleName());
>>} catch (GBeanNotFoundException e) {
>>throw new DeploymentException("Could not locate web module
>> gbean in web app configuration", e);
>>}
>>}
>>
>> I hope this helps.
>>
>> Thanks,
>> Gianny
>>
>>
>> On 12/10/2009, at 7:09 PM, Ashish Jain wrote:
>>
>>  Hello Gianny,
>>>
>>> I see you have suggested that you were able to figure out the problem.
>>> Can you please suggest what is the problem? Is there any workaround for this
>>> issue?
>>> Any associated JIRA's???
>>>
>>> There is another JIRA which has been opened for a similar issue. Please
>>> have a look at the following url https://issues.apache.org/
>>> jira/browse/GERONIMO-4900.
>>>
>>> I am still investigating will let you know if I find anything.
>>>
>>> Thanks
>>> Ashish
>>>
>>> On Tue, Jul 8, 2008 at 6:21 PM, Jason Warner  wrote:
>>> Fantastic, Gianny.  Thanks for looking into this!
>>>
>>>
>>> On Mon, Jul 7, 2008 at 9:19 PM, Gianny Damour <
>>> gianny.dam...@optusnet.com.au> wrote:
>>> Hello Jason,
>>>
>>> I had a quick look and identified the problem. I will check-in a fix
>>> during the day.
>>>
>>> Thanks,
>>> Gianny
>>>
>>>
>>> On 08/07/2008, at 4:10 AM, Jason Warner wrote:
>>>
>>> I've spent some time looking at this, but I haven't really gotten
>>> anywhere with it.  While debugging I noticed that the error occurs because
>>> the configuration id that is provided by the module upon loading doesn't
>>> match what geronimo is expecting.  The problem I'm having is figuring out
>>> where on earth geronimo is getting the config id that it's expecting.  It
>>> seems that it's pulling it from the plan itself, but I'm not sure how.  I've
>>> been a little busy lately though and haven't been able to look into it
>>> further.  Anyone else have any thoughts on what could be the cause of this?
>>>
>>> Thanks
>>>
>>> On Tue, Jul 1, 2008 at 5:17 PM, jon.saba...@gmail.com <
>>> jon.saba...@gmail.com> wrote:
>>>
>>> The end goal would be to deploy an ear containing a coupe ejb modules,
>>> wars &
>>> rars with wadi clustering enabled for the web apps - packaging the
>>> wadi-webapp.war into an ear was the simplest test I could think of to see
>>> if
>>> the war would deploy cleanly with tomcat-clustering-wadi in the
>>> deployment
>>> plan.
>>>
>>> In the ear that I used to test I actually left out application.xml &
>>> geronimo-application.xml (just jarred up the war), but here is the
>>> web.xml &
>>> geronimo-web.xml I used:
>>>
>>> 
>>> >> 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>
>>>
>>> 
>>>
>>>  
>>>
>>>  
>>>  org.mortbay.jetty.servlet.SessionPath
>>>  /wadi
>>>   
>>>  
>>>
>>>
>>> 
>>>
>>>  
>>>  jsp.aopTest_jsp
>>>  jsp.aopTest_jsp
>>>  
>>>
>>>  
>>>

Re: using wadi with tomcat & web app in an ear

2009-10-12 Thread Ashish Jain

Hi Gianny,

Did you mean that the Missing Dependency Exception will be fixed by the code
snippet suggested by you. I had build the new jar
"geronimo-tomcat6-clustering-builder-wadi-2.1.4.jar" and replaced the
existing one in g214 with this new one. Started two clean instances of g214
with replaced jars. deployed the application.

The server still throws the Missing Dependency Exception
"org.apache.geronimo.kernel.repository.MissingDependencyException: Missing
dependency: default/ClusterTestEAR/1.0/ear".

Please advice.

Thanks
Ashish

On Mon, Oct 12, 2009 at 5:02 PM, Gianny Damour <
gianny.dam...@optusnet.com.au> wrote:

> Hi Ashish,
>
> I added a comment to GERONIMO-4900. This problem should have been fixed as
> part of 2.1.4; unfortunately, it seems that the fix was applied to trunk
> after the creation of the 2.1.4 branch. Could you please confirm that this
> works OK against trunk?
>
> Regarding the Tomcat bug reported by this email, the problem is caused by
> the AbstractNameQuery used to find the name of Tomcat Web app context GBean.
> When the clustered WAR is within an EAR, the query returned by
> WADITomcatClusteringBuilder.createTomcatWebAppContextNameQuery does not
> work.  I am not sure why as I cannot debug (I cannot build the server due to
> missing a dependency "org.apache.activemq:activemq-core:jar:5.3.0"...).
> Having said that, I would suggest to substitute
> WADITomcatClusteringBuilder.extractWebModule.with:
>
>protected GBeanData extractWebModule(DeploymentContext moduleContext)
> throws DeploymentException {
>Configuration configuration = moduleContext.getConfiguration();
>try {
>return
> configuration.getGBeans().get(moduleContext.getModuleName());
>} catch (GBeanNotFoundException e) {
>throw new DeploymentException("Could not locate web module gbean
> in web app configuration", e);
>}
>}
>
> I hope this helps.
>
> Thanks,
> Gianny
>
>
> On 12/10/2009, at 7:09 PM, Ashish Jain wrote:
>
>  Hello Gianny,
>>
>> I see you have suggested that you were able to figure out the problem. Can
>> you please suggest what is the problem? Is there any workaround for this
>> issue?
>> Any associated JIRA's???
>>
>> There is another JIRA which has been opened for a similar issue. Please
>> have a look at the following url https://issues.apache.org/
>> jira/browse/GERONIMO-4900.
>>
>> I am still investigating will let you know if I find anything.
>>
>> Thanks
>> Ashish
>>
>> On Tue, Jul 8, 2008 at 6:21 PM, Jason Warner  wrote:
>> Fantastic, Gianny.  Thanks for looking into this!
>>
>>
>> On Mon, Jul 7, 2008 at 9:19 PM, Gianny Damour <
>> gianny.dam...@optusnet.com.au> wrote:
>> Hello Jason,
>>
>> I had a quick look and identified the problem. I will check-in a fix
>> during the day.
>>
>> Thanks,
>> Gianny
>>
>>
>> On 08/07/2008, at 4:10 AM, Jason Warner wrote:
>>
>> I've spent some time looking at this, but I haven't really gotten anywhere
>> with it.  While debugging I noticed that the error occurs because the
>> configuration id that is provided by the module upon loading doesn't match
>> what geronimo is expecting.  The problem I'm having is figuring out where on
>> earth geronimo is getting the config id that it's expecting.  It seems that
>> it's pulling it from the plan itself, but I'm not sure how.  I've been a
>> little busy lately though and haven't been able to look into it further.
>>  Anyone else have any thoughts on what could be the cause of this?
>>
>> Thanks
>>
>> On Tue, Jul 1, 2008 at 5:17 PM, jon.saba...@gmail.com <
>> jon.saba...@gmail.com> wrote:
>>
>> The end goal would be to deploy an ear containing a coupe ejb modules,
>> wars &
>> rars with wadi clustering enabled for the web apps - packaging the
>> wadi-webapp.war into an ear was the simplest test I could think of to see
>> if
>> the war would deploy cleanly with tomcat-clustering-wadi in the deployment
>> plan.
>>
>> In the ear that I used to test I actually left out application.xml &
>> geronimo-application.xml (just jarred up the war), but here is the web.xml
>> &
>> geronimo-web.xml I used:
>>
>> 
>> > 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>
>>
>> 
>>
>>  
>>
>>  
>>  org.mortbay.jetty.servlet.SessionPath
>>  /wadi
>>   
>>  
>>
>>
>> 
>>
>>  
>>  jsp.aopTest_jsp
>>  jsp.aopTest_jsp
>>  
>>
>>  
>>  jsp.destroy_jsp
>>  jsp.destroy_jsp
>>  
>>
>>  
>>  jsp.index_jsp
>>  jsp.index_jsp
>>  
>>
>>  
>>  jsp.session_jsp
>>  jsp.session_jsp
>>  
>>
>>  
>>  jsp.aopTest_jsp
>>  /aopTest.jsp
>>  
>>
>>  
>>  jsp.destroy_jsp
>>  /destroy.jsp
>>  
>>
>>  
>>  jsp.index_jsp
>>  /index.jsp
>>  
>>
>>  
>>  jsp.session_jsp
>>  /session.jsp
>>  
>>
>> 
>>
>>
>> 
>> --
>> 
>>
>> http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.1";
>>  xmlns:wadi="http://geronimo.apache.org/xml/ns/clustering-wadi-1.2";>
>>
>>  
>>  
>>  or

Re: Jetty Advanced Integration Test Failure

2009-10-12 Thread Quintin Beukes

No problem.

Quintin Beukes



On Mon, Oct 12, 2009 at 8:18 AM, Ivan  wrote:
> Thanks, Quinitin Beukes, could ypu please open a JIRA for it ? and if
> possible, attach your diff file to the JIRA.
>
> 2009/10/12 Quintin Beukes 
>>
>> Hey,
>>
>> I found the cause of the test failure.
>>
>> In the file: {src
>>
>> root}/plugins/jetty7/geronimo-jetty7/./src/main/java/org/apache/geronimo/jetty7/connector/JettyConnector.java
>> Line: 289
>>
>> It reads: new String[]{"host", "port", "minThreads", "maxThreads",
>> "bufferSizeBytes", "headerBufferSizeBytes", "acceptQueueSize",
>> "lingerMillis", "protocol", "redirectPort", "connectUrl",
>> "maxIdleTimeMs"},
>> Change to: new String[]{"host", "port", "minThreads", "maxThreads",
>> "bufferSizeBytes", "headerBufferSizeBytes", "acceptQueueSize",
>> "lingerMillis", "redirectPort", "maxIdleTimeMs"},
>>
>> Basically removing the "protocol" and "connectUrl" attributes from the
>> persistent interface attributes fixes the problem.
>>
>> "protocol" is static for Jetty BIO connector, so it doesn't need to be
>> saved, or can't be specified.
>> "connectUrl" is generated on the fly through getConnectUrl(), so can't
>> be saved either.
>>
>> So unless my understanding of what persistentAttributes are is
>> incorrect, this seems to be the correct solution? Please correct me if
>> I'm wrong.
>>
>> What caused the problem is that the JettyConnector class doesn't have
>> a setter for these attributes, so when XBean searches all the
>> specified attributes' setters, it fails when it can't find these. This
>> caused the test to fail, because the connector doesn't start again
>> after being edited (enters the failed state).
>>
>> Quintin Beukes
>
>
>
> --
> Ivan
>

Re: osgi progress

David Jencks wrote:

I only have a minute so can't address anything in detail right now.

Most of the servicemix bundle dependencies can probably be on released
versions. I went for speed and used the ones from my checked out
servicemix trunk in case I needed to patch them.

I don't think we need the geronimo plexus bundles I set up -- although
we do need to find some solution for accessing the code or not using
it at all.

What are the testsuite errors you get? It would be useful to find out
if they are windows specific. Similarly it would be great to find out
if anyone else can build on a non-windows system :-)
I took a little deeper look at the deployment test case errors I'm
getting. The root cause of the failure is this exception:

Since this is failing just calling bundleContext.installBundle() in the
MockBundleContext code, I suspect I'm not running under karaf. Have I
missed some setup step somewhere?

Rick

thanks
david jencks

On Oct 9, 2009, at 4:55 AM, Rick McGuire wrote:

David Jencks wrote:
I changed the url scheme so we always use pax maven urls for
everything in the geronimo repository, and now I can get, with some
work, all the plugin bundles to start as bundles. However they
mostly don't start as plugins (i.e., no gbeans start). I haven't
figured out why yet.

How to get it to "run":

build
This one word is starting to remind me of the famous Sydney Harris
cartoon:

http://www.sciencecartoonsplus.com/pages/gallery.php

I've had a few issues getting this to build, so I thought I'd capture
the notes here for the benefit of others. Some of these we can fix
in the build, others are things that need to be accounted for before
building. A major problem is getting all of the dependencies into
your maven repository so the build can work.

1) servicemix bundles. In addition to the patch that David
provided, you need to checkout and build the servicemix bundles from:

https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk

Unfortunately, the root pom for servicemix does not build all of the
subprojects. Many of the ones that are skipped are required by
Geronimo and need to be built individually. This list includes:

jaxb-impl-2.1.6
xmlbeans-2.4.0 (NOTE: this builds 2.4.0_3-SNAPSHOT, but the
dependency is currently 2.4.0_2-SNAPSHOT. The Geronimo pom needs to
be adjusted).

woodstox-3.2.8
jline-0.9.94

The framework builds additional bundlized versions of dependencies,
but at the moment, they are not included in the build. The
subprojects are located in framework/bundles, but there's no root pom
that builds all of these, so each subproject needs to be built
individually. There are some dependencies between these
subprojects. For example, plexus-archiver depends on plexus-utils,
so plexus-utils needs to be built first. Unfortunately, plexus-utils
is building version 1.5.15_1-SNAPSHOT, and plexus-archiver has a
dependency on 1.4.5_-SNAPSHOT. plexus-utils exports a 1.4.5 level of
the packages, so I'm guessing this was intended to be
1.4.5_1-SNAPSHOT, so the POM needs adjusting.

Once I've done the steps above, I get some test failures in
geronimo-kernel. If I try to build with tests turned off, then I get
the following failure:

1) org.apache.geronimo.framework:geronimo-kernel:jar:tests:3.0-SNAPSHOT

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.framework
-Dartifac
tId=geronimo-kernel -Dversion=3.0-SNAPSHOT -Dclassifier=tests
-Dpackaging=jar -D

file=/path/to/file

most likely the result of the test failures. The test failures
don't make much sense to me, but this might be a Windows-specific
problem with normalizing URLs. If I comment out the assertions that
are failing, I'm able to get geronimo-kernel to build, but get test
failures in other projects. Now, however, disabling the tests
appears to work.

This gets me to errors with the dependency history checks because in
the change to the xmlbeans dependency. This requires deleting all of
the history files to continue on.

Ok, once I get past all of that, I get a whole series of errors that
I don't know how to get around. I'm pretty much stuck here, but I'll
go back and look at the geronimo-kernel test failures and see if I
can figure out what's going on there. Here are the

[jira] Commented: (GERONIMO-4900) MissingDependencyException while deploying EAR in Clustering Environment


[ 
https://issues.apache.org/jira/browse/GERONIMO-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764662#action_12764662
 ] 

Ashish Jain commented on GERONIMO-4900:
---

import org.apache.geronimo.gbean.annotation.GBean;
import org.apache.geronimo.gbean.annotation.ParamAttribute;
import org.apache.geronimo.gbean.annotation.ParamReference;
import org.apache.geronimo.gbean.annotation.ParamSpecial;
import org.apache.geronimo.gbean.annotation.SpecialAttributeType;

Please advice.

> MissingDependencyException while deploying EAR in Clustering Environment
> 
>
> Key: GERONIMO-4900
> URL: https://issues.apache.org/jira/browse/GERONIMO-4900
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.1.4
>Reporter: Amit puri
>Assignee: Ashish Jain
> Attachments: ClusterTestEAR.ear
>
>
> 1. Installed two geronimo instances A and B at different paths
> 2. Made the following changes to Geronimo A
>For var\config\config-substitutions.properties
>clusterNodeName=NODE --> clusterNodeName=NODE-A
>For var\config\config.xml, add the following contents to module: 
> org.apache.geronimo.configs/farming/2.1.4/car
> -
>  name="org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=NodeInfo,name=NODE-B"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-B
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> localhost
> 1109
> JMXConnector
> false
>   
> 
> -
> 3. Made the following changes to Geronimo B
>For var\config\config-substitutions.properties
>clusterNodeName=NODE --> clusterNodeName=NODE-B
>PortOffset=0 --> PortOffset=10
>For var\config\config.xml, add the following contents to module: 
> org.apache.geronimo.configs/farming/2.1.4/car
> -
>  name="org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=NodeInfo,name=NODE-A"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-A
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> localhost
> 1099
> JMXConnector
> false
>   
> 
> -
> 4. Started both Geronimo A and B
> 5. Ran the following commands in Geronimo_A_Path\bin
>deploy --user system --password manager start 
> org.apache.geronimo.configs/farming/2.1.4/car
>deploy --user system --password manager --port 1109 start 
> org.apache.geronimo.configs/farming/2.1.4/car
> 6. Deployed one sample ClusterTestEAR.ear in Geronimo_A_Path\bin
> deploy --user system --password manager deploy --targets  
> org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=ConfigurationStore,name=MasterConfigurationStore
>  PATH_SAMPLE\ClusterTestEAR.ear
> Output:
> A) Errors in Geronimo A geronimo.log
>  INFO  [BasicClusterConfigurationStoreClient] Upload of configuration 
> [default/ClusterTestEAR_G_SLAVE/1.0/ear] - [File(s) transferred to server.  
> Resuming deployment operation.]
>  INFO  [BasicClusterConfigurationController] Exception while starting 
> configuration [default/ClusterTestEAR_G_SLAVE/1.0/ear] on [NODE-B]. Ignoring.
> org.apache.geronimo.kernel.config.LifecycleException: load of 
> default/ClusterTestEAR_G_SLAVE/1.0/ear failed
> Caused by: 
> org.apache.geronimo.kernel.config.InvalidConfigException: Error starting 
> configuration gbean default/ClusterTestEAR_G_SLAVE/1

[jira] Commented: (GERONIMO-4900) MissingDependencyException while deploying EAR in Clustering Environment


[ 
https://issues.apache.org/jira/browse/GERONIMO-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764661#action_12764661
 ] 

Ashish Jain commented on GERONIMO-4900:
---

Helllo Gianny, thanks for pointing this out. I feel that the fix for 
GERONIMO-4556 did not make to g214. I have the code for g214 tags and I am not 
able to see this revision applied to it.. I tried applying the revision 
http://svn.apache.org/viewvc?view=rev&revision=748991 to my g214 code  base but 
I see several un resolved imports in MasterConfigurationStore.java related to 
gbean annotations. A few of them I am listing here.


> MissingDependencyException while deploying EAR in Clustering Environment
> 
>
> Key: GERONIMO-4900
> URL: https://issues.apache.org/jira/browse/GERONIMO-4900
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.1.4
>Reporter: Amit puri
>Assignee: Ashish Jain
> Attachments: ClusterTestEAR.ear
>
>
> 1. Installed two geronimo instances A and B at different paths
> 2. Made the following changes to Geronimo A
>For var\config\config-substitutions.properties
>clusterNodeName=NODE --> clusterNodeName=NODE-A
>For var\config\config.xml, add the following contents to module: 
> org.apache.geronimo.configs/farming/2.1.4/car
> -
>  name="org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=NodeInfo,name=NODE-B"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-B
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> localhost
> 1109
> JMXConnector
> false
>   
> 
> -
> 3. Made the following changes to Geronimo B
>For var\config\config-substitutions.properties
>clusterNodeName=NODE --> clusterNodeName=NODE-B
>PortOffset=0 --> PortOffset=10
>For var\config\config.xml, add the following contents to module: 
> org.apache.geronimo.configs/farming/2.1.4/car
> -
>  name="org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=NodeInfo,name=NODE-A"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-A
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> localhost
> 1099
> JMXConnector
> false
>   
> 
> -
> 4. Started both Geronimo A and B
> 5. Ran the following commands in Geronimo_A_Path\bin
>deploy --user system --password manager start 
> org.apache.geronimo.configs/farming/2.1.4/car
>deploy --user system --password manager --port 1109 start 
> org.apache.geronimo.configs/farming/2.1.4/car
> 6. Deployed one sample ClusterTestEAR.ear in Geronimo_A_Path\bin
> deploy --user system --password manager deploy --targets  
> org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=ConfigurationStore,name=MasterConfigurationStore
>  PATH_SAMPLE\ClusterTestEAR.ear
> Output:
> A) Errors in Geronimo A geronimo.log
>  INFO  [BasicClusterConfigurationStoreClient] Upload of configuration 
> [default/ClusterTestEAR_G_SLAVE/1.0/ear] - [File(s) transferred to server.  
> Resuming deployment operation.]
>  INFO  [BasicClusterConfigurationController] Exception while starting 
> configuration [default/ClusterTestEAR_G_SLAVE/1.0/ear] on [NODE-B]. Ignoring.
> org.apache.geronimo.kernel.config.LifecycleException: load of 
> default/ClusterTestEAR_G_SLAVE/1.0/ear failed
> Caused by: 
> org

Re: using wadi with tomcat & web app in an ear

2009-10-12 Thread Gianny Damour

Hi Ashish,

I added a comment to GERONIMO-4900. This problem should have been  
fixed as part of 2.1.4; unfortunately, it seems that the fix was  
applied to trunk after the creation of the 2.1.4 branch. Could you  
please confirm that this works OK against trunk?

Regarding the Tomcat bug reported by this email, the problem is  
caused by the AbstractNameQuery used to find the name of Tomcat Web  
app context GBean. When the clustered WAR is within an EAR, the query  
returned by  
WADITomcatClusteringBuilder.createTomcatWebAppContextNameQuery does  
not work.  I am not sure why as I cannot debug (I cannot build the  
server due to missing a dependency "org.apache.activemq:activemq- 
core:jar:5.3.0"...). Having said that, I would suggest to substitute  
WADITomcatClusteringBuilder.extractWebModule.with:

protected GBeanData extractWebModule(DeploymentContext  
moduleContext) throws DeploymentException {

Configuration configuration = moduleContext.getConfiguration();
try {
return configuration.getGBeans().get 
(moduleContext.getModuleName());

} catch (GBeanNotFoundException e) {
throw new DeploymentException("Could not locate web  
module gbean in web app configuration", e);

}
}

I hope this helps.

Thanks,
Gianny

On 12/10/2009, at 7:09 PM, Ashish Jain wrote:

Hello Gianny,

I see you have suggested that you were able to figure out the  
problem. Can you please suggest what is the problem? Is there any  
workaround for this issue?

Any associated JIRA's???

There is another JIRA which has been opened for a similar issue.  
Please have a look at the following url https://issues.apache.org/ 
jira/browse/GERONIMO-4900.

I am still investigating will let you know if I find anything.

Thanks
Ashish

On Tue, Jul 8, 2008 at 6:21 PM, Jason Warner  wrote:
Fantastic, Gianny.  Thanks for looking into this!

On Mon, Jul 7, 2008 at 9:19 PM, Gianny Damour  
 wrote:

Hello Jason,

I had a quick look and identified the problem. I will check-in a  
fix during the day.

Thanks,
Gianny

On 08/07/2008, at 4:10 AM, Jason Warner wrote:

I've spent some time looking at this, but I haven't really gotten  
anywhere with it.  While debugging I noticed that the error occurs  
because the configuration id that is provided by the module upon  
loading doesn't match what geronimo is expecting.  The problem I'm  
having is figuring out where on earth geronimo is getting the  
config id that it's expecting.  It seems that it's pulling it from  
the plan itself, but I'm not sure how.  I've been a little busy  
lately though and haven't been able to look into it further.   
Anyone else have any thoughts on what could be the cause of this?

Thanks

On Tue, Jul 1, 2008 at 5:17 PM, jon.saba...@gmail.com  
 wrote:

The end goal would be to deploy an ear containing a coupe ejb  
modules, wars &

rars with wadi clustering enabled for the web apps - packaging the
wadi-webapp.war into an ear was the simplest test I could think of  
to see if
the war would deploy cleanly with tomcat-clustering-wadi in the  
deployment

plan.

In the ear that I used to test I actually left out application.xml &
geronimo-application.xml (just jarred up the war), but here is the  
web.xml &

geronimo-web.xml I used:

Application

2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>

  org.mortbay.jetty.servlet.SessionPath
  /wadi

  jsp.aopTest_jsp
  jsp.aopTest_jsp

  jsp.destroy_jsp
  jsp.destroy_jsp

  jsp.index_jsp
  jsp.index_jsp

  jsp.session_jsp
  jsp.session_jsp

  jsp.aopTest_jsp
  /aopTest.jsp

  jsp.destroy_jsp
  /destroy.jsp

  jsp.index_jsp
  /index.jsp

  jsp.session_jsp
  /session.jsp

--

http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.1";
  xmlns:wadi="http://geronimo.apache.org/xml/ns/clustering-wadi-1.2";>

  org.codehaus.wadi
  wadi-webapp
  2.0-SNAPSHOT
  war

 /wadi-webapp

 false

In the ear that I would actually like to cluster there is a
geronimo-application.xml as well as application.xml (no  
modifications to
working configs with those, only change would be a > element
in the war's web.xml &  in geronimo- 
web.xml),  but
the exception thrown during deployment matches the test ears  
exception with

the only exception being the gbean name being looked for.

Jason Warner wrote:
>
> I'm a little confused about what you're trying to do.  Are you  
saying

> you're
> trying to package the wadi-webapp.war into an ear file?  Do you  
have a

> specific goal by doing this?  I think this issue is caused by
> misconfiguration in the ear deployment plan.  Would you be able  
to post

> your
> ear?  If not, could you post your geronimo-application.xml?
>
> Thanks!
>
> On Fri, Jun 27, 2008 at 6:49 PM, jon.saba...@gma

Re: osgi progress


Ivan wrote:
After building many 3-rd parties libries locally, I got the same error 
that Jarek found, luckily,  it seems that the error "INFO 
 [DeploymentContext] The Strict Manifest Classpath" is not the root 
cause,  after setting karaf.home property, the build process could 
continue , But, I got another error below, still try to find why ...


What does the karaf.home property need to be set to and where do you set it?

Rick



17:33:56,218 WARN  [DependencyManager] Could not start bundle: 
org.apache.geronimo.framework.geronimo-jmx-remoting [68]
org.osgi.framework.BundleException: Unresolved constraint in bundle 
org.apache.geronimo.framework.geronimo-jmx-remoting [68]: package; 
(package=org.apache.xbean.naming)

at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915)
at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902)
at 
org.apache.geronimo.system.configuration.DependencyManager.installed(DependencyManager.java:97)
at 
org.apache.geronimo.system.configuration.DependencyManager.bundleChanged(DependencyManager.java:70)
at 
org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:800)
at 
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:728)
at 
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610)
at 
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3576)

at org.apache.felix.framework.Felix.installBundle(Felix.java:2478)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2277)
at 
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:130)
at 
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:108)
at 
org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:208)
at 
org.apache.geronimo.deployment.DeploymentContext.initializeConfiguration(DeploymentContext.java:174)
at 
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:249)
at 
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:209)
at 
org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:854)
at 
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
at 
org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:517)
at 
org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:337)
at 
org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:234)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

at org.codehaus.classworlds.Launcher.la

[jira] Created: (XBEAN-141) NumberFormatException upon installing the shaded subprojects - asm and reflect - into Apache Felix 2.0.0

2009-10-12 Thread Jacek Laskowski (JIRA)

NumberFormatException upon installing the shaded subprojects - asm and reflect 
- into Apache Felix 2.0.0


 Key: XBEAN-141
 URL: https://issues.apache.org/jira/browse/XBEAN-141
 Project: XBean
  Issue Type: Bug
  Components: reflect
Affects Versions: 3.6
Reporter: Jacek Laskowski
 Fix For: 3.7


The header Bundle-Version is set to 3.7-SNAPSHOT and it's done manually in 
pom.xml while shading. It should be 3.7.0.SNAPSHOT as maven-bundle-plugin does 
for the other subprojects.

jlaskow...@work /cygdrive/c/apps/felix-framework
$ java -jar bin/felix.jar

Welcome to Felix


-> version
2.0.0
-> install 
file:/C:\.m2\org\apache\xbean\xbean-asm-shaded\3.7-SNAPSHOT\xbean-asm-shaded-3.7-SNAPSHOT.jar
java.lang.NumberFormatException: For input string: "7-SNAPSHOT"
at 
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:458)
at java.lang.Integer.parseInt(Integer.java:499)
at org.osgi.framework.Version.(Version.java:129)
at org.osgi.framework.Version.parseVersion(Version.java:218)
at 
org.apache.felix.framework.util.manifestparser.ManifestParser.(ManifestParser.java:77)
at org.apache.felix.framework.ModuleImpl.(ModuleImpl.java:200)
at 
org.apache.felix.framework.BundleImpl.createModule(BundleImpl.java:1095)
at org.apache.felix.framework.BundleImpl.(BundleImpl.java:82)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2379)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2282)
at 
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:130)
at 
org.apache.felix.shell.impl.InstallCommandImpl.install(InstallCommandImpl.java:104)
at 
org.apache.felix.shell.impl.InstallCommandImpl.execute(InstallCommandImpl.java:68)
at 
org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Activator.java:281)
at 
org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java:184)
at java.lang.Thread.run(Thread.java:619)
java.lang.NumberFormatException: For input string: "7-SNAPSHOT"

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

[jira] Commented: (GERONIMO-4900) MissingDependencyException while deploying EAR in Clustering Environment

2009-10-12 Thread Gianny Damour (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764643#action_12764643
 ] 

Gianny Damour commented on GERONIMO-4900:
-

This problem is due to the modification of configuration names (suffix 
'_G_SLAVE'  is added to base name) happening during farm deployment.

GERONIMO-4556, which should have been included in 2.1.4, addresses this 
problem. In a few words, configuration names are no longer updated.

> MissingDependencyException while deploying EAR in Clustering Environment
> 
>
> Key: GERONIMO-4900
> URL: https://issues.apache.org/jira/browse/GERONIMO-4900
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.1.4
>Reporter: Amit puri
>Assignee: Ashish Jain
> Attachments: ClusterTestEAR.ear
>
>
> 1. Installed two geronimo instances A and B at different paths
> 2. Made the following changes to Geronimo A
>For var\config\config-substitutions.properties
>clusterNodeName=NODE --> clusterNodeName=NODE-A
>For var\config\config.xml, add the following contents to module: 
> org.apache.geronimo.configs/farming/2.1.4/car
> -
>  name="org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=NodeInfo,name=NODE-B"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-B
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> localhost
> 1109
> JMXConnector
> false
>   
> 
> -
> 3. Made the following changes to Geronimo B
>For var\config\config-substitutions.properties
>clusterNodeName=NODE --> clusterNodeName=NODE-B
>PortOffset=0 --> PortOffset=10
>For var\config\config.xml, add the following contents to module: 
> org.apache.geronimo.configs/farming/2.1.4/car
> -
>  name="org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=NodeInfo,name=NODE-A"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-A
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> localhost
> 1099
> JMXConnector
> false
>   
> 
> -
> 4. Started both Geronimo A and B
> 5. Ran the following commands in Geronimo_A_Path\bin
>deploy --user system --password manager start 
> org.apache.geronimo.configs/farming/2.1.4/car
>deploy --user system --password manager --port 1109 start 
> org.apache.geronimo.configs/farming/2.1.4/car
> 6. Deployed one sample ClusterTestEAR.ear in Geronimo_A_Path\bin
> deploy --user system --password manager deploy --targets  
> org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=ConfigurationStore,name=MasterConfigurationStore
>  PATH_SAMPLE\ClusterTestEAR.ear
> Output:
> A) Errors in Geronimo A geronimo.log
>  INFO  [BasicClusterConfigurationStoreClient] Upload of configuration 
> [default/ClusterTestEAR_G_SLAVE/1.0/ear] - [File(s) transferred to server.  
> Resuming deployment operation.]
>  INFO  [BasicClusterConfigurationController] Exception while starting 
> configuration [default/ClusterTestEAR_G_SLAVE/1.0/ear] on [NODE-B]. Ignoring.
> org.apache.geronimo.kernel.config.LifecycleException: load of 
> default/ClusterTestEAR_G_SLAVE/1.0/ear failed
> Caused by: 
> org.apache.geronimo.kernel.config.InvalidConfigException: Error starting 
> configuration gbean default/ClusterTestEAR_G_SLAVE/1.0/ear
>   at 
> org

Re: using wadi with tomcat & web app in an ear

2009-10-12 Thread Ashish Jain

Hello Gianny,

I see you have suggested that you were able to figure out the problem. Can
you please suggest what is the problem? Is there any workaround for this
issue?
Any associated JIRA's???

There is another JIRA which has been opened for a similar issue. Please have
a look at the following url
https://issues.apache.org/jira/browse/GERONIMO-4900.

I am still investigating will let you know if I find anything.

Thanks
Ashish

On Tue, Jul 8, 2008 at 6:21 PM, Jason Warner  wrote:

> Fantastic, Gianny.  Thanks for looking into this!
>
>
> On Mon, Jul 7, 2008 at 9:19 PM, Gianny Damour <
> gianny.dam...@optusnet.com.au> wrote:
>
>> Hello Jason,
>>
>> I had a quick look and identified the problem. I will check-in a fix
>> during the day.
>>
>> Thanks,
>> Gianny
>>
>>
>> On 08/07/2008, at 4:10 AM, Jason Warner wrote:
>>
>>  I've spent some time looking at this, but I haven't really gotten
>>> anywhere with it.  While debugging I noticed that the error occurs because
>>> the configuration id that is provided by the module upon loading doesn't
>>> match what geronimo is expecting.  The problem I'm having is figuring out
>>> where on earth geronimo is getting the config id that it's expecting.  It
>>> seems that it's pulling it from the plan itself, but I'm not sure how.  I've
>>> been a little busy lately though and haven't been able to look into it
>>> further.  Anyone else have any thoughts on what could be the cause of this?
>>>
>>> Thanks
>>>
>>> On Tue, Jul 1, 2008 at 5:17 PM, jon.saba...@gmail.com <
>>> jon.saba...@gmail.com> wrote:
>>>
>>> The end goal would be to deploy an ear containing a coupe ejb modules,
>>> wars &
>>> rars with wadi clustering enabled for the web apps - packaging the
>>> wadi-webapp.war into an ear was the simplest test I could think of to see
>>> if
>>> the war would deploy cleanly with tomcat-clustering-wadi in the
>>> deployment
>>> plan.
>>>
>>> In the ear that I used to test I actually left out application.xml &
>>> geronimo-application.xml (just jarred up the war), but here is the
>>> web.xml &
>>> geronimo-web.xml I used:
>>>
>>> 
>>> >> 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>
>>>
>>> 
>>>
>>>  
>>>
>>>  
>>>   org.mortbay.jetty.servlet.SessionPath
>>>   /wadi
>>>
>>>  
>>>
>>>
>>> 
>>>
>>>   
>>>   jsp.aopTest_jsp
>>>   jsp.aopTest_jsp
>>>   
>>>
>>>   
>>>   jsp.destroy_jsp
>>>   jsp.destroy_jsp
>>>   
>>>
>>>   
>>>   jsp.index_jsp
>>>   jsp.index_jsp
>>>   
>>>
>>>   
>>>   jsp.session_jsp
>>>   jsp.session_jsp
>>>   
>>>
>>>   
>>>   jsp.aopTest_jsp
>>>   /aopTest.jsp
>>>   
>>>
>>>   
>>>   jsp.destroy_jsp
>>>   /destroy.jsp
>>>   
>>>
>>>   
>>>   jsp.index_jsp
>>>   /index.jsp
>>>   
>>>
>>>   
>>>   jsp.session_jsp
>>>   /session.jsp
>>>   
>>>
>>> 
>>>
>>>
>>> 
>>> --
>>> 
>>>
>>> http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.1";
>>>   xmlns:wadi="http://geronimo.apache.org/xml/ns/clustering-wadi-1.2";>
>>>
>>>   
>>>   
>>>   org.codehaus.wadi
>>>   wadi-webapp
>>>   2.0-SNAPSHOT
>>>   war
>>>   
>>>   
>>>
>>>  /wadi-webapp
>>>
>>>  
>>>  false
>>>  
>>>
>>> 
>>>
>>> In the ear that I would actually like to cluster there is a
>>> geronimo-application.xml as well as application.xml (no modifications to
>>> working configs with those, only change would be a 
>>> element
>>> in the war's web.xml &  in geronimo-web.xml),
>>>  but
>>> the exception thrown during deployment matches the test ears exception
>>> with
>>> the only exception being the gbean name being looked for.
>>>
>>>
>>> Jason Warner wrote:
>>> >
>>> > I'm a little confused about what you're trying to do.  Are you saying
>>> > you're
>>> > trying to package the wadi-webapp.war into an ear file?  Do you have a
>>> > specific goal by doing this?  I think this issue is caused by
>>> > misconfiguration in the ear deployment plan.  Would you be able to post
>>> > your
>>> > ear?  If not, could you post your geronimo-application.xml?
>>> >
>>> > Thanks!
>>> >
>>> > On Fri, Jun 27, 2008 at 6:49 PM, jon.saba...@gmail.com <
>>> > jon.saba...@gmail.com> wrote:
>>> >
>>> >>
>>> >> I am having trouble enabling wadi for a web app contained in an ear.
>>>  I
>>> >> am
>>> >> able to deploy the sample wadi-webapp war by changing the
>>> clustering-wadi
>>> >> tag in geronimo-web.xml to tomcat-clustering-wadi but am unable to
>>> >> package
>>> >> the war in an ear, when doing so geronimo complains about not being
>>> able
>>> >> to
>>> >> locate the web module gbean.
>>> >>
>>> >> Here is the relevant portion of the logs:
>>> >>
>>> >> 16:40:50,618 INFO  [DirectoryHotDeployer] Deploying wadi.ear
>>> >> 16:40:50,723 ERROR [DirectoryHotDeployer] Unable to deploy: Could not
>>> >> locate
>>> >> web module gbean in web app configuration
>>> >> org.apache.geronimo.common.DeploymentException: Could not locate web
>>> >> module
>>> >

[BUILD] trunk: Failed for Revision: 824210

Geronimo Revision: 824210 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 376 minutes 8 seconds
[INFO] Finished at: Mon Oct 12 03:19:36 EDT 2009
[INFO] Final Memory: 1342M/1536M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012/logs-2100-tomcat/
 
 
[INFO] Scanning for projects...
[INFO] 
[INFO] Building Geronimo TestSuite
[INFO]task-segment: [install]
[INFO] 
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/selenium-maven-plugin/1.0-rc-1/selenium-maven-plugin-1.0-rc-1.pom
21K downloaded
Downloading: 
http://nexus.openqa.org/content/repositories/releases/org/codehaus/mojo/mojo-parent/19/mojo-parent-19.pom
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/mojo-parent/19/mojo-parent-19.pom
17K downloaded
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/selenium-maven-plugin/1.0-rc-1/selenium-maven-plugin-1.0-rc-1.jar
60K downloaded
[INFO] snapshot 
org.apache.geronimo.buildsupport:geronimo-maven-plugin:3.0-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] snapshot 
org.apache.geronimo.buildsupport:geronimo-maven-plugin:3.0-SNAPSHOT: checking 
for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.buildsupport:buildsupport:3.0-SNAPSHOT: 
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.buildsupport:buildsupport:3.0-SNAPSHOT: 
checking for updates from codehaus.snapshots
[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
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/shitty-maven-plugin/1.0-alpha-3/shitty-maven-plugin-1.0-alpha-3.pom
16K downloaded
Downloading: 
http://repo.exist.com/maven2/org/codehaus/mojo/shitty-maven-plugin/1.0-alpha-3/shitty-maven-plugin-1.0-alpha-3.jar
106K downloaded
[INFO] [genesis:validate-configuration {execution: default}]
[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 openqa-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 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 openqa-snapshots
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion failed 
with message:
Detected JDK Version: 1.5.0-18 is not in the allowed range [1.6,).
[INFO] 
[ERROR] BUILD ERROR
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091012/logs-2100-jetty/
 
 
[INFO] Scanning for projects...
[INFO] 
[INFO] Building Geronimo TestSuite
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion failed 
with message:
Detected JDK

Re: [BUILD] branches/2.2: Failed - New activemq-webconsole dependency?

2009-10-12 Thread Ivan

The web console that required this dependency is from the ActiveMQ project,
not the default activemq console of Geronimo, and by default it is not
shipped with Geronimo binary build.  IMO, adding this dependency should not
affect us too much.

2009/10/9 Donald Woods 

> The latest activemq-webconsole artifact has a new dependency of -
>
>jivesoftware
>smack
>jar
>
>
> From its POM, it is "...an Open Source XMPP (Jabber) client library for
> instant messaging and presence..." and uses ASL 2.0.
>
> Do we really need this for the ActiveMQ web console or can we exclude it?
>
>
> -Donald
>
>
> ga...@apache.org wrote:
>
>> Geronimo Revision: 823517 built with tests included
>>  See the full build-0800.log file at
>> http://people.apache.org/builds/geronimo/server/binaries/2.2/20091009/build-0800.log
>>   See the unit test reports at
>> http://people.apache.org/builds/geronimo/server/binaries/2.2/20091009/unit-test-reports
>>  4K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//org/springframework/spring-jms/2.5.6/spring-jms-2.5.6.jar
>> Downloading:
>> http://oss.sonatype.org/content/repositories/jetty-with-staging//org/springframework/spring-jms/2.5.6/spring-jms-2.5.6.jar
>> Downloading:
>> http://repo.exist.com/maven2/org/springframework/spring-jms/2.5.6/spring-jms-2.5.6.jar
>> 190K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//commons-pool/commons-pool/1.4/commons-pool-1.4.jar
>> Downloading:
>> http://oss.sonatype.org/content/repositories/jetty-with-staging//commons-pool/commons-pool/1.4/commons-pool-1.4.jar
>> Downloading:
>> http://repo.exist.com/maven2/commons-pool/commons-pool/1.4/commons-pool-1.4.jar
>> 85K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//org/springframework/spring-context-support/2.5.6/spring-context-support-2.5.6.jar
>> Downloading:
>> http://oss.sonatype.org/content/repositories/jetty-with-staging//org/springframework/spring-context-support/2.5.6/spring-context-support-2.5.6.jar
>> Downloading:
>> http://repo.exist.com/maven2/org/springframework/spring-context-support/2.5.6/spring-context-support-2.5.6.jar
>> 94K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//org/apache/activemq/activemq-pool/5.3.0/activemq-pool-5.3.0.jar
>> 37K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//rome/rome/0.8/rome-0.8.jar
>> Downloading:
>> http://oss.sonatype.org/content/repositories/jetty-with-staging//rome/rome/0.8/rome-0.8.jar
>> Downloading: http://repo.exist.com/maven2/rome/rome/0.8/rome-0.8.jar
>> 192K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//org/springframework/spring-webmvc/2.5.6/spring-webmvc-2.5.6.jar
>> Downloading:
>> http://oss.sonatype.org/content/repositories/jetty-with-staging//org/springframework/spring-webmvc/2.5.6/spring-webmvc-2.5.6.jar
>> Downloading:
>> http://repo.exist.com/maven2/org/springframework/spring-webmvc/2.5.6/spring-webmvc-2.5.6.jar
>> 392K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//xmlpull/xmlpull/1.1.3.4d_b4_min/xmlpull-1.1.3.4d_b4_min.jar
>> Downloading:
>> http://oss.sonatype.org/content/repositories/jetty-with-staging//xmlpull/xmlpull/1.1.3.4d_b4_min/xmlpull-1.1.3.4d_b4_min.jar
>> Downloading:
>> http://repo.exist.com/maven2/xmlpull/xmlpull/1.1.3.4d_b4_min/xmlpull-1.1.3.4d_b4_min.jar
>> 23K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//org/apache/activemq/activemq-xmpp/5.3.0/activemq-xmpp-5.3.0.jar
>> 171K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
>> Downloading:
>> http://oss.sonatype.org/content/repositories/jetty-with-staging//jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
>> Downloading:
>> http://download.java.net/maven/2/jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
>> Downloading:
>> http://repository.codehaus.org//jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
>> Downloading:
>> http://repo.exist.com/maven2/jivesoftware/smackx/3.1.0/smackx-3.1.0.jar
>> 502K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//jivesoftware/smack/3.1.0/smack-3.1.0.jar
>> Downloading:
>> http://oss.sonatype.org/content/repositories/jetty-with-staging//jivesoftware/smack/3.1.0/smack-3.1.0.jar
>> Downloading:
>> http://repo.exist.com/maven2/jivesoftware/smack/3.1.0/smack-3.1.0.jar
>> 278K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-staging-008//org/apache/activemq/activemq-console/5.3.0/activemq-console-5.3.0.jar
>> 85K downloaded
>> Downloading:
>> https://repository.apache.org/content/repositories/activemq-stagin

[jira] Commented: (GERONIMO-4900) MissingDependencyException while deploying EAR in Clustering Environment


[ 
https://issues.apache.org/jira/browse/GERONIMO-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764582#action_12764582
 ] 

Ashish Jain commented on GERONIMO-4900:
---

I was able to simulate this issue. While debugging I found that 
"default/ClusterTestEAR/1.0/ear" is being looked onto the master repository, 
cluster repository and repository of instance B. As it does not find it it 
throws a MissingDependencyException. The method being called to resolve this 
dependency is org.apache.geronimo.kernel.config.ConfigurationResolver.resolve.

Added similar breakpoints for WAR module but do not see 
"org.apache.geronimo.kernel.config.ConfigurationResolver.resolve" this method 
being called.

Is this a supported scenario to deploy an EAR?? Or this only works with a WAR 
module??

> MissingDependencyException while deploying EAR in Clustering Environment
> 
>
> Key: GERONIMO-4900
> URL: https://issues.apache.org/jira/browse/GERONIMO-4900
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.1.4
>Reporter: Amit puri
>Assignee: Ashish Jain
> Attachments: ClusterTestEAR.ear
>
>
> 1. Installed two geronimo instances A and B at different paths
> 2. Made the following changes to Geronimo A
>For var\config\config-substitutions.properties
>clusterNodeName=NODE --> clusterNodeName=NODE-A
>For var\config\config.xml, add the following contents to module: 
> org.apache.geronimo.configs/farming/2.1.4/car
> -
>  name="org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=NodeInfo,name=NODE-B"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-B
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> localhost
> 1109
> JMXConnector
> false
>   
> 
> -
> 3. Made the following changes to Geronimo B
>For var\config\config-substitutions.properties
>clusterNodeName=NODE --> clusterNodeName=NODE-B
>PortOffset=0 --> PortOffset=10
>For var\config\config.xml, add the following contents to module: 
> org.apache.geronimo.configs/farming/2.1.4/car
> -
>  name="org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=NodeInfo,name=NODE-A"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-A
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> localhost
> 1099
> JMXConnector
> false
>   
> 
> -
> 4. Started both Geronimo A and B
> 5. Ran the following commands in Geronimo_A_Path\bin
>deploy --user system --password manager start 
> org.apache.geronimo.configs/farming/2.1.4/car
>deploy --user system --password manager --port 1109 start 
> org.apache.geronimo.configs/farming/2.1.4/car
> 6. Deployed one sample ClusterTestEAR.ear in Geronimo_A_Path\bin
> deploy --user system --password manager deploy --targets  
> org.apache.geronimo.configs/farming/2.1.4/car?ServiceModule=org.apache.geronimo.configs/farming/2.1.4/car,j2eeType=ConfigurationStore,name=MasterConfigurationStore
>  PATH_SAMPLE\ClusterTestEAR.ear
> Output:
> A) Errors in Geronimo A geronimo.log
>  INFO  [BasicClusterConfigurationStoreClient] Upload of configuration 
> [default/ClusterTestEAR_G_SLAVE/1.0/ear] - [File(s) transferred to server.  
> Resuming deployment operation.]
>  INFO  [BasicClusterConfigurationController] Exception while starting 
> configuration [default/Cluster

[jira] Assigned: (GERONIMO-4900) MissingDependencyException while deploying EAR in Clustering Environment