tree f02d74ef132a0e2b741cd47227ae7028a2ccb832
parent f6ea51ae6b55497a6f0b01de31d450bad275958b
author Saša Živkov <sasa.zivkov@sap.com> 1579255951 +0100
committer Saša Živkov <zivkov@gmail.com> 1579512952 +0000

Set HTTP thread name to describe the request it is processing

The HTTP worker threads had generic names: HTTP-100, HTTP-101, ...
While we could conclude from the stack trace what this thread was doing
we missed some important information like repository name, user name,
etc...

With this change the HTTP threads get descriptive names. For example, if
there is an ongoing git-fetch operation we would see a thread named
like:

"HTTP POST /a/myProject/git-upload-pack (johndoe from 10.87.75.169)"

This can be of a great help for Gerrit admins trying to figure out who
is executing that many git-fetch requests and affecting the overall
performance.  Note that we cannot reliably tell that from the httpd_log
as requests are logged only once they are finished. The show-queue
command also doesn't show tasks being processing in the HTTP thread
pool.

As additional justification, SSH thread names are already named with a
similar pattern i.e:

"SSH git-upload-pack /myProject (johndoe)"

Change-Id: I98cf112018732e5d4075568e7da8614ffe0495a4