Jetty - Java HTTP Servlet Server

I am copying my message since I got no reply to it. Jetty developers, if you
do not post the documentation concerning certain areas of the project, and
still wish that people use your product, we expect from you to be more
helpful.
Documentation in the code does not help enough and in the understandable way

1. I need to configure Monolog to work with Jetty. (there exists a
monolog.jar so, I should be able to use it).
2. Do I use it through JCL or directly calling a monolog class in some
property file or VM?
2. How do I do it (pass a parameter to VM, config file etc.??)
I need a full step-by-step explanation, faq, doc. whatever.

Thank you,
Igor Smirnov

----- Original Message -----
From: "Igor Smirnov" <igor@...>
To: <jetty-support@...>
Sent: Monday, May 17, 2004 6:58 PM
Subject: Re: [Jetty-support] Jetty 1st time


> So if I understand right, for JCL to work with jetty I'd need to configure
> commons-logging.properties somewhere in the directory tree. Where would
> that be? I am familiar with JCL, worked with Tomcate using it.
> Thanks,
> Igor
>
> Jan Bartel wrote:
>
> > Hi Igor,
> >
> > There are 2 different types of logs in Jetty:
> > + the standard HTTP access log
> > + general debug/info log (Jetty uses the Jakarta Commons Logging
> > mechanism)
> >
> > The first is configured in your jetty xml config file (see
> > $JETTY_HOME/etc/demo.xml for an example).
> >
> > For the second, you need to use the facilities of the Commons Logging
> > to select which type of log implementation you'd like to use, such as
> > Log4J, JDK1.4 logging etc etc. The Commons Logging pages have more
> > info on this:
> >
> >    http://jakarta.apache.org/commons/logging/guide.html
> >
> >
> > cheers,
> > Jan
> >
> >
> > Igor Smirnov wrote:
> >
> >> Hi everyone,
> >>
> >> I have just installed Jetty 4.2.18, unzipped it, better to say. 1st
> >> time ever to use Jetty so I'm very new to the product.
> >> I am interested in how Jetty does logging. I see there were changes
> >> recently and common logging was deployed in this version. I see there
> >> is support for both log4j and monolog.
> >> Sadly, I found no docummentation describing the logging process.
> >> Is there anyone here who could explain me where to configure the
> >> logger I would like to use with jetty, where the output goes.
> >> Right now I am staring Jetty with java -jar start.jar. Should i be
> >> using a different command to configure logging?
> >>
> >> Thanks in advance!
> >> Igor
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: SourceForge.net Broadband
> > Sign-up now for SourceForge Broadband and get the fastest
> > 6.0/768 connection for only $19.95/mo for the first 3 months!
> > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> > _______________________________________________
> > Jetty-support mailing list
> > Jetty-support@...
> > https://lists.sourceforge.net/lists/listinfo/jetty-support
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Jetty-support mailing list
> Jetty-support@...
> https://lists.sourceforge.net/lists/listinfo/jetty-support
>

I have a webapp which runs great on Jetty (thanks guys!).  I am trying to find 
a solution that will let me run IIS and redirect the requests to Jetty.  I 
tried using IISRelayJ however it doesnt seem to be able to handle sessions 
properly.  Im wondering if there is an alternative to IISRelayJ?

What does the Jetty team recommend to use for this type of situation.

Hi all,
=20
    Trying to get Jikes working with Jetty and run into another problem.
I kept getting the error:=20
=20
    org.mortbay.util.MultiException[javax.servlet.UnavailableException:
Configuration problem]
        at org.mortbay.http.HttpServer.start(HttpServer.java:640)
        at
mbf.neuroInfo.app.JettyFacade.startServer(JettyFacade.java:271)
        at mbf.neuroInfo.app.Server.<init>(Server.java:231)
        at mbf.neuroInfo.app.Server.<init>(Server.java:56)
        at mbf.neuroInfo.app.Server.main(Server.java:359)
    javax.servlet.UnavailableException: Configuration problem
        at
org.mortbay.jetty.servlet.WebApplicationContext.initialize(WebApplicatio
nContext.java:714)
        at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationCont
ext.java:404)
        at org.mortbay.http.HttpServer.start(HttpServer.java:663)
        at
