[jira] [Closed] (GERONIMO-5803) EBA cannot work after server restart

2011-05-12 Thread Tina Li (JIRA) 

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

Tina Li closed GERONIMO-5803.
-


Verified on build 2011.05.11-14:06:04.476+0800-3.0-SNAPSHOT 

 EBA cannot work after server restart
 

 Key: GERONIMO-5803
 URL: https://issues.apache.org/jira/browse/GERONIMO-5803
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 3.0-M2, 3.0
 Environment: windows 7
Reporter: LiWenQin
Assignee: Rex Wang
 Fix For: 3.0

 Attachments: CounterApp_1.0.0.eba


 1.deploy CounterApp_1.0.0.eba through Deployer Portlet.
 2.There is a copy CounterApp_1.0.0.eba in repository.
 3. In the cache, there are CounterApp, CounterWebBundle, 
 CounterServiceBundle, CounterWorldBundle and their states are all Active in 
 the OSGi Portlet
 4. We can access http://localhost:8080/CounterWebBundle/CounterServlet.
 5. hard stop the server.
 6. In the OSGi Portlet,  states of CounterWebBundle, CounterServiceBundle, 
 CounterWorldBundle are Resolved (CounterApp is Active) so that EBA cannot 
 work. 
 We cannot access url 
 http://localhost:8080/CounterWebBundle/CounterServlet.
 7. In the Application EBAs Portlet, state of 
 application/CounterApp/1.0.0/eba is running but the app does not work. 
 Stop application/CounterApp/1.0.0/eba in the Application EBAs Portlet 
 will remove CounterApp in OSGi Portlet but not remove other three related 
 bundles.
 (CounterApp EBA will work well after normal stop.)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

2011-05-12 Thread Jarek Gawor 
Geronimo Revision: 1102134 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110512/build-2000.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110512/unit-test-reports
 
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.FileProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.FileProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.FileProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.FileProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@68b868b8
Downloading: 
http://repo2.maven.org/maven2/net/sourceforge/serp/serp/1.11.0/serp-1.11.0.pom

