Community
Participate
Working Groups
The Jetty variant of Virgo requires some different vm args and so doesn't work from the existing launcher.
OK, this seems a simple matter of changing the args when we create the run configuration for a jetty server.
Alright, with bug 373453 it should be super easy to deal with this. We just need a few pieces of information from the server team: 1. Some way to trivially infer that we're dealing with a Jetty server rather than TomCat. I'm thinking I'll take the obvious route and base that on the existence of a "jetty" directory at installation root. Reasonable? 2. We need the actual vm arguments to use.
*** Bug 369238 has been marked as a duplicate of this bug. ***
*** Bug 340183 has been marked as a duplicate of this bug. ***
Hi, I'll comment in here once I've figured out what we need. Chris.
Hi, So I've been through the logs to check I'm not missing anything and it's actually simpler than I thought. I have some extra arguments in the Virgo scripts I need to remove. All that is required is -Djetty.home="${KERNEL_HOME}/jetty" adding to the VM args. Chris.
Chris, are you saying that we *shouldn't* include the other args used by Tomcat or that this arg should be in addition to those args?
OK, I have Jetty launching, but I can't get greenpages to work -- dependency issues. I'm not sure how this could be an issue with how we're launcing it though. Does greenpages currently work under Jetty?
Hi, In addition to any other args is all I tried, I guess it could be trimmed down a little though. I don't know of any reason why it shouldn't work. Jetty has some issues with TagLibs but Greenpages isn't using TagLibs. What version of Jetty are you trying? I'll have a go. Chris.
OK, I'm going to mark this as completed. Please re-open if you experince any issues.