Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SAM Stops polling

I am troubleshooting why SAM stops to poll while running on an additional poller. I am not sure but i think restarting the module engine service on the Orion server fixes the issue. Looking through all logs the only line that looks suspicious is on the additional poller in the APM BusinessLayer log. Does this look familiar? We are running SAM 5.0.0 RC. Thanks

WARN SolarWinds.APM.BusinessLayer.JobResultProcessing.JobManagerBase`1 - Number of received items is too large and exceeds max queue length - queue name: JobResult, current queue size: 7500, max size: 7500, items received: 5

Find more posts tagged with

Accepted answers

lukas.belza

Hello,

We had one issue with following description: 'Orion Module Engine' service on Primary Orion must be running before this service starts on Additional Poller. If Primary Orion is not running when Additional Poller is starting, then Additional Poller is not started properly and ends up in a weird state when it is running, but it's not doing anything (not processing polling job results).

This issue was fixed in SAM 5.0.1 Service Release that is available.

Regarding following warning message in the APM.BusinessLayer.log file:

"WARN SolarWinds.APM.BusinessLayer.JobResultProcessing.JobManagerBase`1 - Number of received items is too large and exceeds max queue length - queue name: JobResult, current queue size: 7500, max size: 7500, items received: 5"

It means that the poller isn't able to save all data to the database. It could be caused by overloading of the database (e.g. during maintenance), bad connectivity to the database... At this moment SAM can start to discard the job results. Also it's possible to see the job result queue size using performance counters to see if this problem occurs randomly or all the time (also available in SAM 5.0.1 Service Release).

If you see a lot of this warning messages in the APM.BusinessLayer.log file, please open support ticket to assist you to find where is the problem.

Thanks you,

Lukas Belza (SolarWinds development)

All comments

aLTeReGo

At a minimum I would recommend upgrading to the GA version of SAM 5.0. There was an issue identified in SAM 5.0 RC3 that sounds very similar to the one you describe here, which prompted us to release an RC4 that eventually became the GA release for SAM 5.0. Currently SAM 5.0.1 is in the release candidate phase and includes additional fixes. Direct Message me if you'd like to receive the SAM 5.0.1 RC.

vsta

Is this fixed?

lukas.belza

Hello,

This issue was fixed in SAM 5.0.1 Service Release that is available.

Regarding following warning message in the APM.BusinessLayer.log file:

If you see a lot of this warning messages in the APM.BusinessLayer.log file, please open support ticket to assist you to find where is the problem.

Thanks you,

Lukas Belza (SolarWinds development)

bwicks

Thank You. Yes we have installed 5.0.1 and we are no longer seeing issues with SAM polling stopping. I will review our logs for errors and start collecting SAM job result performance counters. Thanks again for your help

bwicks

We are seeing SAM stop polling on an additional poller when we remove all sdf files "in collector and jobengine2" and restart all services on the poller. Seems we have to restart the module engine service on the Orion server for SAM to start polling again.. is this expected behavior. Thanks

lukas.belza

Hello bwicks,

Yes this is the expected behavior. When you replace the SDF files with blank ones, the information about jobs are lost and it is necessary to reschedule all jobs. SAM module schedules jobs from Main poller, so the restarting SolarWinds Orion Module Engine service on Main poller is necessary for rescheduling all SAM jobs on all pollers.

Lukas Belza (SolarWinds development)

bwicks

Thanks