[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.FileProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@68b868b8
Downloading: 
http://repo2.maven.org/maven2/org/apache/openjpa/openjpa/1.2.2/openjpa-1.2.2.jar
Downloading: 
http://repo2.maven.org/maven2/net/sourceforge/serp/serp/1.11.0/serp-1.11.0.jar


[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/openjpa/geronimo-persistence-jpa10/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/openjpa/geronimo-persistence-jpa10/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/openjpa/geronimo-persistence-jpa10/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/openjpa/geronimo-persistence-jpa10/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test {execution: default-test}]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.FileProfileActivator@68b868b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@68b868b8
[INFO] Surefire report directory: 
/home/geronimo/geronimo/2.2/plugins/openjpa/geronimo-persistence-jpa10/target/surefire-reports

---
 T E S T S
---
Running

[jira] [Commented] (GERONIMO-4576) Make persistence exceptions more visible to client

2011-05-12 Thread Vamsavardhana Reddy (JIRA) 

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

Vamsavardhana Reddy commented on GERONIMO-4576:
---

I see that 2.2 revs 1097555 and 1097965 are also related to this JIRA.

 Make persistence exceptions more visible to client
 --

 Key: GERONIMO-4576
 URL: https://issues.apache.org/jira/browse/GERONIMO-4576
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: persistence
Affects Versions: 2.2
 Environment: Linux, Windows
Reporter: Joe Bohn
Priority: Minor
 Fix For: Wish List


 See http://issues.apache.org/jira/browse/GERONIMO-3907  for details of the 
 original problem.   That core problem was resolved.  However, upon resolution 
 it was mentioned that it would be beneficial to report more specific failure 
 information back to the client.  From GERONIMO-3907:
 Ralf Baumhof - 06/May/08 06:17 AM
 Today if have tested the new Geronimo release 2.1.1 (published on 
 28.04.2008). The problem is now fixed. If the server gets an error on trying 
 a commit, this error is now thrown to the web bean.
 Exception text:
 javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, 
 presumably because setRollbackOnly was called during a synchronization: 
 Unable to commit: transaction marked for rollback Root Cause: 
 javax.transaction.TransactionRolledbackException : Transaction was rolled 
 back, presumably because setRollbackOnly was called during a synchronization: 
 Unable to commit: transaction marked for rollback
 Unfortunately there is no proper root cause attached to the exception. So the 
 cause can only be seen in the server console, but can not be reported to the 
 user. It would be very nice if you could change this in a later release.
 Thanks for your help.
 Vincent MATHON - 06/Nov/08 02:03 AM
 I agree that exceptions on the server side should not be thrown to the client 
 side since such exceptions types might not be known by the client. However, 
 for unit testing purpose, it is useful to attach the root cause to the 
 RollBackException. I have modified a few lines in 
 org.apache.geronimo.transaction.manager.TransactionImpl.java to attach the 
 root cause in case of RollBackException and it works for my unit testing 
 purpose (I have not enough background on the java transaction architecture 
 topic to submit a patch for production). It would be great to define a 
 configuration parameter that permits to provide the root cause to the client 
 and keep the current behaviour that does not by default.
 Geoff Callender - 22/Dec/08 03:36 AM
 It's useful for more than unit testing - it's essential to be able to inform 
 the client what's wrong with the request. I've added some examples of this to 
 https://issues.apache.org/jira/browse/OPENEJB-782 .

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (GERONIMO-5835) Support web service deployment in car-maven-plugin

2011-05-12 Thread Shawn Jiang (JIRA) 

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

Shawn Jiang reassigned GERONIMO-5835:
-

Assignee: Shawn Jiang  (was: Ivan)

 Support web service deployment in car-maven-plugin
 --

 Key: GERONIMO-5835
 URL: https://issues.apache.org/jira/browse/GERONIMO-5835
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: car-maven-plugin, webservices
Affects Versions: 3.0
Reporter: Ivan
Assignee: Shawn Jiang

 Seems that we do not support WDSL generation in the car-maven-plugin, while 
 the latest UDDI war package uses web service.
 The exception below is thrown while compiling uddi-tomcat
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal org.apache.geronimo.buildsupport:car-maven-plugin:3.0-SNAPSHOT:package 
 (default-package) on project uddi-tomcat: could not package plugin
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
   at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
   at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
   at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
   at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:600)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
 Caused by: org.apache.maven.plugin.MojoExecutionException: could not package 
 plugin
   at 
 org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:233)
   at 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
   ... 19 more
 Caused by: org.apache.geronimo.common.DeploymentException: Wsdl generator not 
 found
   at 
 org.apache.geronimo.axis2.builder.Axis2Builder.getWsdlGenerator(Axis2Builder.java:195)
   at 
 org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.java:220)
   at 
 org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSServiceBuilder.java:188)
   at 
 org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:614)
   at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:716)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:600)
   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:872)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
   at 
 org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:526)
   at 
 org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:341)
   at

[jira] [Reopened] (GERONIMO-5288) Cannot use @EJB in java ee component(servlet, JSF) to inject ejb object

2011-05-12 Thread Forrest Xia (JIRA) 

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

Forrest Xia reopened GERONIMO-5288:
---


this problem appears again in build 20110511.

 Cannot use @EJB in java ee component(servlet, JSF) to inject ejb object
 ---

 Key: GERONIMO-5288
 URL: https://issues.apache.org/jira/browse/GERONIMO-5288
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Web Profile
Affects Versions: 3.0
Reporter: Forrest Xia
Assignee: Ivan
 Fix For: 3.0


 I tried two new java ee 6 samples jpa20demo-javaee6 and ejbtimer-javaee6, 
 they both failed at injecting ejb object in JSF managed bean or servlet.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-5835) Support web service deployment in car-maven-plugin

2011-05-12 Thread Shawn Jiang (JIRA) 

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

Shawn Jiang updated GERONIMO-5835:
--

Attachment: 0001-adding-axis2-deployer-for-uddi-module.patch

a patch to enable the uddi-tomcat web service compile with  car-maven-plugin.


Because an bug of uddi itself.   I'll hold this patch until the uddi fix the 
problem.

 Support web service deployment in car-maven-plugin
 --

 Key: GERONIMO-5835
 URL: https://issues.apache.org/jira/browse/GERONIMO-5835
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: car-maven-plugin, webservices
Affects Versions: 3.0
Reporter: Ivan
Assignee: Shawn Jiang
 Attachments: 0001-adding-axis2-deployer-for-uddi-module.patch


 Seems that we do not support WDSL generation in the car-maven-plugin, while 
 the latest UDDI war package uses web service.
 The exception below is thrown while compiling uddi-tomcat
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal org.apache.geronimo.buildsupport:car-maven-plugin:3.0-SNAPSHOT:package 
 (default-package) on project uddi-tomcat: could not package plugin
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
   at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
   at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
   at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
   at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:600)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
 Caused by: org.apache.maven.plugin.MojoExecutionException: could not package 
 plugin
   at 
 org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:233)
   at 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
   ... 19 more
 Caused by: org.apache.geronimo.common.DeploymentException: Wsdl generator not 
 found
   at 
 org.apache.geronimo.axis2.builder.Axis2Builder.getWsdlGenerator(Axis2Builder.java:195)
   at 
 org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.java:220)
   at 
 org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSServiceBuilder.java:188)
   at 
 org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:614)
   at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:716)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:600)
   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:872)
   at

