> > > I can see two solutions, implement a more standard timeout > > (i.e. inactivity based), or have connections expire more gradually, > > rather than all at once. The second option would probably be a very > > messy solution. > > They do not expire "all at once," since they are created lazily.
You didn't read my post. The site we are using is under incredibly heavy load. If a webserver is restarted at any time other than the middle of the night - ALL the connections get created at once. Have modified the connection pool so if an expiry time of -1 is supplied they connections never expire. Want me to submit a patch? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
