-
Bug
-
Resolution: Fixed
-
Major
-
-
2.335,2.332.1
This week after the jenkins update of 2.317 and to 2.318 , my agent machine (windows 10) start getting terminated again and again after connected
As normally I use jnlp file right click to launch , the jenkins agent windows appears and I can see Connected but within few seconds its got Terminated
I went into the remoting folder to check out the logs and it prompts this error
Caused by: java.security.AccessControlException: access denied ("java.util.PropertyPermission" "hudson.util.RingBufferLogHandler.defaultSize" "read")
Agent Java version : OpenJDK 1.8.0 301
Jenkins version : Jenkins 2.318
I am using Openwebstart for jnlp
Complete log message (agent machine)
Okt 26, 2021 9:53:03 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFORMATION: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Okt 26, 2021 9:53:03 AM org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
INFORMATION: Waiting for ProtocolStack to start.
Okt 26, 2021 9:53:08 AM hudson.remoting.UserRequest perform
WARNUNG: LinkageError while performing UserRequest:hudson.slaves.SlaveComputer$SlaveInitializer@6cfcc55d
java.lang.ExceptionInInitializerError
at hudson.slaves.SlaveComputer$SlaveInitializer.call(SlaveComputer.java:1042)
at hudson.slaves.SlaveComputer$SlaveInitializer.call(SlaveComputer.java:1033)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:376)
at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:122)
at java.lang.Thread.run(Unknown Source)
Caused by: java.security.AccessControlException: access denied ("java.util.PropertyPermission" "hudson.util.RingBufferLogHandler.defaultSize" "read")
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
at java.lang.System.getProperty(Unknown Source)
at java.lang.Integer.getInteger(Unknown Source)
at java.lang.Integer.getInteger(Unknown Source)
at hudson.util.RingBufferLogHandler.<clinit>(RingBufferLogHandler.java:39)
... 11 more
- is duplicated by
-
JENKINS-67034 Unable to connect web start agents after updating to 2.318 from 2.311. "Terminated" after 1 second
-
- Closed
-
- relates to
-
JENKINS-67881 Jenkins agent connection terminates with agents that 'Launch agent by connecting it to the controller'
-
- Closed
-
-
JENKINS-67913 Remoting uses terminally deprecated System#setSecurityManager method
-
- Closed
-
-
JENKINS-57139 Linux agent installer does not work on Java 11
-
- Closed
-
- links to
[JENKINS-67000] JavaWebStart agents cannot connect due to AccessControlException
Labels | New: exception slave windows |
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
I can't duplicate the problem you're reporting. I have a Windows 10 agent connected by running a local batch script that runs the Java command with remoting.jar to connect to my Docker based controller running Jenkins 2.318. No loss of connection. No issues reported.
I'm running remoting 4.10 on my Windows agent. What version of remoting are you running?
I've now updated to use the 4.11 agent.jar with remoting.jar 4.11. No issues detected in any of the cases yet.
The version node monitor plugin will show the version of remoting used by each of your agents. It will also allow you to enforce that agent remoting must match the remoting version on your controller.