All collectors are in running state

[shaktinayak]

All collectors are in running state and is not getting completed. we have tried restarting the application , the collectors get aborted and again when we run the same issue.

What might be the issue . this is affecting the production environment.

[AzamMuhamad]

In Monitoring - Thread Information. Could you filter the threads to State=RUNNABLE and see if there any threads stuck at socketRead etc. If so, please share the stacktrace in full.

You may raise RSA Support case if you require urgent assistance.

[IanStaines · Accepted solution]

Are you certain all of your collectors are in "Running" state?  Normally collectors are scheduled sequentially and at any one time one collector will be in "Running" state but all other collectors will be in "New" state.  A particular collector staying in "Running" state is considered a failure of that collector and we troubleshoot it accordingly.

There is a failure mode that may cause a particular collector to remain in the "Running" state without moving to completion.  Any failure mode where the collector is reachable, but does not return a result can result in the collector running indefinitely.  This is uncommon but may occur typically with AD collectors.  See the following KB article. 

https://community.rsa.com/docs/DOC-103808 

There are some other potential failure modes similar to this but they are rare.  I recommend you open a support case for your specific issue.