BWB Task Failures, first is: Task Queue Full
-
I've been seeing numerous errors of this type in
ma.log
:ERROR 2018-05-22T08:06:16,238 (com.infiniteautomation.nosql.MangoNoSqlBatchWriteBehindManager$StatusProvider.scheduleTimeout:738) - 1 BWB Task Failures, first is: Task Queue Full │········
Which System Setting changes can eliminate this error?
What symptoms would this error lead to?
We are sometimes not receiving emails of critical events. Could this be the cause?Thread Pools:
High priority core pool size = 60
High priority maximum pool size = 15000
Medium priority core pool size = 6
Low priority core pool size = 8I have not found anything substantially relevant in the forum search.
Thanks, -
Hi Pedro,
Which System Setting changes can eliminate this error?
You could slow down the point data mover and status provider by increasing the "Batch process manager period (ms)" and the "Status update period (ms) " in the NoSQL section of the system settings. Also, if you are fully up to date, these messages have been removed entirely since they're mostly clutter.
What symptoms would this error lead to?
None. This would be more indicative that a garbage collection lasted longer than the intervals specified for the two tasks in part 1 of this response.
We are sometimes not receiving emails of critical events. Could this be the cause?
No. You should have an error in your log file about being unable to send an email if the error was known before the actual relay of the mail was handed on to the SMTP server. If you do not have an error about sending a test email when you try to send a test email, then either your SMTP provider isn't forwarding it or it's being filtered out of your inbox.