#19 Non-functional on Linux/ Sun Java 1.5 with certain browsers

I'm running Debian testing, Linux 2.68, and Sun Java
1.5.0 and I get the following error, resulting in the
client not working at all.

[ERROR] [01-29-2005 11:08:32]
dijjer.io.xfer.Downloader$Request.request(line:283)
Exception while writing data to http client
java.net.SocketException: Connection reset
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
at
java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
dijjer.util.TruncatingOutputStream.write(TruncatingOutputStream.java:56)
at
dijjer.io.xfer.Downloader$Request.request(Downloader.java:281)
at
dijjer.io.xfer.Downloader.download(Downloader.java:71)
at
dijjer.io.xfer.http.handlers.DownloadResponse.writeTo(DownloadResponse.java:41)
at
dijjer.io.xfer.http.HTTPResponse.write(HTTPResponse.java:28)
at
dijjer.io.xfer.http.HTTPRequestHandler.threadLoop(HTTPRequestHandler.java:34)
at
dijjer.util.AbstractThread.run(AbstractThread.java:60)
at java.lang.Thread.run(Thread.java:595)

[Anonymous]

Logged In: YES
user_id=48482

I also get this error sometimes:

java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native
Method)
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at
java.net.SocketOutputStream.write(SocketOutputStream.java:124)
at
dijjer.io.xfer.http.handlers.GIFResponse.writeTo(GIFResponse.java:37)
at
dijjer.io.xfer.http.HTTPResponse.write(HTTPResponse.java:28)
at
dijjer.io.xfer.http.HTTPRequestHandler.threadLoop(HTTPRequestHandler.java:34)
at
dijjer.util.AbstractThread.run(AbstractThread.java:60)
at java.lang.Thread.run(Thread.java:595)
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native
Method)
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at
java.net.SocketOutputStream.write(SocketOutputStream.java:124)
at
dijjer.io.xfer.http.HTTPResponse.write(HTTPResponse.java:27)
at
dijjer.io.xfer.http.HTTPRequestHandler.threadLoop(HTTPRequestHandler.java:45)
at
dijjer.util.AbstractThread.run(AbstractThread.java:60)
at java.lang.Thread.run(Thread.java:595)
[ERROR] [01-29-2005 11:08:25]
dijjer.util.AbstractThread.run(line:66) Subclass process
threw an exception
java.lang.RuntimeException: java.net.SocketException: Broken
pipe
at
dijjer.io.xfer.http.HTTPRequestHandler.threadLoop(HTTPRequestHandler.java:50)
at
dijjer.util.AbstractThread.run(AbstractThread.java:60)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketException: Broken pipe
... 3 more

[Anonymous]

Logged In: YES
user_id=2857

Hmmm, these errors indicates that your HTTP client closed
the connection unexpectedly. It typically happens when a
user aborts a download in their web browser. I'm not sure
that this is the cause of the failure you are reporting -
what other symptoms are there? When you say that the client
is not working, do you mean that the web interface is
no-longer reachable, or that dijjer actually terminates?

[Anonymous]

Logged In: YES
user_id=48482

the HTTP interface is no longer reachable

[Anonymous]

Logged In: YES
user_id=2857

This isn't a bug, it just indicates that the HTTP client died.

[Anonymous]

Logged In: YES
user_id=48482

The bug isn't the error message. The bug is the fact that
the client doesn't work relaibly for me.

After a bit more experimentation, I've found that Dijjer
never works with the Galeon, Epiphany, or Konqueror web
browsers. It does work with FireFox.