[jira] [Closed] (GERONIMO-5929) org.apache.geronimo.kernel.config.LiefcycleException when starting Hudson.war on G3.0

2011-05-12 Thread Tina Li (JIRA) 

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

Tina Li closed GERONIMO-5929.
-

   Resolution: Fixed
Fix Version/s: 3.0

The error was cause by incorrect deployment plan, after using the new plan from 
Michael, hudson.war can be deployed successfully.

 org.apache.geronimo.kernel.config.LiefcycleException when starting Hudson.war 
 on G3.0
 -

 Key: GERONIMO-5929
 URL: https://issues.apache.org/jira/browse/GERONIMO-5929
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 3.0
 Environment: Sun JDK 1.6.0_21, GBuild 04/19
Reporter: Chi Runhua
Assignee: Shawn Jiang
 Fix For: 3.0

 Attachments: hudson_DD.xml, hudson_DD.xml


 Hudson.war can be deployed successfully, however, it fails to start because 
 of the following exception:
 2011-04-22 10:26:13,093 ERROR [DeploymentPortlet] The application was not 
 successfully started.
 start of hudson/hudson/1.384/war failed
 org.apache.geronimo.kernel.config.LifecycleException: start of 
 hudson/hudson/1.384/war failed
   at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:718)
   at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:681)
   at 
 org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67)
   at java.lang.Thread.run(Thread.java:619)
 Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown 
 start exception
   at 
 org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:521)
   at 
 org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:226)
   at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:702)
   ... 3 more
 Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: 
 Configuration hudson/hudson/1.384/war failed to start due to the following 
 reasons:
   The service 
 J2EEApplication=null,j2eeType=WebModule,name=hudson/hudson/1.384/war did not 
 start because ContainerBase.addChild: start: 
 org.apache.catalina.LifecycleException: java.io.IOException: Context did not 
 start for an unknown reason
 java.lang.IllegalStateException: ContainerBase.addChild: start: 
 org.apache.catalina.LifecycleException: java.io.IOException: Context did not 
 start for an unknown reason
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:816)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:787)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583)
   at 
 org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:310)
   at 
 org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:569)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:975)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546)
   at 
 org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110)
   at 
 org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145)
   at 
 org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119)
   at 
 org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175)
   at 
 org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
   at 
 org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:301)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546)
   at 
 org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110)
   at 
 org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145)
   at 
 org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119)
   at

[jira] [Closed] (GERONIMO-5892) An error window pops up when clicking on JNDI viewer

2011-05-12 Thread Tina Li (JIRA) 

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

Tina Li closed GERONIMO-5892.
-


Verified on build 2011.05.11-14:06:04.476+0800-3.0-SNAPSHOT   

 An error window pops up when clicking on JNDI viewer
 

 Key: GERONIMO-5892
 URL: https://issues.apache.org/jira/browse/GERONIMO-5892
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 3.0
 Environment: 2011-04-07 Tomcat build
Reporter: Chi Runhua
Assignee: Shawn Jiang
Priority: Minor
 Attachments: GERONIMO-5892.patch, GERONIMO-5892.patch, 
 JNDI_Viewer_Error.png


 2011-04-08 13:29:11,955 WARN  [BaseCallMarshaller] --Erroring: batchId[1] 
 message[org.apache.geronimo.kernel.NoSuchAttributeException: Unknown 
 attribute componentContext in gbean 
 org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car?EJBModule=org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car,J2EEApplication=null,j2eeType=StatelessSessionBean,name=ejb/mgmt/MEJB]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (GERONIMO-5924) Servlet.service() for servlet WARModules threw exception java.lang.SecurityException

2011-05-12 Thread Tina Li (JIRA) 

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

Tina Li closed GERONIMO-5924.
-


The error was cause by incorrect deployment plan, after using the new plan from 
Michael, hudson.war can be deployed successfully.

 Servlet.service() for servlet WARModules threw exception  
 java.lang.SecurityException
 -

 Key: GERONIMO-5924
 URL: https://issues.apache.org/jira/browse/GERONIMO-5924
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console, security
Affects Versions: 3.0
 Environment: 04/19 build, Sun JDK 1.6.0_21+Win7
