Resolution
Inbound agent connections are initiated by the agent, so a controller does not manage them in general.
Thus the retention strategy that must be selected when configuring the agent is:
Keep this agent online as much as possible
Choosing any other strategy does not make sense, since if the selected retention strategy were:
Take this agent online when in demand, and offline when idle
the agent will then re-establish the connection. And if the retention strategy:
Take this agent online according to a schedule
is selected, the JNLP agent connection will be terminated by the Jenkins master according to the schedule, but the agent will then re-establish the connection.
In both invalid cases, and specially if the JNLP command is installed as a service, the logs will grow excessively.
This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.