Hi,
I am afraid that with a simple java program that performs very fast socket
open/reset james can crash, which would be a serious bug.
You haven't told us about your environment. On Java Production Servers
under Linux with many open sockets I usually have to change the nofile
Parameter in sec
Hi
A bit of news.
We increased the check delay of the load balancer from 30 secs to 180 secs
and he system is still up and running from 48 hours.
It seems that the load balancer "is alive" check is a simple socket's
open/reset operation on the port 110 (that's why the "connection reset"
exception o
ilto:[EMAIL PROTECTED]
>> Inviato: lunedì 26 febbraio 2007 19.34
>> A: James Users List
>> Oggetto: Re: POP3 problem in a HA environment
>>
>> Hi,
>>
>> first of all i whould suggest to upgrade to james 2.3.0. We fixed many
>> bugs in this release.
>>
&g
I would like to, but will my mailets and matchers be compatible?
M
> -Messaggio originale-
> Da: Norman [mailto:[EMAIL PROTECTED]
> Inviato: lunedì 26 febbraio 2007 19.34
> A: James Users List
> Oggetto: Re: POP3 problem in a HA environment
>
> Hi,
>
> first
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.
On 2/26/07, Marcello Marangio <[EMAIL PROTECTED]> wrote:
We thought it wasn't harmless, but after a while (more or less an hour) the
system crashes.
I'm surprised by this, it *should* be the server giving up on a
hanging connection and should be reclaiming resources not leaking
them.
I don't
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 pr
