Steve,
> > > I suspect this will fix my leaked POP3 connections too.
>
> > I am not so sure, unfortunately. So please let me know what
> > you experience.
> > My production server ran James v2.2.0a8-ish (something
> > between 2.2.0a8 and 2.2.0a9) pretty much non-stop from
> > July 12th until last week when I put 2.2.0a12 into service.
> > Ironically, *yesterday* while I was travelling for the
> > first time since May, the "Maximum connections" problem
> > cropped up.
> Unless under 2.2.0a12 you were running either fetchmail or fetchPOP we can
> rule out both as the cause of your "Maximum connections" problem and what
> we have here is a new problem.
I don't run either, nor do I suggest that they have anything to do with the
problem. I have turned on debug for the connection manager, and so far
everything is flawless. If this were easily reproduced, I'd think we'd have
seen it by now, but I am going to do a code audit of the possible leak
paths, probably on the 9 hour drive home next week. If others have time to
take a look, that would be great.
> If you are thinking that fetchPOP or fetchmail might not be releasing
> connections, their consumption of connections is not going to be
> directly illuminated by enabling connection manager logging, as
> neither fetchPOP or fetchmail use a ConnectionManager.
Which is why I don't think that his problem is related to Fetch___, either.
A priori, I would guess at some sort of Throwable caused leak, but that's
just because I cannot think of anything more likely at the moment.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
