Which of the following best describes what may also be required when increasing the max number of threads for a MID Server?

When adjusting MID Server performance parameters by increasing the maximum number of concurrent threads (threads.max), the MID Server will process more Discovery probes, patterns, and simultaneous background tasks. This elevated concurrent workload directly consumes more Java Virtual Machine (JVM) heap memory. Consequently, ServiceNow strongly recommends that administrators monitor memory utilization and proportionally increase the maximum memory allocated to the MID Server application (typically adjusted via the wrapper.java.maxmemory setting in the wrapper-override.conf file). Failing to increase allocated memory when aggressively scaling thread counts can rapidly lead to JVM OutOfMemoryError conditions, causing the MID Server to crash, restart unexpectedly, or become entirely unresponsive during extensive localized Discovery schedules.

A. increase the amount of disk space on the MID Server host: Thread adjustments primarily impact CPU and RAM utilization, not the persistent disk storage space required by the host.
B. updating the acl rules for the CMDB tables in ServiceNow: MID Server thread configurations are strictly local infrastructure tuning and do not affect or require instance-side ACL modifications.
D. increase the MID Server max payload size: Payload size parameters dictate the maximum allowed size of individual XML payloads, which is functionally distinct from concurrent thread processing capacity.

ServiceNow Product Documentation > IT Operations Management > MID Server > MID Server configuration > MID Server parameters. Section: "threads.max".

ServiceNow Support Knowledge Base > KB0597561 > Tuning MID Server JVM Memory.