[JIRA] [cli] (JENKINS-24385) Jenkins CLI hangs with InvocationTargetException

2 views
Skip to first unread message

saar.netzer@gmail.com (JIRA)

unread,
Aug 3, 2015, 5:05:01 AM8/3/15
to jenkinsc...@googlegroups.com
Saar Netzer reopened an issue
 

This issue is happening now again.
When running jenkins_cli command it hangs.
Every couple of days the identity file is getting corrupted.
Moving it and restarting Jenkins resolving the problem as a new identity file is created.
This happen when Jenkins is running and not on shutdown/restart of the platform.
Jenkins Version 1.565.3

Jenkins / Bug JENKINS-24385
Jenkins CLI hangs with InvocationTargetException
Change By: Saar Netzer
Resolution: Cannot Reproduce
Status: Resolved Reopened
Assignee: Saar Netzer
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

saar.netzer@gmail.com (JIRA)

unread,
Aug 3, 2015, 5:07:03 AM8/3/15
to jenkinsc...@googlegroups.com
This issue is happening now again.
When running jenkins_cli command it hangs.
Every couple of days the identity file is getting corrupted.
Moving it and restarting Jenkins resolving the problem as a new identity file is created.
This happen when Jenkins is running and not on shutdown/restart of the platform.
Jenkins Version 1.565.3

Java build 1.7.0_75-b13

dbeck@cloudbees.com (JIRA)

unread,
Aug 3, 2015, 5:49:02 AM8/3/15
to jenkinsc...@googlegroups.com
Daniel Beck resolved as Cannot Reproduce
 

1.565.x has been out of community support for over a year. For this issue to be relevant, needs to happen with a recent release (1.609.x preferably, 1.596.x if absolutely necessary).

If the identify file gets corrupted while Jenkins is running, consider making it readonly for the user Jenkins is running as to see what fails to work because of that.

Change By: Daniel Beck
Status: Reopened Resolved
Resolution: Cannot Reproduce

VictorMartinezRubio@gmail.com (JIRA)

unread,
Oct 13, 2016, 8:31:05 AM10/13/16
to jenkinsc...@googlegroups.com
Victor Martinez commented on Bug JENKINS-24385
 
Re: Jenkins CLI hangs with InvocationTargetException

Hi there,

Unfortunately I've just seen this issue with the previous LTS release:

  • jenkins version: 2.7.4
  • Java: 1.7.0_111
command
$ telnet 127.0.0.1 8080
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
^Connection closed by foreign host.

$ java -jar /usr/share/jenkins/jenkins-cli.jar -s http://127.0.0.1:8080 help
jenkins.log
Oct 13, 2016 2:25:08 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
INFO: Accepted connection #4 from /127.0.0.1:46816
Oct 13, 2016 2:25:08 PM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException
SEVERE: A thread (TCP agent connection handler #4 with /127.0.0.1:46816/1601) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.
java.lang.Error: java.lang.reflect.InvocationTargetException
	at hudson.cli.CliProtocol2$Handler2.run(CliProtocol2.java:74)
	at hudson.cli.CliProtocol2.handle(CliProtocol2.java:33)
	at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:182)
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at hudson.cli.CliProtocol2$Handler2.run(CliProtocol2.java:65)
	... 2 more
Caused by: java.lang.NullPointerException
	at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.get(InstanceIdentity.java:152)
	... 7 more

I'll double check whether with the latest release 2.19.X works fine

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

VictorMartinezRubio@gmail.com (JIRA)

unread,
Oct 13, 2016, 9:36:04 AM10/13/16
to jenkinsc...@googlegroups.com

It works after upgrading to the latest version: 2.19.1 and the below plugins:

  • credentials = '2.1.0'
  • ssh_credentials = '1.12'
  • build_pipeline_plugin = '1.4.4'
  • findbugs = '4.62'
  • jquery = '1.11.2-0'
  • token_macro = '1.12.1'

Cheers

brennx0r@gmail.com (JIRA)

unread,
Nov 11, 2016, 4:16:02 PM11/11/16
to jenkinsc...@googlegroups.com

I experienced this issue. My setup:

Jenkins 2.7.4 - 2.11.11
Docker - CentOS 6.8
JDK 1.8.111
No security setup (this is a test instance - chef + kitchen)

The cause of the behavior in my case was that the identity file in the Jenkins root could not be loaded. To correct the issue, I simply removed the file and restarted the Jenkins service.

Reply all
Reply to author
Forward
0 new messages