Given a container has been started via the yet-another-docker-plugin (and possibly any other cloud provider), and leaving the JNLP process to reconnect (ie, no --no-reconnect flag)

Eventually, after a Jenkins master restart, the JNLP process is receiving a 404 on requests to

slaveJnlpURL

with the remoting Launcher class retrying forever (haven't fond the cause for the slave removal).

This loop wont be exited, leading to resource extarvation.

A possible solution would be throwing a FileNotFoundException under a 404, at Launcher.java and adding a new exception handler at the same class (as that 404 will be not recoverable)