Reporter: Chi Runhua
Assignee: Shenghao Fang
Priority: Minor
 Attachments: hudson-realm.xml, hudson_DD.xml


 After hudson.war was deployed successfully, click WAR on navigation menu. The 
 page failed to render.
 2011-04-21 14:16:48,568 ERROR [[WARModules]] Servlet.service() for servlet 
 WARModules threw exception
 java.lang.SecurityException: Invalid signature file digest for Manifest main 
 attributes
   at 
 sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:221)
   at 
 sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:176)
   at java.util.jar.JarVerifier.processEntry(JarVerifier.java:245)
   at java.util.jar.JarVerifier.update(JarVerifier.java:199)
   at java.util.jar.JarFile.initializeVerifier(JarFile.java:323)
   at java.util.jar.JarFile.getInputStream(JarFile.java:388)
   at 
 org.apache.geronimo.system.configuration.RepositoryConfigurationStore.loadConfigurationInfo(RepositoryConfigurationStore.java:497)
   at 
 org.apache.geronimo.system.configuration.RepositoryConfigurationStore.listConfigurations(RepositoryConfigurationStore.java:455)
   at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.listConfigurations(SimpleConfigurationManager.java:221)
   at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.listConfigurations(SimpleConfigurationManager.java:193)
   at 
 org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:225)
   at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348)
   at javax.portlet.GenericPortlet.render(GenericPortlet.java:253)
   at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
   at 
 org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163)
   at 
 org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91)
   at 
 org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105)
   at 
 org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340)
   at 
 org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518)
   at 
 org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233)
   at 
 org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117)
   at 
 org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157)
   at 
 org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165)
   at 
 jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518)
   at

[jira] [Reopened] (GERONIMO-5855) Simplify EJB Deployment

2011-05-12 Thread Shawn Jiang (JIRA) 

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

Shawn Jiang reopened GERONIMO-5855:
---


 Simplify EJB Deployment
 ---

 Key: GERONIMO-5855
 URL: https://issues.apache.org/jira/browse/GERONIMO-5855
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: OpenEJB
Reporter: David Blevins
Assignee: David Blevins
 Fix For: 3.0

 Attachments: SimplifyEjbModuleCreation.diff


 Seems like we're always having issues due to changes in the OpenEJB 
 DeploymentLoader code, so I've attempted to extract the parts that Geronimo 
 needs.  Hopefully this can provide some stability and maybe even help with 
 tuning deployment to Geronimo's needs in the future.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-5855) Simplify EJB Deployment

2011-05-12 Thread Shawn Jiang (JIRA) 

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

Shawn Jiang commented on GERONIMO-5855:
---

One solution is to extract the WEB-INF/lib/xxx.jar  in the war  and then scan 
descriptor/annotations in those jars too. I'm not sure if it's the best way 
to go.

 Simplify EJB Deployment
 ---

 Key: GERONIMO-5855
 URL: https://issues.apache.org/jira/browse/GERONIMO-5855
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: OpenEJB
Reporter: David Blevins
Assignee: David Blevins
 Fix For: 3.0

 Attachments: SimplifyEjbModuleCreation.diff


 Seems like we're always having issues due to changes in the OpenEJB 
 DeploymentLoader code, so I've attempted to extract the parts that Geronimo 
 needs.  Hopefully this can provide some stability and maybe even help with 
 tuning deployment to Geronimo's needs in the future.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

2011-05-12 Thread Jarek Gawor 
Geronimo Revision: 1102169 built with tests included
 
See the full build-0200.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110512/build-0200.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110512
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 232 minutes 46 seconds
[INFO] Finished at: Thu May 12 05:57:45 EDT 2011
[INFO] Final Memory: 314M/829M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110512/logs-0200-tomcat/
 
