> 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. So
it looks like there might be something that's changed that needs a looking
after. I doubt that the limit really has been hit, so much as there being
some rare event that causes the connection manager to *THINK* that there are
open connections.
If you can still reproduce the leaking connections, please enable for the
connection manager logs in SAR-INF/environment.xml. We'll start to track
this thing down, and nail it before the Release.
Anyone who sees that message in the connections log should please let us
know.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
