[Bug 1237226] New: Caused by: java.lang.ClassNotFoundException: hudson.remoting.Callable
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
Bug ID: 1237226 Summary: Caused by: java.lang.ClassNotFoundException: hudson.remoting.Callable Product: Fedora Version: 22 Component: jenkins Assignee: msrb@redhat.com Reporter: jamespatterson@operamail.com QA Contact: extras-qa@fedoraproject.org CC: java-sig-commits@lists.fedoraproject.org, mizdebsk@redhat.com, msrb@redhat.com
Description of problem: jenkins seems broken out of the box with a missing class error.
$ cd /usr/share/jenkins/webroot/WEB-INF/lib
$ java -jar jenkins-core-1.609.jar Exception in thread "main" java.lang.NoClassDefFoundError: hudson/remoting/Callable at hudson.Main.getHudsonHome(Main.java:77) at hudson.Main.run(Main.java:63) at hudson.Main.main(Main.java:55) Caused by: java.lang.ClassNotFoundException: hudson.remoting.Callable at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 3 more
That missing class is provided by remoting.jar in the same directory.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce: 1. 2. 3.
Actual results:
Expected results:
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
Mikolaj Izdebski mizdebsk@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed| |2015-06-30 10:56:43
--- Comment #1 from Mikolaj Izdebski mizdebsk@redhat.com --- (In reply to James Patterson from comment #0)
$ java -jar jenkins-core-1.609.jar
Running Jenkins this way is not supported in Fedora.
The recommended way to run Jenkins is using systemd: systemctl start jenkins systemctl stop jenkins
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
James Patterson jamespatterson@operamail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |NEW Resolution|NOTABUG |--- Keywords| |Reopened
--- Comment #2 from James Patterson jamespatterson@operamail.com --- The above is not my problem, it's the reproducer for the actual bug: monitoring external jobs is not possible.
Docs: https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs See "Monitoring an execution"
Seems it's broken on Fedora.
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
--- Comment #3 from Mikolaj Izdebski mizdebsk@redhat.com --- Then please describe the actual problem you are having.
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
--- Comment #4 from James Patterson jamespatterson@operamail.com --- Using any combination of the jenkins-core*jar files, I always get the traceback from comment 1 while running the command for monitoring an execution from the jenkins wiki, i.e.
$ sudo updatedb $ locate jenkins-core|grep jar$
For each of those results, I run:
$ export JENKINS_HOME=http://user:pw@myserver.acme.org/path/to/jenkins/ $ java -jar foundpathandfile.jar "job name" <program arg1 arg2...>
then the traceback from comment 1.
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
--- Comment #5 from James Patterson jamespatterson@operamail.com --- s/combination//;
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
--- Comment #6 from Mikolaj Izdebski mizdebsk@redhat.com --- Running Jenkins JAR directly is not supported in Fedora, but I think we can add a script for this purpose. Michal, do you agree?
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
--- Comment #7 from Michal Srb msrb@redhat.com --- Hi James,
thanks for the bug report. The problem is caused by missing Class-Path entry in MANIFEST.MF of our jenkins-core.jar. Having Class-Path in MANIFEST.MF is banned by packaging guidelines in Fedora. It's a bit unfortunate, but as Mikolaj suggested, we can add script for this purpose.
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
--- Comment #8 from James Patterson jamespatterson@operamail.com --- That sounds great. Would it be possible to get a copy of this script to test?
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
--- Comment #9 from Michal Srb msrb@redhat.com --- I will prepare it later today/tomorrow and push it as an update for Fedora 22. It will be available for testing via fedora-updates-testing repository, or directly downloadable from http://koji.fedoraproject.org/koji/.
https://bugzilla.redhat.com/show_bug.cgi?id=1237226
Fedora End Of Life jkurik@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed|2015-06-30 10:56:43 |2016-07-19 11:07:57
--- Comment #10 from Fedora End Of Life jkurik@fedoraproject.org --- Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
java-sig-commits@lists.fedoraproject.org
-
Red Hat Bugzilla