[INFO] Running security-testsuite.security
[INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 61.762 
sec  FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110512/logs-0200-jetty/
 
[INFO] Running security-testsuite-generic-auth-test
[INFO] Tests run: 4, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.45 sec 
 FAILURE!
 
Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110512/samples-0200.log
 
Build status: FAILED

Re: LinkageError woes

2011-05-12 Thread Kevan Miller 

On May 10, 2011, at 11:01 PM, David Blevins wrote:

 
 On May 10, 2011, at 6:57 PM, David Blevins wrote:
 
 I have a hunch that eagerly loading annotations *and* enums might do the 
 trick.  Going to see if that is the case as that might give us more 
 information about the issue and potentially a workaround that might be one 
 we can stomach.  Loading all the classes eagerly is not ok, but eagerly 
 loading annotation and enum classes might be livable till we can find the 
 real issue.
 
 Looks like eagerly loading all the application's annotations and enums twice 
 does the trick.  The first time fails with the LinkageError and the second 
 time works.
 
 Currently performing some magic in debugger with evaluating expressions to 
 get this accomplished.  Not going to codify it just yet, but if we wanted 
 this as a hack as an implemented workaround we'd need to use ASM to scrape 
 and get a list of all annotation and enum classes, put that data in perhaps a 
 gbean that is setup to load on app startup with a dependency on the app 
 classloader, then have that gbean do the double load.  The xbean-finder code 
 doesn't currently have the ability to list annotations and enums -- we'd have 
 to add it or scrape again.
 
 Hopefully we can find the real issue and not have to do that.

So, I swapped a bit more state back in (how quickly I forget). ClassFile 
transformation driven by OpenJPA is causing this error. I re-opened our 
original Jira. I created an Equinox bug report and they've created a patch, 
which seems to fix our problem. 

There will be the question of how we pick up the fix within Geronimo. The patch 
is on Equinox 3.7 -- something we probably want to pick up anyway.

--kevan

[jira] [Commented] (GERONIMODEVTOOLS-672) Error occurs in geronimo deployment plan when refactoring projects

2011-05-12 Thread Yi Xiao (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032402#comment-13032402
 ] 

Yi Xiao commented on GERONIMODEVTOOLS-672:
--

Has been resolved with GERONIMODEVTOOLS-670

 Error occurs in geronimo deployment plan when refactoring projects
 --

 Key: GERONIMODEVTOOLS-672
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-672
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
 Environment: Eclipse 3.6
Reporter: Wang Guang Zhe
Assignee: Delos Dai
 Fix For: 3.0

 Attachments: end.png, error.JPG, middle.png, modify.png, new.png, 
 upper.png


 Different Errors occurs in geronimo deployment plan when refactoring projects 
 in different ways which will be showed in pictures below.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-672) Error occurs in geronimo deployment plan when refactoring projects

2011-05-12 Thread Yi Xiao (JIRA) 

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

Yi Xiao resolved GERONIMODEVTOOLS-672.
--

Resolution: Fixed

 Error occurs in geronimo deployment plan when refactoring projects
 --

 Key: GERONIMODEVTOOLS-672
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-672
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
 Environment: Eclipse 3.6
Reporter: Wang Guang Zhe
Assignee: Delos Dai
 Fix For: 3.0

 Attachments: end.png, error.JPG, middle.png, modify.png, new.png, 
 upper.png


 Different Errors occurs in geronimo deployment plan when refactoring projects 
 in different ways which will be showed in pictures below.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-4576) Make persistence exceptions more visible to client

2011-05-12 Thread Vamsavardhana Reddy (JIRA) 

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

Vamsavardhana Reddy commented on GERONIMO-4576:
---

I notice that revs 1097555 and 1097965 are once again masking the original 
persistence exception and putting a SetRollbackOnlyException() as the cause. To 
give an example, with rev 1076770 applied in my code, I am getting the 
following exception report:

REPORT-1:

org.apache.jasper.JasperException: javax.ejb.EJBTransactionRolledbackException: 
Transaction was rolled back, presumably because setRollbackOnly was called 
during a synchronization: Unable to commit: transaction marked for rollback

root cause:
javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, 
presumably because setRollbackOnly was called during a synchronization: Unable 
to commit: transaction marked for rollback

root cause:
javax.transaction.RollbackException: Unable to commit: transaction marked for 
rollback

root cause:
openjpa-1.2.2-r422266:898935 fatal general error 
org.apache.openjpa.persistence.PersistenceException: The transaction has been 
rolled back.  See the nested exceptions for details on the errors that occurred.

...

--
With revs 1076770, 1097555 and 1097965 applied in my code, I am getting the 
following exception report in the same case (notice that the persistence 
exception is lost):

REPORT-2:

org.apache.jasper.JasperException: javax.ejb.EJBTransactionRolledbackException: 
Transaction was rolled back, presumably because setRollbackOnly was called 
during a synchronization: Unable to commit: transaction marked for rollback

root cause:
javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, 
presumably because setRollbackOnly was called during a synchronization: Unable 
to commit: transaction marked for rollback

root cause:
javax.transaction.RollbackException: Unable to commit: transaction marked for 
rollback

