PowerConsole threads are not efficiently made available to the pool, resulting in lowered Discovery performance - Known Error

PowerConsole threads are not efficiently made available to the pool, resulting in lowered Discovery performance Description You note that during high Discovery volume that performance will take hours/days to execute a single classify probe or pattern.

When taking a thread dump you'll note that the threads are in "TIMED_WAITING" state with locks similar to: at com.service_now.mid.win.powershell.api.PowerConsole.executeCurrentCommand(PowerConsole.java:274) - waiting to re-lock in wait() &lt;0x0000000716e4a2d0&gt; (a java.lang.Object)

Steps to Reproduce

Run Discovery schedule, which will use PowerShell related probes on all 25 standard threads simultaneously. Workaround This problem is currently under review and has no workaround. To receive notifications when more information will become available, subscribe to this Known Error article by clicking the Subscribe button at the top of this article. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.