The timeout comes most probable from the database.
Every database has a predefined timeout. Usually on the clients side there is a parameter for the time wainting for an answer from the server.
There are some solutions for your problem:
First try whether your database is the one giving you this problem. It could be a timeout for example from IP or a wrong routing when e.g. the firewall interrups the traffic.
Then check whether your connection parameters are right. A wrong port number could give you the head ache.
If you identify the database as the one making the timeout: Rise the connection timeout in your database. There is usually an entry in a configuration file or depending on database and OS an environment variable. Rise the limit of open connections if it is a problem of too many open (and probably in parts idle) connections. If you have lots of users try pooling.
LeuchukIn reply to Re^2: DBIx::Connector timeout?
by leuchuk
in thread DBIx::Connector timeout?
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |