Jetty

[ashikuzzaman]

I would like to know a little about Jetty. As there is no forum on Jetty only, it seems ok to post here.

What's Jetty's strength over Tomcat and can it be seperately used besides JBoss as a web container? And some more please.... :)

[kbutler]

I have seen one comparison report that I think I found on serverside.com. The results showed Jetty serving pages slower than Tomcat, but not dropping connection requests as early (under load). I could only characterize these results as "hearsay" however, since I don't know the details on the configurations.

I myself have used Tomcat (standalone) for a couple of years and am familiar with that. I am trying Jetty since it is the default JBoss config.

Lemme know if you find any useful results, I am just starting my research.

** Does anybody know how to override the default servlet configuration, I **think** that in the webdefault.xml config file I should be able to add a "resourceBase" param and direct all requests NOT associated with a context to a default context, however this is not working, probably I'm doing something wrong.

Beginning of my webdefault.xml, modified within the deployed jbossweb-jetty.sar --- look at the very end, the 'resourceBase' param::

<web-app>

Default web.xml file.
This file is applied to a Web application before it's own WEB_INF/web.xml file



<servlet-name>default</servlet-name>
<servlet-class>org.mortbay.jetty.servlet.Default</servlet-class>
<init-param>
<param-name>acceptRanges</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>dirAllowed</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>putAllowed</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>delAllowed</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>redirectWelcome</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>minGzipLength</param-name>
<param-value>8192</param-value>
</init-param>
<init-param>
<param-name>resourceBase</param-name>
<param-value>/hasp</param-value>
</init-param>
<load-on-startup>0</load-on-startup>

[kbutler]

Also as you've probably found out by now any part of JBoss can (theoretically I haven't tried it) be NOT deployed, thereby yes you could just deploy Jetty by itself within JBoss.

[kbutler]

OK - found an answer. It's not necessary to monkey around with the default Jetty configuration within the SAR.

I modifed the application.xml inside my EAR to point the web-uri to /, and that seems to work.

Here's the config:


<web-uri>hasp.war</web-uri>
<context-root>/</context-root>



I'm not sure if I can use 2 web modules, one using default context, the other using a real context (/hasp). I'm not sure I'd want to, but it may be useful. (I'm converting an older non-compliant webapp).

[jonlee]

Take a look at http://www.webperformanceinc.com/library/ServletReport/

Also, look at the Jetty documentation at:
http://jetty.mortbay.org

Jetty, like Tomcat, is its own entity. There is a Jetty forum (not JBoss) and also further information at Core Developers Network.

[kbutler]

Ah yes, looks familiar. Thanks!!