root cause:
org.apache.geronimo.transaction.manager.SetRollbackOnlyException: 
setRollbackOnly() called.  See stacktrace for origin


 Make persistence exceptions more visible to client
 --

 Key: GERONIMO-4576
 URL: https://issues.apache.org/jira/browse/GERONIMO-4576
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: persistence
Affects Versions: 2.2
 Environment: Linux, Windows
Reporter: Joe Bohn
Priority: Minor
 Fix For: Wish List


 See http://issues.apache.org/jira/browse/GERONIMO-3907  for details of the 
 original problem.   That core problem was resolved.  However, upon resolution 
 it was mentioned that it would be beneficial to report more specific failure 
 information back to the client.  From GERONIMO-3907:
 Ralf Baumhof - 06/May/08 06:17 AM
 Today if have tested the new Geronimo release 2.1.1 (published on 
 28.04.2008). The problem is now fixed. If the server gets an error on trying 
 a commit, this error is now thrown to the web bean.
 Exception text:
 javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, 
 presumably because setRollbackOnly was called during a synchronization: 
 Unable to commit: transaction marked for rollback Root Cause: 
 javax.transaction.TransactionRolledbackException : Transaction was rolled 
 back, presumably because setRollbackOnly was called during a synchronization: 
 Unable to commit: transaction marked for rollback
 Unfortunately there is no proper root cause attached to the exception. So the 
 cause can only be seen in the server console, but can not be reported to the 
 user. It would be very nice if you could change this in a later release.
 Thanks for your help.
 Vincent MATHON - 06/Nov/08 02:03 AM
 I agree that exceptions on the server side should not be thrown to the client 
 side since such exceptions types might not be known by the client. However, 
 for unit testing purpose, it is useful to attach the root cause to the 
 RollBackException. I have modified a few lines in 
 org.apache.geronimo.transaction.manager.TransactionImpl.java to attach the 
 root cause in case of RollBackException and it works for my unit testing 
 purpose (I have not enough background on the java transaction architecture 
 topic to submit a patch for production). It would be great to define a 
 configuration parameter that permits to provide the root cause to the client 
 and keep the current behaviour that does not by default.
 Geoff Callender - 22/Dec/08 03:36 AM
 It's useful for more than unit testing - it's essential to be able to inform 
 the client what's wrong with the request. I've added some examples of this to 
 https://issues.apache.org/jira/browse/OPENEJB-782 .

--
This message is automatically generated by

[jira] [Commented] (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime

2011-05-12 Thread Yi Xiao (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032412#comment-13032412
 ] 

Yi Xiao commented on GERONIMODEVTOOLS-670:
--

Tina, about the openejb-jar-2.2.xsd's validation issue, Janet has consulted the 
openejb's team, I will trace it.

 Geronimo deployment plan doesn't be created when creating projects using the 
 Geronimo 2.2 as the target runtime
 ---

 Key: GERONIMODEVTOOLS-670
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
 Environment: OS: Windows XP SP3
 JDK: IBM JDK 6
 Eclipse: 3.6
Reporter: Wang Guang Zhe
Assignee: Delos Dai
 Fix For: 3.0

 Attachments: patch.patch


 I created an web, an ejb and an ear projects using  the Geronimo 2.2 as the 
 target runtime, the geronimo deployment plans which should be in these 
 projects don't exist.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-744) More flexible no-redeployment option

2011-05-12 Thread Jarek Gawor (JIRA) 
More flexible no-redeployment option


 Key: GERONIMODEVTOOLS-744
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-744
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor


It would be nice to let user specify a list of file extensions that do not 
cause the application to be re-deployed if one of the files with a matching 
extension is modified. Instead the given file would be simply copied and the 
application left running as is.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-745) Switching JRE via server configuration causes sever startup errors

2011-05-12 Thread Jarek Gawor (JIRA) 
Switching JRE via server configuration causes sever startup errors
--

 Key: GERONIMODEVTOOLS-745
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-745
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor


There are 2 problems here:

1) Switching JRE types or versions via server configuration - Runtime 
Environment - JRE causes the server not to start up anymore. The path to JRE 
doesn't seem to get updated in VM arguments.

2) Switching between JRE definition that really points to JDK directory and not 
JRE directory can also cause server startup problems.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-746) Invalid module state after server is stopped

2011-05-12 Thread Jarek Gawor (JIRA) 
Invalid module state after server is stopped


 Key: GERONIMODEVTOOLS-746
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-746
 Project: Geronimo-Devtools
  Issue Type: Improvement
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor


