Noel J. Bergman wrote: Noel,
> > 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. If you are seeing this problem when running fetchmail or fetchPOP, would it be possible for you to rerun with these disabled so that we can see if the problem goes away? This would enable us to start to isolate the cause. > 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. 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. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
