I had the same error for quite some time, the issue seemed to be server resources not being able to kill off connections quickly enough. We had a lot of traffic and some pretty slow queries. Optimizing the queries bought us some time, but ultimately we had to upgrade hardware. This bought us about a year and we are against the wall again now with the 1040 issue. We are probably going to get another server and set up replication.
I'd be interested to hear anyone elses stories around this issue, it's been quite a headache for us... Quoting A Z <[EMAIL PROTECTED]>: > > > Hi, > > MySQL 4.0.14 > > This may have been queried a lot here. > > We get this error and after re-starting the server > (MySQL) it seems to go away for a while. > > As per instructions we have changed the max connection > in the My.ini to 500 (max_connections=500). > MySQLAdmin displays connections = 120. > > Is there anything else we can do to deal with this > issue? > > regards > > > > > > > ___________________________________________________________ > ALL-NEW Yahoo! Messenger - all new features - even more fun! > http://uk.messenger.yahoo.com > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
