Hi, first of all i whould suggest to upgrade to james 2.3.0. We fixed many bugs in this release.
Please upgrade and test again. bye Norman Am Montag, den 26.02.2007, 16:21 +0100 schrieb Marcello Marangio: > Hi > > There could be a problem with james 2.2.0 in a High Avaliability > environment. > > We set up 2 james instances to work at the same time on the same database > (using a failover connection string). > > There is a load balancer which every few seconds checks if the pop3 server > is alive, without closing properly the pop3 session. > > Every time the check happens we get in the pop3server logs an error message > "Connection reset". > > > > This is the stacktrace: > > > > 26/02/07 14:43:27 ERROR pop3server: Exception during connection from > <ip_address> (<ip_address>) : Connection reset > > java.net.SocketException: Connection reset > > at java.net.SocketInputStream.read(SocketInputStream.java:168) > > at java.io.BufferedInputStream.read1(BufferedInputStream.java:220) > > at java.io.BufferedInputStream.read(BufferedInputStream.java:277) > > at > sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:408) > > at > sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:450) > > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182) > > at java.io.InputStreamReader.read(InputStreamReader.java:167) > > at java.io.BufferedReader.fill(BufferedReader.java:136) > > at java.io.BufferedReader.read(BufferedReader.java:157) > > at > org.apache.james.util.CRLFTerminatedReader.readLine(CRLFTerminatedReader.jav > a:98) > > at > org.apache.james.pop3server.POP3Handler.readCommandLine(POP3Handler.java:415 > ) > > at > org.apache.james.pop3server.POP3Handler.handleConnection(POP3Handler.java:26 > 6) > > at > org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run > (ServerConnection.java:417) > > at > org.apache.james.util.thread.ExecutableRunnable.execute(ExecutableRunnable.j > ava:55) > > at > org.apache.james.util.thread.WorkerThread.run(WorkerThread.java:90) > > > > > > We thought it wasn't harmless, but after a while (more or less an hour) the > system crashes. > > At the moment the problem happens even if there is only one james instance > up and running, i.e. it's not a concurrency problem. > > > > Any help will be REALLY appreciated. > > Thanks > > Marcello > > !EXCUBATOR:1,45e2fb0a39071340968383! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
