SQL pool errors since CWA 2021.10

Post Reply
SteveITS
Posts: 5
Joined: Wed Oct 09, 2019 4:27 pm
3

SQL pool errors since CWA 2021.10

Post by SteveITS »

Since we installed the 2021.10 patch we have had to restart either the LTAgent service or the CWA server daily to avoid SQL pool errors. Otherwise after about 2-2.5 days we start getting this error in the LTAErrors.txt log file:

1) Plugin Misses error: 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.

Followed a few hours later by:

2) Unable to connect to database: System.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.

...and monitors and scripts eventually stop working, and finally agents stop checking in. After disabling this plugin, and disabling ETL log file processing (which I'm told is off by default on new installs) the errors have not recurred in 5 days.

Looking back the Plugin_PrinterStatus_Errors.txt has the following recurring error dating back at least to 2020:
Plugin Error PrinterStatus, Version=0.1.0.6, Culture=neutral, PublicKeyToken=null: SetSQLYou have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1:::

As you can see we have also tried updating to the recently released v1.0.6 which did not help.

User avatar
Cubert
Posts: 2134
Joined: Tue Dec 29, 2015 7:57 pm
6
Contact:

Re: SQL pool errors since CWA 2021.10

Post by Cubert »

Ok That's a new one, Let me go have a peek at the code base, It may need some updates to it.

User avatar
Cubert
Posts: 2134
Joined: Tue Dec 29, 2015 7:57 pm
6
Contact:

Re: SQL pool errors since CWA 2021.10

Post by Cubert »

Also just for shits and grins,

You said you also had to change the following "disabling ETL log file processing"

Did you happen to turn back on Printer status and see if the same result returned after this change?

Lastly could you send us a sample of the log, the timing and dates will help us determine what process was calling that.

Post Reply

Return to “Printer Status Plugin”