Status: Resolved (View Workflow)
Jenkins 2.121.2, enviniject 2.1.6
I'm seeing the following warning in the logs:
WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 in file:/var/lib/jenkins/plugins/envinject/WEB-INF/lib/envinject.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
JENKINS-50457 Attempt to (de-)serialize anonymous class
Ubuntu 16.04 (both master ans slaves)
Jenkins vers: 2.138.4
EnvInject API 1.5
All I did was disconnect the slave and reconnect again.
The warning would always show up right before the line "Agent successfully connected and online".
I am experiencing the same issue with a recent upgrade using the following environment listed below.
Warning message on agent:
..... Jan 14, 2019 11:36:15 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Jan 14, 2019 11:36:21 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
Jenkins vers: 2.150
EnvInject API 1.5
Agent: Windows 10 Build 1803 (fully patched)
Master: CentOS 6.10
Java: 1.8.0_191 (Master and Agents)
One piece of troubleshooting was replacing the agent.jar file with the previous slave.jar file and bringing the agent online successfully without the warning message.
How did you replace the agent.jar with the previous slave.jar? (I'm here because I got that message, AND because my slave execution takes 20GIG of ram!:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4539 engineer 20 0 20.738g 224564 14776 S 0.3 0.3 0:49.35 java
and am trying to see if I can do anything to make it better)
Also, what do I need to do to GET the 'fixed' version, since supposedly it is fixed (assuming that's why it was resolved! I am using
We also still face the same problem in with Jenkins version 2.150.1 during connect with the agent.jar.