Re: Jigsaw on Mac

Greg Kimberly writes:
 > At 9:39 AM 11/20/96, Anselm Baird_Smith wrote:
 > >Greg Kimberly writes:
 > > > I've had partial success running alpha3 on a Mac under CW10.
 > > >
 > > > The command line I use (under javai in MetroWerks Java) is:
 > > >
 > > > -working "/InstallDir/Jigsaw/Jigsaw" -classpath
 > > > "/InstallDir/Jigsaw/Jigsaw/Jigsaw.zip" w3c.jigsaw.http.httpd -root
 > > > "/InstallDir/Jigsaw/Jigsaw"
 > > >
 > > > (note that this *may not* have a trailing return on it...)
 > > > (and that I keep my zip file in the main Jigsaw directory)
 > > >
 > > > The server seems to happily serve up pages, but does through the following
 > > > exception for every page served:
 > > >
 > > > java.lang.UnknownError: Broken Pipe
 > > > 	at java.net.SocketInputStream.read(SocketInputStream.java:89)
 > > > 	at java.io.BufferedInputStream.fill(BufferedInputStream.java:107)
 > > > 	at java.io.BufferedInputStream.read(BufferedInputStream.java:121)
 > > > 	at w3c.www.mime.MimeParser.parse(MimeParser.java:177)
 > > > 	at w3c.jigsaw.http.Client.getNextRequest(Client.java:275)
 > > > 	at w3c.jigsaw.http.Client.loop(Client.java:512)
 > > > 	at w3c.jigsaw.http.Client.runConnection(Client.java:642)
 > > > 	at w3c.jigsaw.http.Client.run(Client.java:620)
 > > > 	at java.lang.Thread.run(Thread.java:294)
 > >
 > >That's normal, the bug is probably that Jigsaw displays the trace
 > >(unlesss you were in trace mode ?)
 > 
 > I was not in trace mode - why does java.net.SocketInputStream.read through
 > the exception at all?

Because Jigsaw uses persistent connections for HTTP (ie m,ultiple
requests can use the same connection). A connection can be closed
either by the server or by the broswer.

In the above case, your browser did close the connection, so Jigsaw
got that exception (and handled it properly). All this is compliant to
the specs, again, the bug is that you saw the trace...

Anselm.

Received on Monday, 25 November 1996 05:28:46 UTC