Utilities: Administration: Server: Server Settings: Machine Settings: Database Timeouts
If your database is exceptionally large, you may experience performance issues. In extreme cases, the web server can lock up waiting for a database connection due to long running database queries. To prevent this, you can specify database timeouts on the Database Timeouts page in ListManager. Recommended values are listed in the table below; you can fine-tune as necessary.
You can also set timeout values in the lmcfg.txt file.
|
Name |
Description |
Recommended Value |
|
|
|
|
|
Default Pool |
Pool timeouts not defined by any other timeout type |
-1 (disabled) |
|
|
|
|
|
Default Command |
Command timeouts not defined by any other timeout type |
3600 (2 hours) |
|
|
|
|
|
List Posting |
Task that handles the processing of an incoming mailing. |
3600 (2 hours) |
|
|
|
|
|
Nightly Jobs |
Used for nightly jobs. |
3600 (2 hours) |
|
|
|
|
|
Incremental Update |
Update summary statistics for only those mailings that have changes since the previous update |
600 (10 minutes) |
|
|
|
|
|
TCL Port Pool |
Timeout to get a TCL port command connection |
60 (1 minute) |
|
|
|
|
|
TCL Port Command |
- Timeout when TCL port command takes too long
- Used for GUI (web server) transactions (HTTP GETs and REQUESTs) |
60 (1 minute) |
|
|
|
|
|
Master Thread Pool |
Timeout to get a master thread command connection |
1 (1 second) |
|
|
|
|
|
Master Thread Command |
- Timeout when Master thread command takes too long
- Used to accept incoming socket connections |
1 (1 second) |