If Avaya Experience Portal has a large configuration, for example, more than 100 applications, MPP cannot update the configuration before the default timeout. When the EPM does not receive the confirmation from MPP in time, it starts sending repetitive configuration requests, which form an infinite loop.
In this case, the EPM logs can contain the following message: Failed sending Configuration to <MPP name> with error Read timed out.
To troubleshoot this issue, increase the default timeout of the MPP and EPM.
For 100 - 500 applications, increase the timeout to one minute.
For 500 - 1000 applications, increase the timeout to two minutes.
For every 1000 applications thereafter, increase the timeout by a minute. For example, for 2000 applications, increase the default timeout to three minutes. For 3000 applications, increase the timeout to four minutes, and so on.