Deployed module remain in started state even after the server is stopped.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMODEVTOOLS-744) More flexible no-redeployment option

2011-05-12 Thread David Jencks (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032470#comment-13032470
 ] 

David Jencks commented on GERONIMODEVTOOLS-744:
---

I think this is to support in place editing of jsps, html, etc.  What happens 
if you deploy an exploded wab using a reference:file:// url?  I would not 
expect anything to get copied into the server due to the reference: url.  Does 
the bundle pick up live changes to the resources?  Do jsps work?

 More flexible no-redeployment option
 

 Key: GERONIMODEVTOOLS-744
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-744
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor

 It would be nice to let user specify a list of file extensions that do not 
 cause the application to be re-deployed if one of the files with a matching 
 extension is modified. Instead the given file would be simply copied and the 
 application left running as is.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMODEVTOOLS-745) Switching JRE via server configuration causes sever startup errors

2011-05-12 Thread Jarek Gawor (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032477#comment-13032477
 ] 

Jarek Gawor commented on GERONIMODEVTOOLS-745:
--

In revision 1102362 I committed changes that should address both of these 
issues. The GERONIMO_HOME and JRE_HOME information is fill-out at the last 
possible moment before starting the server.


 Switching JRE via server configuration causes sever startup errors
 --

 Key: GERONIMODEVTOOLS-745
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-745
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor

 There are 2 problems here:
 1) Switching JRE types or versions via server configuration - Runtime 
 Environment - JRE causes the server not to start up anymore. The path to JRE 
 doesn't seem to get updated in VM arguments.
 2) Switching between JRE definition that really points to JDK directory and 
 not JRE directory can also cause server startup problems.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMODEVTOOLS-746) Invalid module state after server is stopped

2011-05-12 Thread Jarek Gawor (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032563#comment-13032563
 ] 

Jarek Gawor commented on GERONIMODEVTOOLS-746:
--

In revision 1102407 I committed a change that sets the module state of all 
deployed modules to STOPPED state if the server is stopped.


 Invalid module state after server is stopped
 

 Key: GERONIMODEVTOOLS-746
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-746
 Project: Geronimo-Devtools
  Issue Type: Improvement
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor

 Deployed module remain in started state even after the server is stopped.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-746) Invalid module state after server is stopped

2011-05-12 Thread Jarek Gawor (JIRA) 

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

Jarek Gawor resolved GERONIMODEVTOOLS-746.
--

   Resolution: Fixed
Fix Version/s: 3.0

 Invalid module state after server is stopped
 

 Key: GERONIMODEVTOOLS-746
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-746
 Project: Geronimo-Devtools
  Issue Type: Improvement
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor
 Fix For: 3.0


 Deployed module remain in started state even after the server is stopped.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-745) Switching JRE via server configuration causes sever startup errors

2011-05-12 Thread Jarek Gawor (JIRA) 

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

Jarek Gawor resolved GERONIMODEVTOOLS-745.
--

   Resolution: Fixed
Fix Version/s: 3.0

 Switching JRE via server configuration causes sever startup errors
 --

 Key: GERONIMODEVTOOLS-745
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-745
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor
 Fix For: 3.0


 There are 2 problems here:
 1) Switching JRE types or versions via server configuration - Runtime 
 Environment - JRE causes the server not to start up anymore. The path to JRE 
 doesn't seem to get updated in VM arguments.
 2) Switching between JRE definition that really points to JDK directory and 
 not JRE directory can also cause server startup problems.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-5958) Repeated hot deployment of EBA fails

2011-05-12 Thread Jarek Gawor (JIRA) 
Repeated hot deployment of EBA fails


 Key: GERONIMO-5958
 URL: https://issues.apache.org/jira/browse/GERONIMO-5958
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Hot Deploy Dir
Affects Versions: 3.0
Reporter: Jarek Gawor


Repeated hot deployment of EBA file fails with NPE. Here's how to reproduce:

1) Start server
2) Drop .eba file into $GERONIMO_HOME/deploy directory.
3) Wait for the eba to be deployed and then remove the .eba from the deploy/ 
directory.
4) Wait 30s or so and drop the .eba file into deploy/ directory again.

At that time the .eba fails to deploy and the following error message is 
visible on the console:

