Hello all,
We are currently running into the issue of the SW Job Scheduler Service periodically dying (id say once every 2 weeks) and not being able to restart. We have opened troube tickets with support and tried the recommended replacement of "JobEngine35.sdf" and also made sure there are no duplicate nodes are present.
Both of these fixes seem temporary for a larger underlying issue that quite a few of users on thwack seem to be experiencing. I am currently running NPM v9.5.1, 2 polling engines, 2 hot standby engines, 1 additional webserver.
This issue of the Job Scheduler Service is only occuring on our primary polling engine. I am starting to think there is an issue with our custom pollers due to the fact that once the service is stopped none of our custom data is collected. We currently have 151 custom pollers running on our primary polling engine, is there a recommended amount we should be limiting ourselves to? If so is this documented anywhere?
thanks,
Matt
