Alex Osborne 1832c5ef89 FetchDNS: Keep dnsjava selector thread out of ToePool ...

dnsjava will create its global selector thread on first DNS lookup.
Since the first lookup occurs on a toe thread then this will cause the
selector thead to join the job's toe thread group. This is a problem
because when the job is terminated ToePool sends an interrupt to all
threads in the thread group which the dnsjava selector thread is
not expected and never clears. The interrupted state then causes
select() to return immediately instead of sleeping so it consumes
100% CPU.

So workaround this by doing a dummy lookup when FetchDNS is loaded,
this ensures the first lookup happens on the web server thread that
handles the job build action instead of a toe thread.

Fixes: 045b2516da ("Update to latest version of dnsjava")

2021-11-01 16:15:27 +09:00

..

src

FetchDNS: Keep dnsjava selector thread out of ToePool

2021-11-01 16:15:27 +09:00

pom.xml

[maven-release-plugin] prepare for next development iteration

2021-09-23 22:08:33 +01:00