[jira] [Commented] (GERONIMO-6000) GBeanInstanceState related error happened and server can't be started
[ https://issues.apache.org/jira/browse/GERONIMO-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046354#comment-13046354 ] Tina Li commented on GERONIMO-6000: --- tried on build 2011.06.09-06:09:01.693+0800 using geronimo run,server startup successfully. GBeanInstanceState related error happened and server can't be started - Key: GERONIMO-6000 URL: https://issues.apache.org/jira/browse/GERONIMO-6000 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Assignee: Ivan Priority: Minor Fix For: 3.0 Attachments: geronimo.log 1.Using the build of Jun 8 2.Start server using command: startup.bat,then error happened 3.Start server using command: geronimo run,then error happened 4.geronimo.log file is attached for deatail -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6000) GBeanInstanceState related error happened and server can't be started
[ https://issues.apache.org/jira/browse/GERONIMO-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li closed GERONIMO-6000. - GBeanInstanceState related error happened and server can't be started - Key: GERONIMO-6000 URL: https://issues.apache.org/jira/browse/GERONIMO-6000 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Assignee: Ivan Priority: Minor Fix For: 3.0 Attachments: geronimo.log 1.Using the build of Jun 8 2.Start server using command: startup.bat,then error happened 3.Start server using command: geronimo run,then error happened 4.geronimo.log file is attached for deatail -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Opening up xbean svn access (Fwd: Jar listing performance)
On Jun 8, 2011, at 9:36 PM, David Blevins wrote: I and pretty much everyone with dual OpenEJB/Geronimo commit is likely way too busy to commit this patch (XBEAN-176). Ended up having to make CDI related change to xbean and cleared out this patch. We should still consider opening things up though. I wonder in general if we shouldn't just open up the xbean section of the repo since it is more or less a commons area. Would be nice to open it up to at least OpenEJB. I.e. we just tweak the svn auth file like so: [/geronimo/xbean/] @geronimo = rw @openejb = rw Could potentially open it to OpenWebBeans at some point later if it starts using xbean-finder. So far talk on the OWB side has always been lets move everything commons which I suppose we could do, but that seems like a lot of pointless refactoring and repackaging and moving when we could just add a couple lines to the svn auth file. Thoughts? -David Begin forwarded message: From: Romain Manni-Bucau rmannibu...@gmail.com Date: June 7, 2011 10:22:22 PM PDT To: d...@openejb.apache.org Subject: Re: Jar listing performance Reply-To: d...@openejb.apache.org In fact there are 2 kind of API for Jar/Zip: the ZipFile and the ZipInputStream (same for jars). If you use the inpout stream one ... you use an input stream so you read everything. If you use the file one you directly call native methods so under linux in particular it works better (i didn't test under windows but i hope it is the same). David said me we are using JarArchive: https://issues.apache.org/jira/browse/XBEAN-176 - Romain 2011/6/8 David Blevins david.blev...@gmail.com FYI, to Romain, regarding http://www.friendpaste.com/JU7WuKslKle9UaAL3r21M There might be caching going on in the first call that makes the second call go faster. We should check that angle. Maybe switch the order or loop the main code a couple times. -David
[jira] [Updated] (GERONIMODEVTOOLS-757) Karaf shell still working after stopped geronimo server through GEP and error happened when excute geronimo server related commands
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-757: - Attachment: 757.patch Tina, The patch is available. The root cause is G3 does not shutdown as before~ Karaf shell still working after stopped geronimo server through GEP and error happened when excute geronimo server related commands --- Key: GERONIMODEVTOOLS-757 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-757 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: geronimo server build: 2011.05.25-3.0 snapshot Gep version:Build id: 20110531125652 Eclipse:Helios Service Release 1 JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Priority: Minor Attachments: 757.patch 1.Start geronimo server using command: geronimo run 2.Create a dynamic web project named testWeb and create an html file named index.html and add the text Helloļ¼ inside the body section 3.Right-click this project and choose Run As--Run on server, create the server runtime using jdk 6 and geronimo 3.0 snapshot 4.Delete the created server and make sure the checkbox Delete running servers and Stop server(s) before deleting choosed when the Delete Server dialog pops up. 5.Then find the server has stopped but karaf shell still working. 6.Input geronimo server related commands such as deploy:list-modules,then error happened: Error executing command: GBean is not running: org.apache.geronimo.configs/conne ctor-deployer-1_6/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/con nector-deployer-1_6/3.0-SNAPSHOT/car,j2eeType=DeploymentConfigurer,name=RARConfi gurer -- 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: 1133791
Geronimo Revision: 1133791 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110609/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110609/unit-test-reports Downloading: http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-io/1.0-alpha-1/plexus-io-1.0-alpha-1.pom Downloading: http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-component-api/1.0-alpha-16/plexus-component-api-1.0-alpha-16.pom Downloading: http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-containers/1.0-alpha-16/plexus-containers-1.0-alpha-16.pom Downloading: http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.4.9/plexus-utils-1.4.9.pom Downloading: http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.4.9/plexus-utils-1.4.9.jar Downloading: http://repo2.maven.org/maven2/org/apache/maven/maven-archiver/2.3/maven-archiver-2.3.jar Downloading: http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-9/plexus-archiver-1.0-alpha-9.jar Downloading: http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-io/1.0-alpha-1/plexus-io-1.0-alpha-1.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar': Unable to load the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar' in the plugin 'org.apache.maven.plugins:maven-jar-plugin'. A required class is missing: org/codehaus/plexus/archiver/zip/AbstractZipArchiver [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar': Unable to load the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar' in the plugin 'org.apache.maven.plugins:maven-jar-plugin'. A required class is missing: org/codehaus/plexus/archiver/zip/AbstractZipArchiver at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:698) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to load the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar' in the plugin 'org.apache.maven.plugins:maven-jar-plugin'. A required class is missing: org/codehaus/plexus/archiver/zip/AbstractZipArchiver at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:679) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: java.lang.NoClassDefFoundError: org/codehaus/plexus/archiver/zip/AbstractZipArchiver at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195
Re: Opening up xbean svn access (Fwd: Jar listing performance)
On Jun 9, 2011, at 2:21 AM, David Blevins wrote: On Jun 8, 2011, at 9:36 PM, David Blevins wrote: I and pretty much everyone with dual OpenEJB/Geronimo commit is likely way too busy to commit this patch (XBEAN-176). Ended up having to make CDI related change to xbean and cleared out this patch. We should still consider opening things up though. Let's definitely keep an eye on things. Have there been problems getting patches applied? I can't really see this instance as a problem. I'd already applied the first patch, found a test failure, and bumped it back to Romain. He posted a second patch in the afternoon. So, I can't really see that this patch was. If Romain or anyone else is consistently contributing to xbean, we'd certainly give them commit consideration... --kevan
Re: buildbot failure in ASF Buildbot on geronimo-server-trunk
fixed. Author: genspring Date: Thu Jun 9 12:21:05 2011 New Revision: 1133819 URL: http://svn.apache.org/viewvc?rev=1133819view=rev Log: had thought that the default value of initializeInOrder in specDD is false instead of null. On Thu, Jun 9, 2011 at 6:26 PM, build...@apache.org wrote: The Buildbot has detected a new failure on builder geronimo-server-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/geronimo-server-trunk/builds/70 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: scheduler Build Source Stamp: [branch geronimo/server/trunk] 1133698 Blamelist: genspring BUILD FAILED: failed compile sincerely, -The Buildbot -- Shawn
Re: Progress on osgi-friendliness
On Thu, Jun 9, 2011 at 9:02 AM, David Jencks david_jen...@yahoo.com wrote: BTW, this includes my idea for wrapping non-bundle jars through the admin console. I haven't tested this at all in case anyone wants to try it. Basically if you try to deploy an artifact that isn't a bundle, it runs the jar through the pax wrap url handler which uses bnd with very lenient settings to turn it into a bundle. I love to see this nice feature, and I will have a try, and get back what I find. thanks! Forrest
[BUILD] branches/2.1: Failed for Revision: 1133656
Geronimo Revision: 1133656 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20110609/build-0200.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.1/20110609 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 199 minutes 47 seconds [INFO] Finished at: Thu Jun 09 12:28:09 EDT 2011 [INFO] Final Memory: 309M/846M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.1/20110609/logs-0200-tomcat/ [INFO] Running security-testsuite.security [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 61.676 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.1/20110609/logs-0200-jetty/ [INFO] Running security-testsuite-generic-auth-test [INFO] Tests run: 4, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.463 sec FAILURE! Samples: branches/2.1 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.1/20110609/samples-0200.log Build status: FAILED
Re: svn commit: r1129174 - in /geronimo/server/trunk: framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ plugins/client/geronimo-client-builder/src/main/java/org/apach
On Jun 1, 2011, at 5:22 PM, David Jencks wrote: But first please explain why you think this change is correct. It looks wrong to me, and I think the test was correct. Maybe i don't understand what the test is doing, but I don't think libfolder/ is in the manifest classpath being tested but it shows up in the results. Why should it? Shawn, Did we get an answer to David's questions including the MFCP_STRICT change? --kevan
[jira] [Assigned] (GERONIMODEVTOOLS-747) Undeploy module while server is stopped
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMODEVTOOLS-747: Assignee: Jarek Gawor 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 Assignee: 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] [Commented] (GERONIMODEVTOOLS-747) Undeploy module while server is stopped
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046714#comment-13046714 ] Jarek Gawor commented on GERONIMODEVTOOLS-747: -- That's correct but for some reason it is not working with GEP. 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 Assignee: 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] [Resolved] (GERONIMODEVTOOLS-707) force Eclipse plugin to refresh and realize the application was undeployed if an application is undeployed through the admin console or Karaf shell
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-707. -- Resolution: Fixed force Eclipse plugin to refresh and realize the application was undeployed if an application is undeployed through the admin console or Karaf shell --- Key: GERONIMODEVTOOLS-707 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-707 Project: Geronimo-Devtools Issue Type: Wish Affects Versions: 2.2.2, 3.0 Reporter: Shawn Jiang Assignee: Jarek Gawor Fix For: 3.0 if an application is undeployed/deployed through the admin console or Karaf shell, we need to provide a way to force Eclipse plugin to refresh and realize the application was undeployed/deployed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-707) force Eclipse plugin to refresh and realize the application was undeployed if an application is undeployed through the admin console or Karaf shell
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046732#comment-13046732 ] Jarek Gawor commented on GERONIMODEVTOOLS-707: -- Additional changes committed in revision 1134033 for this issue. Some modules can be in some state between started stopped so also check available modules before removing the module from the list. force Eclipse plugin to refresh and realize the application was undeployed if an application is undeployed through the admin console or Karaf shell --- Key: GERONIMODEVTOOLS-707 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-707 Project: Geronimo-Devtools Issue Type: Wish Affects Versions: 2.2.2, 3.0 Reporter: Shawn Jiang Assignee: Jarek Gawor Fix For: 3.0 if an application is undeployed/deployed through the admin console or Karaf shell, we need to provide a way to force Eclipse plugin to refresh and realize the application was undeployed/deployed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-747) Undeploy module while server is stopped
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046740#comment-13046740 ] Jarek Gawor commented on GERONIMODEVTOOLS-747: -- Fixed in revision 1134035. The change type for the module was recomputed incorrectly. Instead of REMOVED it was changed to CHANGED which redeployed the module instead of removing it. 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 Assignee: Jarek Gawor Fix For: 3.0 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] [Resolved] (GERONIMODEVTOOLS-747) Undeploy module while server is stopped
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-747. -- Resolution: Fixed Fix Version/s: 3.0 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 Assignee: Jarek Gawor Fix For: 3.0 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] [Commented] (GERONIMODEVTOOLS-718) Update a bundle within an EBA
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046751#comment-13046751 ] Jarek Gawor commented on GERONIMODEVTOOLS-718: -- In revision 1134035 I simplified the EBA code that deals with deciding which module/bundle should be refreshed. I also changed the code not to cache the bundle ids since they change frequently and it's hard to keep GEP up-to-date with the latest ids. There is definitely a lot more opportunity here to optimize and clean up the bundle update code. Update a bundle within an EBA - Key: GERONIMODEVTOOLS-718 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-718 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Han Hong Fang Fix For: 3.0-M2, 3.0 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 feature will probably require changes to the server's deployer code or might need a new set of API for deploying managing bundles within or outside of EBAs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5997) Missing commands for startup
[
https://issues.apache.org/jira/browse/GERONIMO-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046832#comment-13046832
]
Leonardo Bueno Postacchini commented on GERONIMO-5997:
--
I downloaded it from Apache as far as I remember, I just checked the original
tarball and the file is just that way.
Missing commands for startup
Key: GERONIMO-5997
URL: https://issues.apache.org/jira/browse/GERONIMO-5997
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: commands, Jetty, startup/shutdown
Affects Versions: 2.2.1
Environment: Debian linux/squeeze
Java 1.6 v19 sun
Reporter: Leonardo Bueno Postacchini
Attachments: geronimo.sh, geronimo_old.sh
Documentations instructs launching geronimo with:
geronimo jpda run
or
geronimo jpda start
for remote debugging but attempting to do that result in message:
Usage: geronimo {start|stop|restart|status}
Edit: Change jpda - jdpa
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5997) Missing commands for startup
[
https://issues.apache.org/jira/browse/GERONIMO-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046835#comment-13046835
]
Leonardo Bueno Postacchini commented on GERONIMO-5997:
--
Just saw that I put it under version 2.2.1, it is in fact, 2.2.
Missing commands for startup
Key: GERONIMO-5997
URL: https://issues.apache.org/jira/browse/GERONIMO-5997
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: commands, Jetty, startup/shutdown
Affects Versions: 2.2
Environment: Debian linux/squeeze
Java 1.6 v19 sun
Reporter: Leonardo Bueno Postacchini
Attachments: geronimo.sh, geronimo_old.sh
Documentations instructs launching geronimo with:
geronimo jpda run
or
geronimo jpda start
for remote debugging but attempting to do that result in message:
Usage: geronimo {start|stop|restart|status}
Edit: Change jpda - jdpa
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5997) Missing commands for startup
[
https://issues.apache.org/jira/browse/GERONIMO-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046946#comment-13046946
]
Kevan Miller commented on GERONIMO-5997:
Hi Leonardo, thanks for the info. So, your geronimo_old.sh file looks like it
was generated by the gserviceReg.sh command. See
https://cwiki.apache.org/GMOxDOC22/running-geronimo-as-a-linux-service.html for
more information. I assume you or someone else ran './gserviceReg add geronimo'
(or similar) to generate a geronimo service. The resulting service script file
would look like your geronimo_old.sh.
gserviceReg.sh was not designed to create a service script which supported the
'jpda' option. I suppose it could, but I'm not sure it's a common use case...
If somebody feels it would be valuable, speak up...
So, if you use the 'geronimo.sh' script that's included in a geronimo download,
I believe you have the function you're looking for.
Missing commands for startup
Key: GERONIMO-5997
URL: https://issues.apache.org/jira/browse/GERONIMO-5997
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: commands, Jetty, startup/shutdown
Affects Versions: 2.2
Environment: Debian linux/squeeze
Java 1.6 v19 sun
Reporter: Leonardo Bueno Postacchini
Attachments: geronimo.sh, geronimo_old.sh
Documentations instructs launching geronimo with:
geronimo jpda run
or
geronimo jpda start
for remote debugging but attempting to do that result in message:
Usage: geronimo {start|stop|restart|status}
Edit: Change jpda - jdpa
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6002) Can't configure defaultJspServlet parameters
Can't configure defaultJspServlet parameters Key: GERONIMO-6002 URL: https://issues.apache.org/jira/browse/GERONIMO-6002 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Kevan Miller Assignee: Kevan Miller Fix For: 3.0 It's not currently possible to configure the defaultJspServlet properties. This means that you can't configure 'development' mode or trimSpaces. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] trunk: Failed for Revision: 1134163
Geronimo Revision: 1134163 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110609/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110609/unit-test-reports codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2) org.apache.felix:maven-bundle-plugin:maven-plugin:2.0.1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.felix -DartifactId=maven-bundle-plugin -Dversion=2.0.1 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.felix -DartifactId=maven-bundle-plugin -Dversion=2.0.1 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.felix:maven-bundle-plugin:maven-plugin:2.0.1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2) org.apache.felix:maven-bundle-plugin:maven-plugin:2.0.1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:178) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.felix -DartifactId=maven-bundle-plugin -Dversion=2.0.1 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.felix -DartifactId=maven-bundle-plugin -Dversion=2.0.1 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.felix:maven-bundle-plugin:maven-plugin:2.0.1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2) org.apache.felix:maven-bundle-plugin:maven-plugin:2.0.1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:253) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184) at org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1626) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1582) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeHandlersInPlugins(DefaultLifecycleExecutor.java:1468
[jira] [Commented] (GERONIMO-6002) Can't configure defaultJspServlet parameters
[
https://issues.apache.org/jira/browse/GERONIMO-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046952#comment-13046952
]
Kevan Miller commented on GERONIMO-6002:
With these changes, can now override xml attributes in config.xml. For instance:
{code}
module name=org.apache.geronimo.configs/jasper-deployer/3.0-SNAPSHOT/car
gbean name=JspModuleBuilderExtension
attribute name=defaultJspServlet
web-app xmlns=http://java.sun.com/xml/ns/javaee;
servlet
servlet-namejsp/servlet-name
servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class
init-param
param-namedevelopment/param-name
param-valuetrue/param-value
/init-param
init-param
param-nametrimSpaces/param-name
param-valuetrue/param-value
/init-param
init-param
param-namefork/param-name
param-valuefalse/param-value
/init-param
init-param
param-namelogVerbosityLevel/param-name
param-valueDEBUG/param-value
/init-param
init-param
param-namexpoweredBy/param-name
param-valuefalse/param-value
/init-param
init-param
param-nameengineOptionsClass/param-name
param-valueorg.apache.geronimo.jasper.JspServletOptions/param-value
/init-param
load-on-startup0/load-on-startup
/servlet
servlet-mapping
servlet-namejsp/servlet-name
url-pattern*.jsp/url-pattern
url-pattern*.jspf/url-pattern
url-pattern*.jspx/url-pattern
url-pattern*.xsp/url-pattern
/servlet-mapping
/web-app
/attribute
/gbean
/module
{code}
Could add this to config-xml-content for jasper-deployer. But, should
consider letting var/catalina/conf/web.xml control these settings. Something
for later...
Can't configure defaultJspServlet parameters
Key: GERONIMO-6002
URL: https://issues.apache.org/jira/browse/GERONIMO-6002
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 3.0
Reporter: Kevan Miller
Assignee: Kevan Miller
Fix For: 3.0
It's not currently possible to configure the defaultJspServlet properties.
This means that you can't configure 'development' mode or trimSpaces.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5976) Load JSP tag libraries from bundles
[ https://issues.apache.org/jira/browse/GERONIMO-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5976. --- Resolution: Fixed Fix Version/s: 3.0 In revision 1134181 I committed minor fixes that avoid UnsupportedOperationException when DependencyManager.getFullDependentBundles() returns an empty list. Load JSP tag libraries from bundles --- Key: GERONIMO-5976 URL: https://issues.apache.org/jira/browse/GERONIMO-5976 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: web Affects Versions: 3.0-M1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 It would be nice to have a way for WAB to load JSP taglib files from separate (somehow dependent) bundles. This is similar to GERONIMO-5938. -- 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: 1134128
Geronimo Revision: 1134128 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110610/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110610/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.activemq:activemq-web-console:war:5.4.2 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-web-console -Dversion=5.4.2 -Dpackaging=war -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-web-console -Dversion=5.4.2 -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT 2) org.apache.activemq:activemq-web-console:war:5.4.2 -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) 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-web-console:war:5.4.2 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-web-console -Dversion=5.4.2 -Dpackaging=war -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-web-console -Dversion=5.4.2 -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT 2) org.apache.activemq:activemq-web-console:war:5.4.2 -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at
Re: Opening up xbean svn access (Fwd: Jar listing performance)
On Jun 9, 2011, at 5:04 AM, Kevan Miller wrote: On Jun 9, 2011, at 2:21 AM, David Blevins wrote: On Jun 8, 2011, at 9:36 PM, David Blevins wrote: I and pretty much everyone with dual OpenEJB/Geronimo commit is likely way too busy to commit this patch (XBEAN-176). Ended up having to make CDI related change to xbean and cleared out this patch. We should still consider opening things up though. Let's definitely keep an eye on things. Have there been problems getting patches applied? Nah it's just been steadily shrinking. Instead of putting good things in, people just take them out. I've watched the finder code get forked a few times and it will likely happen again as a commons project. Overall the projects that used to contribute to xbean have largely stopped doing so and we've been unsuccessful convincing anyone to start using the libraries. As you say, we'll keep an eye on it. I don't really have the brain capacity to think about good solutions at the moment anyway. -David
