mysql_pconnect() too many simultanous connection issue

I designed a registration portal with databridge and my site keeps prompting a warning about too many connections whenever i try to connect to database. After going through a lot of forums, it was suggested that i should used mysql_connect() instead of the persistent version. What are the possible changes i could make to the codes of my pages generated by data bridge to as to be compatible with mysql_connect()?

You can just update the connection file in the Connections folder. That is the only location where the database connection is made.

Often that error occurs because of a server configuration issue. You may want to contact your hosting provider and have them look into it for you as well.

But what i understood about the difference between the two is that, mysql_pconnect() creates a permanent connection for about 8 hrs (by default) and does not close connection with mysql_close() while mysql_connect() closes connection by calling mysql_close() function. If that is the case, changing to mysql_connect() function requires one to close the connection. Must i close the connection on every page that opens that connection?

php should automatically close the connection when the page is delivered to the browser, so unless you were closing it before the end of the page it isn't necessary to close as long as php is working correctly.

If that is case, what is the benefit of implementing the persistence version in data bridge? When i contacted my host they suggested that i should upgrade to a dedicated host to do away with that problem. If i make changes to the connection function and that takes care of the problem automatically, i see no benefit of implementing mysql_pconnect() in your extension.

If that solves the problem then that is a valid solution. It is supposed to persist the connection and re-use the same connection for each user. pconnect should hypothetically cause fewer connections, not more. I'm not sure who your hosting provider is, but the solution is usually to make sure your php server is configured properly as to not cause the problem. However any solution that removes the error is valid.

I was able to track and solve the problem. The problem was due to a php script that is being called by the registration page, which contains a connection to a database that was not closing each time the script executes. i.e. Whenever the script executes, the previous connection is still live. Therefore, whenever the script executes for certain number of times equals to the maximum number of connections set by the server, no more connections were accepted and the error presents.