- From: Jeremy Johnson <jeremy@yonks.com>
- Date: Fri, 26 Mar 1999 13:00:25 -0500 (EST)
- To: www-jigsaw@w3.org
Re my previous posting, servlets are not totally locked up. They will answer around 5 minutes (!) or more after being requested by the browser. Sometimes with the correct response and sometimes with a NullPointerException. After returning a response once they will then do it again without any delay. Sounds like a cache problem (if there is one) in Jigsaw? This is weird, anyone seen this? I'm going to re-install the whole of Jigsaw and see of that fixes it. Debugging with a 5-10 minute time delay between requests would be almost impossible. Jeremy. >Big problem (maybe), has anyone else seen this? > >I've been using Jigsaw for three months+ with no problems like this but >the server has suddenly decided to stop serving servlets after the first >request. > >If I request a servlet, any servlets, even one which just opens an output >stream and returns some text, the server throws a NullPointerException >internally (ie. it doesn't get back to the browser as is usually the case) >and refuses to serve any more servlets from then until it is restarted. > >It will still server static web pages OK. > >I'm getting: > >java.lang.NullPointerException: > at java.io.DataOutputStream.flush(DataOutputStream.java) > at org.w3c.jigsaw.http.Client.terminate(Client.java) > at org.w3c.jigsaw.http.Client.startConnection(Client.java) > at org.w3c.jigsaw.http.Client.SocketClient.run(SocketClient.java) > at org.w3c.util.CachedThread.run(ThreadCache.java) > >My SQL server (MySQL) is not involved, this happens with Servlets that >don't 'do' anything apart from return text, as well as much more complex >ones that have been fine for ages. > >The output stream is being closed OK by the Servlet code etc. > >The jigadm server is serving fine and the admin applet can be accessed ok. > >The server error log contains nothing after the server startup message > >This is Jigsaw 2.0.1 running under RedHat Linux 5.2 with JDK 1.1.7a. > >Has anyone had this? It's not easy to see how to go about fixing it >without doing a full re-install. > >Jeremy.
Received on Friday, 26 March 1999 13:12:10 UTC