DEBUG messages for HTTPClient.registerOtherProtocols() are spamming the MID Server log, when debug logging is not turned on - Known Error

DEBUG messages for HTTPClient.registerOtherProtocols() are spamming the MID Server log, when debug logging is not turned on Description Since Paris and Orlando Patch 6, DEBUG messages for HTTPClient.registerOtherProtocols() are spamming the MID Server agent log, even though MID Server debug log level is the default "info". This doesn't appear to affect functionality, but makes the logs a lot less readable, and causes quicker rotation and loss of the older logs.

Steps to Reproduce

This has been seen on customer MID Servers to start after a Paris Patch - Hotfix 1 to Paris Patch 1 upgrade. I has also been seen on Orlando Patch 6.

Install a new Paris MID Server, using the MSI installer (taking into account workarounds for known problems KB0855251 /KB0858646) Start the MID Server and tail the .agent/logs/agent0.log.0 file There will have been no debug parameters added to this mid server, because it is a fresh install. The mid.log.level should be the default .

Inspect the agent log, and it will show thousands of DEBUG entries, for various threads. In some cases this can account for nearly half the rows in the log. e.g.

09/21/20 01:23:59 (751) MIDServer DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[MIDServer,5,main]. 09/21/20 01:24:26 (423) StartupSequencer DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[StartupSequencer,5,main]. 09/21/20 01:25:29 (220) File sync worker: ecc_agent_script_file DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[File sync worker: ecc_agent_script_file,5,main]. 09/21/20 01:25:29 (220) File sync worker: mid_server_tools DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[File sync worker: mid_server_tools,5,main]. 09/21/20 01:25:29 (251) File sync worker: ecc_agent_mib DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[File sync worker: ecc_agent_mib,5,main]. 09/21/20 01:25:29 (267) File sync worker: ecc_agent_jar DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[File sync worker: ecc_agent_jar,5,main]. 09/21/20 01:25:29 (876) File sync worker: ecc_agent_script_file DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[File sync worker: ecc_agent_script_file,5,main]. 09/21/20 01:26:21 (325) StartupSequencer DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[StartupSequencer,5,main]. 09/21/20 01:26:35 (138) AMBClientProvider DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[AMBClientProvider,10,main]. 09/21/20 01:27:08 (482) AutoUpgrade.3600 DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[AutoUpgrade.3600,5,main]. 09/21/20 01:27:09 (467) ECCQueueMonitor.40 DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[ECCQueueMonitor.40,5,main]. 09/21/20 01:27:10 (919) Thread-120 DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[Thread-120,5,main]. 09/21/20 01:28:00 (118) Worker-Interactive:HeartbeatProbe-afc93c8b1b931410254542e7cc4bcb2a DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[Worker-Interactive:HeartbeatProbe-afc93c8b1b931410254542e7cc4bcb2a,10,Interactive Thread Group]. 09/21/20 01:28:01 (055) ECCQueueMonitor.1 DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[ECCQueueMonitor.1,5,main]. 09/21/20 01:28:35 (358) RefreshMonitor.65 DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[RefreshMonitor.65,5,main]. 09/21/20 01:28:35 (415) ECCSender.1 DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[ECCSender.1,5,main]. 09/21/20 01:28:36 (946) Worker-Interactive:SystemCommand-e0f9744b1bd714107e63415bbc4bcb11 DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[Worker-Interactive:SystemCommand-e0f9744b1bd714107e63415bbc4bcb11,10,Interactive Thread Group]. etc. Workaround This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.