• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Debian 7 Wheezy x86-64, Oracle Java 8, Jenkins 1.586

      Using Java8, Jenkins doesn't start with the following message:

      SCHWERWIEGEND: Container startup failed
      java.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory
         at winstone.Launcher.spawnListener(Launcher.java:209)
         at winstone.Launcher.<init>(Launcher.java:149)
         at winstone.Launcher.main(Launcher.java:354)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
         at java.lang.reflect.Method.invoke(Method.java:483)
         at Main._main(Main.java:293)
         at Main.main(Main.java:98)
      Caused by: java.lang.NoClassDefFoundError: sun/security/x509/CertAndKeyGen
         at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:101)
         at winstone.Launcher.spawnListener(Launcher.java:207)
         ... 8 more
      Caused by: java.lang.ClassNotFoundException: sun.security.x509.CertAndKeyGen
         at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
         at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
         ... 10 more
      

      After switching back to Oracle Java 7, it works without problems.

          [JENKINS-25333] Jenkins 1.586 not starting up using Java8

          Jason Smith added a comment -

          I am using the RedHat Jemkins rpms, and have this config setting: JENKINS_HTTPS_PORT="8443", which adds this argument to the java command line in the initscript: --httpsPort=8443. But I think this is irrelevant, since the failure comes from the import:

          https://github.com/jenkinsci/winstone/blob/master/src/java/winstone/HttpsConnectorFactory.java#L18

          since the class path was moved. So even if I used my own keystore for the cert & key, importing sun.security.x509.CertAndKeyGen will still fail.

          Jason Smith added a comment - I am using the RedHat Jemkins rpms, and have this config setting: JENKINS_HTTPS_PORT="8443", which adds this argument to the java command line in the initscript: --httpsPort=8443. But I think this is irrelevant, since the failure comes from the import: https://github.com/jenkinsci/winstone/blob/master/src/java/winstone/HttpsConnectorFactory.java#L18 since the class path was moved. So even if I used my own keystore for the cert & key, importing sun.security.x509.CertAndKeyGen will still fail.

          Daniel Beck added a comment -

          smithj4 Yes, so you're relying on ad-hoc cert functionality. Just create a cert and reference that and you should be fine.

          Imports don't really matter here, otherwise the stack trace in the issue description wouldn't have called start() and reached line 101.

          Daniel Beck added a comment - smithj4 Yes, so you're relying on ad-hoc cert functionality. Just create a cert and reference that and you should be fine. Imports don't really matter here, otherwise the stack trace in the issue description wouldn't have called start() and reached line 101.

          danielbeck Maybe it's best to remove this functionality from Winstone. My PR was just to give us some time before removing it completely. The fix I provided won't work with JDK 9, so this might give us a few months(years?) to suggest to avoid using the built-in cert generation and use a valid one before everyone starts using JDK 9 heavily. I could also provide an error on startup suggesting everyone switch to using an outside certificate instead.

          Steven Christou added a comment - danielbeck Maybe it's best to remove this functionality from Winstone. My PR was just to give us some time before removing it completely. The fix I provided won't work with JDK 9, so this might give us a few months(years?) to suggest to avoid using the built-in cert generation and use a valid one before everyone starts using JDK 9 heavily. I could also provide an error on startup suggesting everyone switch to using an outside certificate instead.

          Daniel Beck added a comment -

          schristou Would be viable, provided it doesn't break things for anyone currently using it successfully. E.g. print a deprecation warning for them and otherwise work, and print a useful error message otherwise. Just removing the parameter and getting something like "This argument doesn't exist" has the potential to break users' instances.

          Daniel Beck added a comment - schristou Would be viable, provided it doesn't break things for anyone currently using it successfully. E.g. print a deprecation warning for them and otherwise work, and print a useful error message otherwise. Just removing the parameter and getting something like "This argument doesn't exist" has the potential to break users' instances.

          Brian Wilson added a comment -

          It would be very useful to get this feature of Jenkins working again. Our setup uses Active Directory user authentication and with Jenkins using http on the default port 8080, the paswords are potentially compromised if someone starts sniffing traffic on the server.

          I've been trying to get the -httpsport option working with no success and happened to stumble across this ticket which explained things. Now I'm trying to get a signed certificate to install, but I have to say SSL/TLS is not something I've had to deal with much so this is a little confusing (learning about CSR, CRT, JKS, KEY, etc.). If this could be better explained, or just plain fixed as documented, I'm sure a lot of people would be very grateful.

          Brian Wilson added a comment - It would be very useful to get this feature of Jenkins working again. Our setup uses Active Directory user authentication and with Jenkins using http on the default port 8080, the paswords are potentially compromised if someone starts sniffing traffic on the server. I've been trying to get the -httpsport option working with no success and happened to stumble across this ticket which explained things. Now I'm trying to get a signed certificate to install, but I have to say SSL/TLS is not something I've had to deal with much so this is a little confusing (learning about CSR, CRT, JKS, KEY, etc.). If this could be better explained, or just plain fixed as documented, I'm sure a lot of people would be very grateful.

          Daniel Beck added a comment -

          If this could be better explained

          The documentation (and usage instructions) says:

          --httpsPrivateKey this switch with --httpsCertificate can be used to run HTTPS with OpenSSL secret key file and the corresponding certificate file

          These files are the output of pretty much every OpenSSL "how to create a self-signed certificate" tutorial on the web.

          I don't think we need to write another one.

          Daniel Beck added a comment - If this could be better explained The documentation (and usage instructions) says: --httpsPrivateKey this switch with --httpsCertificate can be used to run HTTPS with OpenSSL secret key file and the corresponding certificate file These files are the output of pretty much every OpenSSL "how to create a self-signed certificate" tutorial on the web. I don't think we need to write another one.

          Jesse Glick added a comment -

          I think in the world of letsencrypt.org there is no reason to keep this functionality undeprecated.

          Jesse Glick added a comment - I think in the world of letsencrypt.org there is no reason to keep this functionality undeprecated.

          Code changed in jenkins
          User: Jesse Glick
          Path:
          .gitignore
          Jenkinsfile
          pom.xml
          src/java/winstone/HttpsConnectorFactory.java
          src/java/winstone/LocalStrings.properties
          http://jenkins-ci.org/commit/winstone/14b69f14db22af3b4f5b1078eb63290a98082eae
          Log:
          Merge pull request #29 from jglick/self-signed-JENKINS-25333

          JENKINS-25333 Avoid hard dependency on non-Java-Platform APIs

          Compare: https://github.com/jenkinsci/winstone/compare/79bc5acdc653...14b69f14db22

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: .gitignore Jenkinsfile pom.xml src/java/winstone/HttpsConnectorFactory.java src/java/winstone/LocalStrings.properties http://jenkins-ci.org/commit/winstone/14b69f14db22af3b4f5b1078eb63290a98082eae Log: Merge pull request #29 from jglick/self-signed- JENKINS-25333 JENKINS-25333 Avoid hard dependency on non-Java-Platform APIs Compare: https://github.com/jenkinsci/winstone/compare/79bc5acdc653...14b69f14db22

          Code changed in jenkins
          User: Jesse Glick
          Path:
          war/pom.xml
          http://jenkins-ci.org/commit/jenkins/4f814c0a9f8e72384046015975f201f4f693abaf
          Log:
          [FIXED JENKINS-25333] Update to Winstone 3.2. (#2673)

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/4f814c0a9f8e72384046015975f201f4f693abaf Log: [FIXED JENKINS-25333] Update to Winstone 3.2. (#2673)

          Oleg Nenashev added a comment -

          The issue fix has been integrated into Jenkins 2.38

          Oleg Nenashev added a comment - The issue fix has been integrated into Jenkins 2.38

            jglick Jesse Glick
            maxzilla Max Wahler
            Votes:
            11 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: