Errors can occur during many different processes, basically any process that attempts to get a connection after the defined pool has been used.
This has been noted with some of the following.
Failed to get status of destination replication job. jobId:{f22f3dec-9c28-4ad4-baaa-ed31bd8f63c9}, operationId:{dbc77bf4-b557-4edc-82d4-cbb6e75e1263}, stage:Wait, type:Export, itemType:Item, status:InProgress
Server was unable to process request. ---> Failed to construct DatabaseContext object. Connection to database failed. ---> Failed to open database connection. Current user is Symantec\altrisadmin. Error: Exception has been thrown by the target of an invocation. ---> Exception has been thrown by the target of an invocation. ---> Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
When a connection string is created to an SQL server, there is an option to define how many connections it can use. By default the connection string for the Symantec Management Platform is set to 200 (prior to SMP 7.6 HF6). This message happens when the defined amount of connections has been exceeded. When there are too many very slow/long connections from clients, these can use out whole DB pool quickly.
Starting with SMP 7.6 HF6, the default value for DBMaxPoolSize was increased from 200 to 400.
Prior to SMP 7.6 HF6:
Steps to increase the pool size:
Post to SMP 7.6 HF6:
Steps to increase the pool size: