12/10/04 16:34:34 ERROR nntpserver: NNTP Connection has idled out.
12/10/04 16:34:34 ERROR nntpserver: Exception during connection:socket closed
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(Unknown Source)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(Unknown Source)
at sun.nio.cs.StreamDecoder.read(Unknown Source)
at java.io.InputStreamReader.read(Unknown Source)
at java.io.BufferedReader.fill(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at org.apache.james.nntpserver.NNTPHandler.handleConnection(NNTPHandler.java:426)
at org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run(ServerConnection.java:417)
at org.apache.james.util.thread.ExecutableRunnable.execute(ExecutableRunnable.java:55)
at org.apache.james.util.thread.WorkerThread.run(WorkerThread.java:90)
12/10/04 16:34:35 ERROR nntpserver: NNTP Connection has idled out.
12/10/04 16:34:35 ERROR nntpserver: Exception during connection:socket closed
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(Unknown Source)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(Unknown Source)
at sun.nio.cs.StreamDecoder.read(Unknown Source)
at java.io.InputStreamReader.read(Unknown Source)
at java.io.BufferedReader.fill(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at org.apache.james.nntpserver.NNTPHandler.handleConnection(NNTPHandler.java:426)
at org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run(ServerConnection.java:417)
at org.apache.james.util.thread.ExecutableRunnable.execute(ExecutableRunnable.java:55)
at org.apache.james.util.thread.WorkerThread.run(WorkerThread.java:90)
It seems to me that James doesn't send correctly the end information to the client to end the communication. Or Mozilla and Jakarta Common-Net doesn't know when the communictaion has ended, but.... it is 2 against 1. :-)
Have you seen this behavior before?
Thanks in advance,
Chemi.
Chemi wrote:
Hi. I have downloaded James to do some NNTP tests.
I have created several news groups and post some messages to them (using Mozilla 1.7.3).
The problem is accessing to those posts. It is really slow showing the body of the messages (the headers appear instantly). After some tests I was able to confirm that it shows the body after exactly 4 minutes. I did the access once again from Mozilla 1.7.3 and also from a Java Test Client I developed with Jakarta-Commons-Net. In both cases I get the body after 4 minutes.
It seems to me that 4 minutes is some kind of time-out internally in James. I did a search within Config.xml file but I didn't find that number. Any idea? The POP3 access hasn't this problem.
I also did the test via Telnet (port 119) sending directly NNTP Commands and in that case I get the body instantly with no delay.
Any idea? Any help?
Thanks in advance,
Chemi.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
