Status: Closed (View Workflow)
Open sourcing the JNLPProtocol4 implementation that combines NIO with TLS encryption to resolve the regression to Thread-per-client in JNLPProtocol3
- is related to
JENKINS-33886 Can only connect one JNLP3 slave per IP address
- relates to
JENKINS-40700 Display communication protocol in agent logs
- links to
How does one confirm that JNLP4 is being used? I tried the latest Jenkins ver. 2.38 (weekly) and configured a JNLP slave (there's no option to configure what kind of JNLP slave).
Additionally, the agent logs don't show much in the way of output confirming which JNLP protocol is even being used. Here's the full log output from the initialization of the JNLP slave.
JNLP agent connected from /REDACTED <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 3.3 This is a Unix agent Agent successfully connected and online
So far, I'm not sure how to tell what protocol is being used.
Nevermind, I found it in Manage Jenkins > Configure Global Security > JNLP. In the Advanced section, you have to enable JNLP4 (and can optionally disable the other protocols). Then if you look at the agent log you can see the JNLP4 class being used in the thread dump output. It would be nice if the agent Log output displayed which protocol it is using in the agent startup information.
It would be nice if the agent Log output displayed which protocol it is using in the agent startup information.
JENKINS-40700 as an enhancement.
Code changed in jenkins
User: Stephen Connolly
[JENKINS-36871, JENKINS-37565] JNLP4-connect implementation and Remoting 3 (#2492)
JENKINS-36871Switch to the new JnlpProtocolHandler based implementation
JENKINS-36871License headers and javadocs JENKINS-36871Restore cookie handling JENKINS-36871Integrating Agent discovery components JENKINS-36871Pick up remoting 3.0-SNAPSHOT JENKINS-36871Pick up newer snapshot JENKINS-36871Oleg wants to log an exception that cannot happen