2011-05-12 14:56:01,051 ERROR [DirectoryMonitor] Error during hot deploymen
java.lang.NullPointerException
at 
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:59)
at 
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:51)
at 
org.apache.geronimo.deployment.hot.DirectoryMonitor.doRemoves(DirectoryMonitor.java:183)
at 
org.apache.geronimo.deployment.hot.DirectoryMonitor.scanDirectory(DirectoryMonitor.java:258)
at 
org.apache.geronimo.deployment.hot.DirectoryMonitor.run(DirectoryMonitor.java:219)
at java.lang.Thread.run(Thread.java:662)


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-747) Undeploy module while server is stopped

2011-05-12 Thread Jarek Gawor (JIRA) 
Undeploy module while server is stopped
---

 Key: GERONIMODEVTOOLS-747
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-747
 Project: Geronimo-Devtools
  Issue Type: Improvement
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor


In Eclipse it is possible to remove a module from the server while the server 
is stopped. However, in GEP this does not translate into actually undeploying 
the module from the server (for example when the server is started the next 
time). So we need to figure it out how we want to handle this case.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-5959) Port Karaf's client command line tool to Geronimo

2011-05-12 Thread Jarek Gawor (JIRA) 
Port Karaf's client command line tool to Geronimo
---

 Key: GERONIMO-5959
 URL: https://issues.apache.org/jira/browse/GERONIMO-5959
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: general
Affects Versions: 3.0
Reporter: Jarek Gawor


Karaf's client command line tool is essentially a ssh client and it would be 
nice to support it in Geronimo since not all machines might have ssh client 
installed.



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-5861) Update a bundle within an EBA

2011-05-12 Thread Jarek Gawor (JIRA) 

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

Jarek Gawor commented on GERONIMO-5861:
---

Right now when a bundle is updated within EBA, the changes will be gone once 
the server is started with --clean option or the EBA is restarted. I think we 
need to make sure the changes are persistent.


 Update a bundle within an EBA
 -

 Key: GERONIMO-5861
 URL: https://issues.apache.org/jira/browse/GERONIMO-5861
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: deployment
Reporter: Han Hong Fang
Assignee: Rex Wang

 Some EBAs might be huge and contain many bundles. Right now whenever a bundle 
 in a EBA is updated, the entire EBA is re-assembled and re-deployed to the 
 server. That of course, can be expensive if the application is big. So it 
 would be nice if only the updated bundle was re-deployed to the server.
 This JIRA is for probably required changes to the server's deployer code for 
 deploying  managing bundles within or outside of EBAs. And GEP JIRA is here: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-718

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

2011-05-12 Thread Jarek Gawor 
Geronimo Revision: 1102505 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110513/build-2000.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110513/unit-test-reports
 
Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/shared/maven-downloader/1.1/maven-downloader-1.1.pom

[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@14b814b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@b740b74
Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/shared/maven-shared-components/4/maven-shared-components-4.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/maven-artifact-manager/2.0/maven-artifact-manager-2.0.pom

[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@14b814b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@b740b74
Downloading: 
http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.4.1/plexus-utils-1.4.1.pom

[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@14b814b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@b740b74
Downloading: 
http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.3/plexus-velocity-1.1.3.pom

[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@14b814b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@b740b74
Downloading: 
http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.5/plexus-components-1.1.5.pom

Downloading: 
http://repo2.maven.org/maven2/commons-collections/commons-collections/2.0/commons-collections-2.0.pom

[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@14b814b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@b740b74
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@14b814b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@b740b74
Downloading: 
http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-resources/1.0-alpha-4/plexus-resources-1.0-alpha-4.pom

[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@14b814b8
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.OperatingSystemProfileActivator@b740b74
Downloading: 
http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.7/plexus-components-1.1.7.pom

Downloading: 
http://repo2.maven.org/maven2/commons-collections/commons-collections/2.0/commons-collections-2.0.jar
Downloading: 
http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.4.1/plexus-utils-1.4.1.jar
Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.0/maven-common-artifact-filters-1.0.jar

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/shared/maven-plugin-testing-harness/1.1/maven-plugin-testing-harness-1.1.jar

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/shared/maven-downloader/1.1/maven-downloader-1.1.jar



Downloading: 
http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.3/plexus-velocity-1.1.3.jar

Downloading: 
http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-resources/1.0-alpha-4/plexus-resources-1.0-alpha-4.jar

[INFO] Setting property: classpath.resource.loader.class = 
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
Downloading: 
http://repo2.maven.org/maven2/org/apache/apache-jar-resource-bundle/1.4/apache-jar-resource-bundle-1.4.jar

[ERROR] ResourceManager : unable to find resource 'META-INF/DEPENDENCIES.vm' in 
any resource loader.
[INFO]