Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-4313: Connection pool error when max pool size is default to 300

Auditing and Monitoring Service ,  

12 April,16 at 10:57 AM

Applies to:
 
DirectAudit earlier than 2014.1
 
Problem:
 
The following message is seen in Collector. The collector has to be restarted frequently. 
 
Is there any reason for this?
 
[Date Time] collector.exe [6644,985] Error: CollectorServer.UpdateAgentStatus: The DirectAudit Collector was unable to update the Agent status table in the Audit Store database for Agent 'FQDN-SERVERNAME'. The DirectAudit Administration Console will not properly reflect the running status of this Agent. Detailed error information: Timeout expired. The timeout period elapsed prior to the obtaining a connection from the pool.
 
Cause: 
 
This may have occurred because all pooled connections were in use and max pool size was reached. Collector service maintains a SQL Server connection pool with 300 connections. When there are more than 300 machines sending data to the collector concurrently, the collector cannot handle all the requests and it will stop completely. 
 
Answer:
 
To remedy the problem, there are two options.
 
Option 1: Add additional collectors to the Audit Store. This will offload the load balance from the busy current collector. 
 
Option 2: Increase the number of connections that SQL Server can pool. The number of connections in the SQL Server connection pool can be set using the following registry key with the type of DWORD (Decimal value). The value can be set to say 2000.
 
Add DWORD (Decimal value) value: MaxPoolSize
HKLM\Software\Centrify\DirectAudit\Collector
 
By default, MaxPoolSize is not present. This is a manual change.
 
Restart collector and DirectAudit service (Windows side).  

To verify if MaxPoolSize is now set to for example to 2000, change the Diagnostic level to 'Verbose' in DirectAudit Collector Control Panel (click 'Configure' button).
 
To summarize, please note the following:
 
DA versionDefault pool sizeConfigurable?
Before Suite 2013.3300No
Suite 2013.3 onwards300Yes (using Collector registry settings)
Future release (Suite 2015)1000Yes (using Collector registry settings)

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-1311: Collector unable to connect to SQL database articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6388:In centrifydc.log, what does 'Pool size' and 'busy size' mean? articleKB-2182: Why is Collector trying to bind as an anonymous user articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-2109: Are there any sizing guides to help plan for scalability and storage requirements for DirectAudit? article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part III