mbf.neuroInfo.app.JettyFacade.startServer(JettyFacade.java:271)
        at mbf.neuroInfo.app.Server.<init>(Server.java:231)
        at mbf.neuroInfo.app.Server.<init>(Server.java:56)
        at mbf.neuroInfo.app.Server.main(Server.java:359)
=20
=20
In my application, I set up the web application in my java application
using:
=20
     server.setRootWebApp("root");
     server.addWebApplications(System.getProperty("jetty.home",".") +
"webapps/");
=20
=20
=20
    I then have a web.xml file that contains all of my servlets.  My
web.xml file looks like:
=20
<?xml version=3D"1.0" encoding=3D"ISO-8859-1"?>
<!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
=20
<web-app>
    <display-name>MicroBrightField Neuroinfo</display-name>
    <description>
        test
    </description>
=20
    <servlet>
        <servlet-name>AdminServlet</servlet-name>
        <servlet-class>org.mortbay.servlet.AdminServlet</servlet-class>
        <load-on-startup>0</load-on-startup>
    </servlet>
=20
    <servlet>
        <servlet-name>DefinitionManage</servlet-name>
=20
<servlet-class>mbf.neuroInfo.serv.DefinitionManage</servlet-class>
        <load-on-startup>0</load-on-startup>
    </servlet>
=20
    <servlet>
        <servlet-name>jsp</servlet-name>
=20
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
        <init-param>
            <param-name>jspCompilerPlugin</param-name>
=20
<param-value>org.apache.jasper.compiler.JikesJavaCompiler</param-value>
        </init-param>
        <load-on-startup>0</load-on-startup>
    </servlet>
=20
    <servlet-mapping>
      <servlet-name>jsp</servlet-name>
      <url-pattern>*.jsp</url-pattern>
    </servlet-mapping>
=20
    <servlet-mapping>
        <servlet-name>AdminServlet</servlet-name>
        <url-pattern>/Administration</url-pattern>
    </servlet-mapping>
=20
    <servlet-mapping>
        <servlet-name>DefinitionManage</servlet-name>
        <url-pattern>/DefinitionManage</url-pattern>
    </servlet-mapping>
</web-app>
=20
Any help is greatly appreciated!
Doug
=20
=20

=20

Hi,

I am trying to run jetty on HP-UX 11.11. I have installed
jetty-4.2.20RC0-all.tar.gz.

I have JRE1.3.1 installed on the system.

When i do=20

java -Djetty.home=3D/opt/jetty-4.2.20RC0
-Djetty.class.path=3D/opt/hpservices/jre/lib -jar -start.jar

It fails and says


java.lang.NumberFormatException:
        at java.lang.Integer.parseInt(Unknown Source)
        at java.lang.Integer.parseInt(Unknown Source)
        at org.mortbay.start.Version.parse(Version.java:42)
        at org.mortbay.start.Version.<init>(Version.java:24)
        at org.mortbay.start.Main.configure(Main.java:183)
        at org.mortbay.start.Main.start(Main.java:428)
        at org.mortbay.start.Main.main(Main.java:91)

Does anybody know what i m doing wrong?

Many thanks
Lalit Seth

Yes, we upgraded to 4.2.20rc0 and the problem appears to have been fixed.
Doing a sigquit on Jetty told us that one or more threads were stuck doing a
socket read when they should have been sleeping.

Thanks for your reply and fixing the problem :)

----- Original Message -----
From: "Greg Wilkins" <gregw@...>
To: <jetty-support@...>
Sent: Wednesday, May 19, 2004 8:56 AM
Subject: Re: Jetty Logging


>
>
> Andrew Hall wrote:
> > Running Jetty 4.2.15 with Java 1.4.2-04, we are seeing that Jetty
eventually
> > stops responding, almost like all it's available threads are being used
up
> > and none are then available to handle accepted requests.
>
> We have had a few bugs over the last 6 months with multi CPU machines.
Basically
> race conditions that allows the listeners to stop working correctly.
>
> As far as I know, these are all fixed in 4.2.19 (and the soon to be
release
> 4.2.20).
>
> Not you can monitor what is happening in the thread pool with the
> JMX http agent.  If you turn stats on you get even more info.
>
> If JEtty does lock up on you, then the best way to work out what
> has happened is to get the JVM to dump it's threads (Ctrl-/ or kill -3 on
Unix).
>
> regards
>