How to monitor pool (Max Pool Size=1000;)

Hi All, I want to know how to monitor pool (Max Pool Size=1000;)

Event Error messages: Service was unable to open new database connection when requested. TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool. Connection string - Data Source=xyz;Initial Catalog=SolarWindsOrion;Persist Security Info=False;User ID=xyz;Password=*******;Max Pool Size=1000;Connect Timeout=20;Load Balance Timeout=120;Packet Size=4096;Application Name=SolarWinds.Alerting.Service@SolarWinds.Alerting.Service.exe;Workstation ID=ABC

Parents
  • Following this thread as had the same problem since upgrading 2 weeks ago and looking to track number of pooled connections in place.

    At the moment we have to restart the INFO_V3 service every 60-90 minutes.

    CASE: 00408837

    Service was unable to open new database connection when requested. InvalidOperationException: 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. Connection string - Data Source=xsdwin5002,56566\XSDWIN0026;Initial Catalog=SolarWindsONET;Persist Security Info=False;User ID=SolarWindsUser;Password=*******;Max Pool Size=1000;Connect Timeout=20;Load Balance Timeout=120;Packet Size=4096;Application Name=SolarWinds.InformationService.ServiceV3@domain-Orion; Workstation ID=SERVERNAME

    Latest suggested fix is to upgrade SQL to latest CU as we're about a year out, arranging this outage for tomorrow.

Reply
  • Following this thread as had the same problem since upgrading 2 weeks ago and looking to track number of pooled connections in place.

    At the moment we have to restart the INFO_V3 service every 60-90 minutes.

    CASE: 00408837

    Service was unable to open new database connection when requested. InvalidOperationException: 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. Connection string - Data Source=xsdwin5002,56566\XSDWIN0026;Initial Catalog=SolarWindsONET;Persist Security Info=False;User ID=SolarWindsUser;Password=*******;Max Pool Size=1000;Connect Timeout=20;Load Balance Timeout=120;Packet Size=4096;Application Name=SolarWinds.InformationService.ServiceV3@domain-Orion; Workstation ID=SERVERNAME

    Latest suggested fix is to upgrade SQL to latest CU as we're about a year out, arranging this outage for tomorrow.

Children