Verbose Logging shows the same message excessively

[Rick Schultz]

When I updated the log4j logger within the jar to have more verbose debug logging on, the following message appears consistently about 25 times every 10 seconds.

2014-01-25 20:08:33,788 Idle HTTP Connection Closer Checking for connections, idleTimeout: 1390698393788
2014-01-25 20:08:33,788 Idle HTTP Connection Closer Checking for connections, idleTimeout: 1390698393788
2014-01-25 20:08:33,788 Idle HTTP Connection Closer Checking for connections, idleTimeout: 1390698393788
2014-01-25 20:08:33,788 Idle HTTP Connection Closer Checking for connections, idleTimeout: 1390698393788

This fills up the logs and rolls off potentially useful log messages. My changes to the file were to simply follow the prescribed uncommenting of the first section and commenting out the second section, per the file's instructions.

1. Is this an issue?

2. What is the recommended setting to get meaningful logging that can help diagnose real problems, yet filter out these types of messages.

This is really hindering our ability to troubleshoot the plugin when it hangs up. We're unable to send meaningful exception logs.

Thanks!

[Andrzej Pasterczyk]

Hi,

1. Not an issue. Those are messages returned from Microsoft TFS SDK

2. It will sound bad but we actually have not found a good way to filter out those messages. There's no documentation from Microsoft on such configuration. It should be possible but numerous attempts to set it up failed.

[Rick Schultz]

Perhaps isolating the code handling that request then applying a more granular logger for that. We could then set that specific package logger to WARN which should then filter out those messages. Solving this should be quite critical, given the inabililty to apply debug logging due to those messages.