Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We get the following Coldfusion error message after our server have been running for a couple of weeks:

Error Executing Database Query.Could not create connection to database server. Attempted reconnect 3 times

We run Coldfusion Enterprise 9 on a one year old XServer with Snow Leopard and MySQL 5 The server has about ten DSN set up in the Coldfusion Administrator All local, with default advanced settings, and host set to "localhost" The server is not under heavy load.

The strange thing is that after a restart of the server, everything works fine. Then after a week or so, some databases will stop working, in the sense that Coldfusion cannot create a connection to them. If I then go to the Coldfusion Administrator and click "Verify all datasources", I will get that only 2 or 3 got verified, the other ones failed, and it is always the same datasources that can't be verified when the server starts to behave like this if I try to verify again, BUT NOT neccessary the same datasources that couldn't be verified the last time the server behaved like this.

I know about the setting "max_connections" and we have included a line for that setting in the MySQL config file and set it to 2000, and when we read it by a query it says "2000", so that can't be the problem.

There's no useful info in the mysql_service.log We have also tried flushing the hosts, as I read about in one forum, to check if the MySQL server has "banned" our user, without result.

Anyone?

share|improve this question
add comment

1 Answer 1

if you type "netstat -an | grep 3306" on the mysql server do you see many many open socket ("ESTABLISHED"), if this is more than the number of sockets mysql is configured to allow open, then something is locking up and holding on to all the database pool handles.

it could be a problem in mysql, but is more likely to be an application problem not releasing handles back to a pool, similar to a memory leak.

it's rather hard to diagnose the problem without more information, but that's where I'd start.

share|improve this answer
    
We just got the problem again this morning, and tried with netstat, and got one row with 127.0.0.1.53306 and one with 127.0.0.1.63306. Both had state CLOSE_WAIT. We've googled some more and will test using the server's actual IP-number when connecting, and not localhost (forums.adobe.com/thread/656969#2987022). Will come back later. –  user1503757 Jul 26 '12 at 7:50
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.