How ti increse heap size in Apache geronimo....
hi folks... i want to increse geronimo heap size for my app.. i am a newbie to geronimo... i am having 512 mb ohysical memory. thanks... ravi
Re: An unexpected error has been detected by HotSpot Virtual Machine:
hi kevan.. thanks for reply... but how to increase heap size of geronimo i am having 512 mb ram... thankx... Kevan Miller <[EMAIL PROTECTED]> wrote: On Jul 10, 2008, at 11:58 PM, ravi naik wrote: > hi.. > thanks for the reply... > i am using my sql as DB... > i am Integrating intalio and Jsp through Geronimo. > i am using Mysqlodbc connctor.not jdbc > thanks in advance... Ravi, Try increasing the heap size of your Geronimo server (e.g. set JAVA_OPTS=-Xmx512m). Adjust accordingly to the requirements of your app... Googling identified the following that looks pretty similar to your situation -- http://www.jguru.com/forums/view.jsp?EID=1273995 If that doesn't work, afraid I don't know what else to try... As Filip has noted, it's not anything we have direct control over... --kevan
[jira] Commented: (GERONIMO-4179) Creating your own custom server with Geronimo framework
[ https://issues.apache.org/jira/browse/GERONIMO-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613240#action_12613240 ] Ashish Jain commented on GERONIMO-4179: --- Are there alternative ways of installing the plugin through geronimo framework? > Creating your own custom server with Geronimo framework > --- > > Key: GERONIMO-4179 > URL: https://issues.apache.org/jira/browse/GERONIMO-4179 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: documentation >Affects Versions: 2.1, 2.1.1 >Reporter: Ashish Jain >Assignee: Ashish Jain > > The starting point for this tutorial should be the bin distro of Geronimo > Framework. ( see http://geronimo.apache.org/apache-geronimo-v211-release.html) > Roughly the sequence in this tutorial should be something like this > * getting the geronimo framework distro > * starting the framework > * using either Geronimo native commands or GShell search/list plugins > * select the required plugins and install them > * test the newly installed plugins -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-235) Plugin cannot synchronize with the server when non-zero portOffset value in the config-substitutions.properties file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613239#action_12613239 ] Ashish Jain commented on GERONIMODEVTOOLS-235: -- Ted, Thanks for your comments! Currently I am not looking at supporting remote servers and multiple server instances into this. Since both of these are not yet supported in GEP. We do have a JIRA GERONIMODEVTOOLS-216 open for remote server support and none for multiple server instances(don't know how feasible it is adding another server from same installation directory). However I would like to work on the current model of GEP that is one server from one installation directory without remote support. If this seems to be viable I will research more on it and provide options for fixing it. > Plugin cannot synchronize with the server when non-zero portOffset value in > the config-substitutions.properties file > > > Key: GERONIMODEVTOOLS-235 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0 >Reporter: Tim McConnell >Assignee: Ashish Jain > Fix For: 2.1.x > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-349) GEP synchronization with a server running outside of Eclipse no longer works
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613236#action_12613236 ] Ashish Jain commented on GERONIMODEVTOOLS-349: -- Thank you Tim and BJ for verifying the fix. > GEP synchronization with a server running outside of Eclipse no longer works > > > Key: GERONIMODEVTOOLS-349 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-349 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.0 >Reporter: Tim McConnell >Assignee: Ashish Jain > Fix For: 2.1.2 > > Attachments: GERONIMODEVTOOLS-349.patch, > GERONIMODEVTOOLS-349_updated.patch > > > The GEP should synchronize with a Geronimo server running either inside of > Eclipse or outside of Eclipse. It no longer works though when the server is > started outside of Eclipse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: JASPI as a component? JACC as a component?
Sounds good to me. Regards, Alan On Jul 11, 2008, at 11:55 AM, David Jencks wrote: I've been looking at JASPI lately, first working with jetty to base its authentication on jaspi, and now looking at implementing a provider for geronimo. I think it makes sense to have this as a component (like the tm/connector framework) rather than inside the geronimo-security jar. I'll move it, if there are problems or anyone objects we can move it back. thanks david jencks
Re: Liferay as a Geronimo Plugin
Hello Peter, This is great news for Liferay developers! IMHO, one of the pain points with Liferay development is the time it takes to build, pack and deploy a WAR to Liferay. Even if Liferay is not so bad on this front when compared with other portals, a typical build-deploy-test cycle is way too time consuming and hence seriously impacts productivity. It would be fantastic to have an in-place WAR development mode in Geronimo. What do you think? Thanks, Gianny On 14/07/2008, at 4:11 AM, Peter Petersson wrote: I have posted a feature issue containing the build code over at http://support.liferay.com/browse/LEP-6680 regards peter petersson Peter Petersson wrote: Hi With the help of David J custom server assemblies document ( http://cwiki.apache.org/GMOxDOC21/custom-server- assemblies.html ) and my experience working with David on the roller plugin I have manage to put together a Liferay ( http:// www.liferay.com ) plugin. For now the plugin is with liferay 5.0.1 rc1 on G 2.1.1 and consists of the following maven artifacts * geronimo-jetty-liferay -- A minimalistic server assembly with the geronimo kernel the lifray jetty plugin and the geronimo console plugin. * liferay-jetty -- The liferay jetty plugin built on the lesslibs liferay-portal war pulling in dependencys like lifray -kernel, - service and -portlet. * geronimo-tomcat-liferay -- A minimalistic server as above but with the liferay tomcat plugin. * liferay-tomcat -- The liferay tomcat plugin as liferay-jetty above but with tomcat. * liferay-derby -- The liferay derby db backend plugin. * lifray-portal -- The liferay portal war fetched from liferay and pulled in to a local maven repos. * liferay-portal-lesslibs -- A overlay of the liferay portal war with filtered lib jars making use of some geronimo builtins instead. The geronimo-tomcat-liferay server seems to work fine but the jetty equivalent has a issue in the login page. When I have ironed out the jetty issue, cleaned up the code, made some additional improvements and put together a simple readme with build instructions ;) I am thinking of wrapping it up and first of all contribute it to the liferay community ( as suggested by david in http://marc.info/?l=geronimo-user&m=121304343919559&w=2 ) to see if they are interested in it for there geronimo integration. Anny suggestions, opinions, tips or help to pull this together in the best way possible are appreciated. regards peter petersson
Re: An unexpected error has been detected by HotSpot Virtual Machine:
On Jul 10, 2008, at 11:58 PM, ravi naik wrote: hi.. thanks for the reply... i am using my sql as DB... i am Integrating intalio and Jsp through Geronimo. i am using Mysqlodbc connctor.not jdbc thanks in advance... Ravi, Try increasing the heap size of your Geronimo server (e.g. set JAVA_OPTS=-Xmx512m). Adjust accordingly to the requirements of your app... Googling identified the following that looks pretty similar to your situation -- http://www.jguru.com/forums/view.jsp?EID=1273995 If that doesn't work, afraid I don't know what else to try... As Filip has noted, it's not anything we have direct control over... --kevan
Re: JASPI as a component? JACC as a component?
On Jul 11, 2008, at 2:55 PM, David Jencks wrote: I've been looking at JASPI lately, first working with jetty to base its authentication on jaspi, and now looking at implementing a provider for geronimo. I think it makes sense to have this as a component (like the tm/connector framework) rather than inside the geronimo-security jar. I'll move it, if there are problems or anyone objects we can move it back. No objections from me. --kevan
Re: For which server version(s) should we release samples?
On Jul 11, 2008, at 5:46 PM, Joe Bohn wrote: Going once ... going twice Anybody that thinks we need to release samples for 2.1 and/or 2.1.1 should speak up soon. So far the consensus is a 2.1.2 release only. I think it's ok for the samples release to only be supported on 2.1.2 (and beyond). --kevan
[jira] Created: (GERONIMO-4203) Restarting configurations from the system modules portlet gives erroneous warning message
Restarting configurations from the system modules portlet gives erroneous warning message - Key: GERONIMO-4203 URL: https://issues.apache.org/jira/browse/GERONIMO-4203 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Environment: RHEL 5 Reporter: Manu T George Priority: Minor If I restart any of the system modules it gives an erroneous warning Restarting this component may prevent the server or admin console from functioning properly. As part of the stop action all dependant components and subsequent dependencies will also be stopped. Only this component will be restarted. However the restart actually starts all of the dependencies and at the bottom of the screen it shows the dependencies that have been started. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4202) On Restart of openejb configuration restart of remote service failing
On Restart of openejb configuration restart of remote service failing - Key: GERONIMO-4202 URL: https://issues.apache.org/jira/browse/GERONIMO-4202 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: OpenEJB Affects Versions: 2.1.1, 2.2 Environment: RHEL 5 Reporter: Manu T George Restarting the openejb configuration from the admin console results in the following error 02:40:22,549 FATAL [remote] Service Start Failed: ejbd 0.0.0.0 4201: Service failed to open socket: Address already in use -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Restarting console-base from command line
Hi Shrey, I also faced this issue recently. My understanding is that all the DWR calls go through the org.apache.geronimo.console.servlet.ContextForwardServlet servlet currently. In that servlet we have a reference to the web app context of say plan creator or any other console plugin. Since plan creator is stopped that context object that we refer to becomes stale. So we need to refresh that context reference in the ContextForwardServlet. I have opened a JIRA and attached a patch. The link to the jira is https://issues.apache.org/jira/browse/GERONIMO-4201 Regards Manu On Fri, Jul 11, 2008 at 11:01 AM, Shrey Banga <[EMAIL PROTECTED]> wrote: > I was trying to write a bat file for automating the process of building > plancreator, stopping the plancreator module on the server, replacing it > with the new build and restarting plancreator. Once this process is done, > the DWR stops working, which is probably because requests to DWR go through > /console webapp context. So I manually restart the console-base from the > admin console which does the trick. Now for the purpose of the bat file, I > need to use the deploy tool to restart only the console-base but it in > list-modules it is shown as: >> >> + org.apache.geronimo.plugins/console-tomcat/2.2-SNAPSHOT/car >> `-> portal-driver.war >> `-> base-portlets.war > > > If I do a deploy restart > org.apache.geronimo.plugins/console-tomcat/2.2-SNAPSHOT/car many of the > other deployed webapps get stopped. How do I restart only console-base ? Or > is there a simpler workaround for the dwr problem ? > -- > Shrey Banga > Bachelor of Technology, III year > Department of Electrical Engineering > Indian Institute of Technology Roorkee
[jira] Assigned: (GERONIMO-4201) Accessing admin console portlets that use DWR after restart giving error
[ https://issues.apache.org/jira/browse/GERONIMO-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manu T George reassigned GERONIMO-4201: --- Assignee: (was: Manu T George) Please commit this patch if appropriate > Accessing admin console portlets that use DWR after restart giving error > > > Key: GERONIMO-4201 > URL: https://issues.apache.org/jira/browse/GERONIMO-4201 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1 > Environment: All >Reporter: Manu T George > Fix For: 2.1.x, 2.2 > > Attachments: G4201_r673785.patch > > > Restart one of the debug views portlet from the admin console and all dwr > calls fail > The exception is > 02:28:42,399 ERROR [[dwr-forward2]] Servlet.service() for servlet > dwr-forward2 threw exception > java.lang.NullPointerException > at > org.apache.geronimo.console.servlet.ContextForwardServlet.doPost(ContextForwardServlet.java:74) > at > org.apache.geronimo.console.servlet.ContextForwardServlet.doGet(ContextForwardServlet.java:60) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4201) Accessing admin console portlets that use DWR after restart giving error
[ https://issues.apache.org/jira/browse/GERONIMO-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manu T George updated GERONIMO-4201: Attachment: G4201_r673785.patch This patch will again refresh the forwardContext variable with the servletContext in case of the request dispatcher being null. This occurs for /dwr(n) calls forwarded via this servlet after restart of the respective console components > Accessing admin console portlets that use DWR after restart giving error > > > Key: GERONIMO-4201 > URL: https://issues.apache.org/jira/browse/GERONIMO-4201 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1 > Environment: All >Reporter: Manu T George >Assignee: Manu T George > Fix For: 2.1.x, 2.2 > > Attachments: G4201_r673785.patch > > > Restart one of the debug views portlet from the admin console and all dwr > calls fail > The exception is > 02:28:42,399 ERROR [[dwr-forward2]] Servlet.service() for servlet > dwr-forward2 threw exception > java.lang.NullPointerException > at > org.apache.geronimo.console.servlet.ContextForwardServlet.doPost(ContextForwardServlet.java:74) > at > org.apache.geronimo.console.servlet.ContextForwardServlet.doGet(ContextForwardServlet.java:60) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4201) Accessing admin console portlets that use DWR after restart giving error
[ https://issues.apache.org/jira/browse/GERONIMO-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613204#action_12613204 ] Manu T George commented on GERONIMO-4201: - In ContextForwardServlet the servletContext that is got in the init method becomes stale after restart. > Accessing admin console portlets that use DWR after restart giving error > > > Key: GERONIMO-4201 > URL: https://issues.apache.org/jira/browse/GERONIMO-4201 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1 > Environment: All >Reporter: Manu T George >Assignee: Manu T George > Fix For: 2.1.x, 2.2 > > > Restart one of the debug views portlet from the admin console and all dwr > calls fail > The exception is > 02:28:42,399 ERROR [[dwr-forward2]] Servlet.service() for servlet > dwr-forward2 threw exception > java.lang.NullPointerException > at > org.apache.geronimo.console.servlet.ContextForwardServlet.doPost(ContextForwardServlet.java:74) > at > org.apache.geronimo.console.servlet.ContextForwardServlet.doGet(ContextForwardServlet.java:60) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4201) Accessing admin console portlets that use DWR after restart giving error
Accessing admin console portlets that use DWR after restart giving error Key: GERONIMO-4201 URL: https://issues.apache.org/jira/browse/GERONIMO-4201 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1.1, 2.1 Environment: All Reporter: Manu T George Assignee: Manu T George Fix For: 2.1.x, 2.2 Restart one of the debug views portlet from the admin console and all dwr calls fail The exception is 02:28:42,399 ERROR [[dwr-forward2]] Servlet.service() for servlet dwr-forward2 threw exception java.lang.NullPointerException at org.apache.geronimo.console.servlet.ContextForwardServlet.doPost(ContextForwardServlet.java:74) at org.apache.geronimo.console.servlet.ContextForwardServlet.doGet(ContextForwardServlet.java:60) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 676407
Geronimo Revision: 676407 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080713/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20080713 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 38 minutes 10 seconds [INFO] Finished at: Sun Jul 13 15:42:30 EDT 2008 [INFO] Final Memory: 371M/1012M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080713/logs-1500-tomcat/test.log Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080713/logs-1500-jetty/test.log Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom Downloading: http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom Downloading: http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom Downloading: http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom Downloading: http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom [INFO] [geronimo:start-server {execution: start}] [INFO] Using assembly configuration: jetty [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking for updates from codehaus-snapshots [INFO] snapshot org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking for updates from apache.snapshots [INFO] Using assembly artifact: org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:zip:bin:2.2-SNAPSHOT:provided [INFO] Using geronimoHome: /home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT [INFO] Installing assembly... [INFO] Expanding: /home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty6-javaee5/2.2-SNAPSHOT/geronimo-jetty6-javaee5-2.2-SNAPSHOT-bin.zip into /home/geronimo/geronimo/trunk/testsuite/target [INFO] Starting Geronimo server... [INFO] Selected option set: default [INFO] Redirecting output to: /home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log [INFO] Waiting for Geronimo server... [INFO] Geronimo server started in 0:00:42.443 [INFO] [shitty:install {execution: default}] [INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom [INFO] [shitty:test {execution: default}] [INFO] Starting 31 test build(s) [INFO] [INFO] --- [INFO] [INFO] commands-testsuite/deployRUNNING [INFO] commands-testsuite/deploySUCCESS (0:01:01.901) [INFO] commands-testsuite/gshellRUNNING [INFO] commands-testsuite/gshellSUCCESS (0:00:28.965) [INFO] commands-testsuite/jaxws RUNNING [INFO] commands-testsuite/jaxws SUCCESS (0:00:18.439) [INFO] concurrent-testsuite/concurrent-basicRUNNING [INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:05.577) [INFO] console-testsuite/advanced RUNNING [INFO] console-testsuite/advanced FAILURE (0:01:19.727) Java returned: 1 [INFO] console-testsuite/basic RUNNING [INFO] console-testsuite/basic SUCCESS (0:01:48.249) [INFO] corba-testsuite/corba-helloworld RUNNING [INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:42.800) [INFO] corba-testsuite/corba-marshalRUNNING [INFO] corba-testsuite/corba-marshalSUCCESS (0:00:58.133) [INFO] corba-testsuite/corba-mytime RUNNING [INFO] corba-testsuite/corba-mytime SUCCESS (0:00:42.711) [INFO] deployment-testsuite/deployment-testsRUNNING [INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:31.671) [INFO] deployment-testsuite/jca-cms-tests RUNNING [INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.370) [INFO] deployment-testsuite/manifestcp-testsRUNNING [INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:31.324) [INFO] enterprise-testsuite/ejb-tests RUNNING [INFO] enterprise-testsuite/ejb
[jira] Updated: (GERONIMO-4200) Create plugins to enable cgi-bin support in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller updated GERONIMO-4200: --- Attachment: cgi-bin.war The attached war file seems to enable cgi-bin support using Tomcat's CGIServlet class. CGIServlet does not support absolute file urls (only files relative to the war). So, it's not easy to have a cgi-bin directory in the root of your Geronimo installation. It would be relatively easy to update CGIServlet to support absolute file addressing (or at least relative to a Geronimo installation). If you want to use cgi-bin in your Geronimo installation, try the following: {code} cd $GERONIMO_HOME mkdir cgi-bin cd cgi-bin jar xvf /cgi-bin.war ../bin/deploy.sh deploy --inPlace . {code} Place your executables in the cgi-bin directory. Note that this is less than ideal in that you have the WEB-INF deployment plan/deployment descriptor in your cgi-bin directory. > Create plugins to enable cgi-bin support in Geronimo > > > Key: GERONIMO-4200 > URL: https://issues.apache.org/jira/browse/GERONIMO-4200 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Reporter: Kevan Miller > Fix For: 2.1.x, 2.2 > > Attachments: cgi-bin.war > > > A user asked about enabling cgi-bin support in Geronimo. Would be nice if we > had Jetty/Tomcat plugins to enable this support. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4200) Create plugins to enable cgi-bin support in Geronimo
Create plugins to enable cgi-bin support in Geronimo Key: GERONIMO-4200 URL: https://issues.apache.org/jira/browse/GERONIMO-4200 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Reporter: Kevan Miller Fix For: 2.1.x, 2.2 A user asked about enabling cgi-bin support in Geronimo. Would be nice if we had Jetty/Tomcat plugins to enable this support. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Liferay as a Geronimo Plugin
I have posted a feature issue containing the build code over at http://support.liferay.com/browse/LEP-6680 regards peter petersson Peter Petersson wrote: Hi With the help of David J custom server assemblies document ( http://cwiki.apache.org/GMOxDOC21/custom-server-assemblies.html ) and my experience working with David on the roller plugin I have manage to put together a Liferay ( http://www.liferay.com ) plugin. For now the plugin is with liferay 5.0.1 rc1 on G 2.1.1 and consists of the following maven artifacts * geronimo-jetty-liferay -- A minimalistic server assembly with the geronimo kernel the lifray jetty plugin and the geronimo console plugin. * liferay-jetty -- The liferay jetty plugin built on the lesslibs liferay-portal war pulling in dependencys like lifray -kernel, -service and -portlet. * geronimo-tomcat-liferay -- A minimalistic server as above but with the liferay tomcat plugin. * liferay-tomcat -- The liferay tomcat plugin as liferay-jetty above but with tomcat. * liferay-derby -- The liferay derby db backend plugin. * lifray-portal -- The liferay portal war fetched from liferay and pulled in to a local maven repos. * liferay-portal-lesslibs -- A overlay of the liferay portal war with filtered lib jars making use of some geronimo builtins instead. The geronimo-tomcat-liferay server seems to work fine but the jetty equivalent has a issue in the login page. When I have ironed out the jetty issue, cleaned up the code, made some additional improvements and put together a simple readme with build instructions ;) I am thinking of wrapping it up and first of all contribute it to the liferay community ( as suggested by david in http://marc.info/?l=geronimo-user&m=121304343919559&w=2 ) to see if they are interested in it for there geronimo integration. Anny suggestions, opinions, tips or help to pull this together in the best way possible are appreciated. regards peter petersson
[jira] Commented: (GERONIMODEVTOOLS-402) Upgrade GEP to support Eclipse 3.4 and WTP 3.0
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613172#action_12613172 ] Tim McConnell commented on GERONIMODEVTOOLS-402: Beware that you cannot install Ganymede on top of Europa. So you must remove the eclipse directory in your local m2 repo before downloading and unzipping Ganymede with this update. Likewise for your own Eclipse installation. > Upgrade GEP to support Eclipse 3.4 and WTP 3.0 > -- > > Key: GERONIMODEVTOOLS-402 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-402 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Reporter: Tim McConnell >Assignee: Tim McConnell > Fix For: 2.1.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-402) Upgrade GEP to support Eclipse 3.4 and WTP 3.0
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613168#action_12613168 ] Tim McConnell commented on GERONIMODEVTOOLS-402: No, this is the only one > Upgrade GEP to support Eclipse 3.4 and WTP 3.0 > -- > > Key: GERONIMODEVTOOLS-402 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-402 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Reporter: Tim McConnell >Assignee: Tim McConnell > Fix For: 2.1.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-402) Upgrade GEP to support Eclipse 3.4 and WTP 3.0
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613164#action_12613164 ] Ted Kirby commented on GERONIMODEVTOOLS-402: Tim submitted rev 672096 for this one. Any more to go for this one, Tim? > Upgrade GEP to support Eclipse 3.4 and WTP 3.0 > -- > > Key: GERONIMODEVTOOLS-402 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-402 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Reporter: Tim McConnell >Assignee: Tim McConnell > Fix For: 2.1.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.