On Fri, 2004-02-13 at 15:30, Michael Nestler wrote: > I will send the netstat output if it should happen again. Yes, I had a > connection limit of 30 (increased it now to 120) - but the connections > were not release for 6 hours. James started logging >
Make sure you have anougth threads configured to open 120 connections > 12/02/04 02:29:38 WARN connections: Maximum number of open connections > exceeded - refusing connection. Current number of connections is 30 > > and continued doing this once every few seconds until I stopped it when > I came to work in the morning: > > 12/02/04 08:11:19 WARN connections: Maximum number of open connections > exceeded - refusing connection. Current number of connections is 30 > 12/02/04 08:11:21 DEBUG connections: Disposing server > [EMAIL PROTECTED] > 12/02/04 08:11:21 DEBUG connections: Closed server connection - cleaning > up clients - [EMAIL PROTECTED] > 12/02/04 08:11:21 DEBUG connections: Cleaned up clients - > [EMAIL PROTECTED] > 12/02/04 08:11:21 DEBUG connections: Disposing server > [EMAIL PROTECTED] > 12/02/04 08:11:21 DEBUG connections: Closed server connection - cleaning > up clients - [EMAIL PROTECTED] > > So, yes it used all connections in the pool - but they were never > released. That is my problem. > > Michael > > > > Noel J. Bergman wrote: > > >Michael, > > > >You can use netstat | grep smtp to check, but I suspect that James is > >working as designed. It appears that you have a connection limit of 30, and > >really do have 30 simultaneously active connections. > > > > --- Noel > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
