Cindy,
The second problem is not a problem - simply that when you stop a server some
threads are interrupted and if you run with DEBUG on you will see those
interrupted exceptions.
The first problem is a problem. It looks like when a response object is
being recycled, the version is reset to Null rather than the default of HTTP/1.0.
In normal operation, this is probably normally reset to whatever version is
required.
You should be able to avoid the problem by making sure your handler always
does a
response.setVersion(request.getVersion());
OR you can upgrade to the latest version of Jetty (4 or 5) where this
problem has been fixed.
regards
Cindy Schilling wrote:
Hi,
My team is using Jetty (version 4.2.9) as an embedded HTTP server in our
product. We've been very happy with Jetty(!), but periodically we see a couple
of pesky errors while we're running. They are described below. Has anyone else
seen these? Greg -- do you know if these will be fixed in Jetty 5?
Error #1: After running a test in which we send a request for which there is
not a registered HTTP handler (but there is a default handler), we see this
occasionally:
OUR ERROR MSG -> 2004-08-29 21:32:10,921 [WARN ] OVI-5700
OviHttpClientServerSuperTest: Received HTTP request that could not be handled.
Target was: /SpongeBob
JETTY ERROR -> 2004-08-29 21:32:10,928 [WARN ] OVI-101 HTTP Server:
java.lang.NullPointerException
at org.mortbay.util.ByteArrayISO8859Writer.write
(ByteArrayISO8859Writer.java:152)
at org.mortbay.http.HttpResponse.writeHeader(HttpResponse.java:254)
at org.mortbay.http.NullableOutputStream.writeHeader
(NullableOutputStream.java:61)
at org.mortbay.http.HttpOutputStream.writeHeader(HttpOutputStream.java:416)
at org.mortbay.http.HttpConnection.commit(HttpConnection.java:702)
at org.mortbay.http.HttpConnection.outputNotify(HttpConnection.java:518)
at org.mortbay.http.HttpOutputStream.notify(HttpOutputStream.java:550)
at org.mortbay.http.HttpOutputStream.close(HttpOutputStream.java:510)
at org.mortbay.http.HttpConnection.close(HttpConnection.java:247)
at org.mortbay.http.HttpConnection.destroy(HttpConnection.java:1091)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:798)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)
Error #2: After executing a "httpServer1.stopServer();" followed by
a "httpServer1.destroyServer();", we sometimes see:
2004-08-30 01:32:25,065 [DEBUG] com.hp.ov.ovi.inf.http.OviJettyLogSink:HTTP
Server - closing ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=34010]
OUR ERROR MSG -> 2004-08-30 01:32:25,077 [INFO ] OVI-101 HTTP Server: Stopped
SocketListener on 0.0.0.0:34010
2004-08-30 01:32:25,084 [DEBUG] com.hp.ov.ovi.inf.http.OviJettyLogSink:HTTP
Server - Stopped com.hp.ov.ovi.inf.http.PlugletHttpHandler in HttpContext[]
THE PROBLEM -> 2004-08-30 01:32:25,086 [DEBUG]
com.hp.ov.ovi.inf.http.OviJettyLogSink:HTTP Server -
java.io.InterruptedIOException: Operation interrupted
2004-08-30 01:32:25,091 [DEBUG] com.hp.ov.ovi.inf.http.OviJettyLogSink:HTTP
Server - Stopped com.hp.ov.ovi.inf.http.PlugletHttpHandler in HttpContext[]
Cindy Schilling
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
| 