System could be dialing slower because {0} is taking more than {1} ms for 10 consecutive requests.
Throttle interval
360
Trigger component
POM Campaign Manager
Cause
This occurs due to one of the following reasons:
For 10 consecutive requests, Campaign Manager takes more than 200 milliseconds to read a record from the POM database.
For 10 consecutive CCXML requests, the App server and MPP server take more than 500 milliseconds to respond.
Solution
Procedure
To identify the cause of the delay in reading records from the POM database, the administrator can read the POM database logs.
To identify the cause of the delay by the App server and MPP server to respond to the CCXML requests, the administrator can read the MPP logs for the extent of CPU usage.
On the POM server, reindex the POM database by running the following script:
$POM_HOME/bin/reindexPOMDB.sh
Clear disk space on the POM server.
The administrator must ensure the following:
The minimum bandwidth of the network is 1 GBPS.
There are no network delays.
Note:
On the POM server, in the pim_config table, in the DB_RECORD_READ_TIME_LIMIT parameter, the duration for POM to read a contact record from the database is 200 milliseconds. This value is set by default. POM uses this parameter while reading records from the POM database. The administration can change this value.
On the POM server, in the pim_config table, in the CCXML_INVOKE_TIME_LIMIT parameter, the time duration in which POM invokes and sends the CCXML request to the App server is 500 milliseconds. This value is set by default. POM uses this parameter while invoking CCXML requests to be sent to AppServer. The administration can change this value.
