Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22081

XStream deserialization errors at service startup

    Details

    • Similar Issues:

      Description

      Hello, I could found other XStream issues, but I don't know if any is related. This XML API is tricky, the least to say being respectful

      What I tried, getting the exact same log afterwhile:

      • doing a fresh jenkins install after purging jenkins, jenkins-common and jenkins-cli Ubuntu packages
      • setting a different JAVA_HOME and '/var/lib/jenkins/config.xml: hudson -> jdks -> jdk -> home' accordingly (tried Open JDK 7, Oracle 7 and Oracle 8,)

      Attached is the error context and data, through shell commands.

      Thanks in advance

        Attachments

        1. file-1.txt
          21 kB
        2. file-1.txt
          21 kB

          Issue Links

            Activity

            Hide
            vgrade martin brook added a comment -

            I've added a pull request for https://issues.jenkins-ci.org/browse/JENKINS-21047 which may be related

            Show
            vgrade martin brook added a comment - I've added a pull request for https://issues.jenkins-ci.org/browse/JENKINS-21047 which may be related
            Hide
            pascalav Pascal added a comment - - edited

            Issue is solved, and narrows down to usage of Java 8 (as Jenkins starting 'JAVA' environment variable).

            By downgrading it to Java 7, Xstream deserialization starting errors disappeared, and I recovered access to the web app.

            So indeed, it might just be version upgrade related.

            Note that the JVM set in the Jenkins config.xml, the one running tests, is not affected by this, and Java 8 runs flawlessly when set there (I initially thought both Java settings were linked).

            Show
            pascalav Pascal added a comment - - edited Issue is solved, and narrows down to usage of Java 8 (as Jenkins starting 'JAVA' environment variable). By downgrading it to Java 7, Xstream deserialization starting errors disappeared, and I recovered access to the web app. So indeed, it might just be version upgrade related. Note that the JVM set in the Jenkins config.xml, the one running tests, is not affected by this, and Java 8 runs flawlessly when set there (I initially thought both Java settings were linked).
            Hide
            belpk K P added a comment -

            I suppose this is now resolved by JENKINS-18537 ?

            Show
            belpk K P added a comment - I suppose this is now resolved by JENKINS-18537 ?
            Hide
            danielbeck Daniel Beck added a comment -

            Duplicates JENKINS-18537, fixed in 1.557 and 1.554.1

            Show
            danielbeck Daniel Beck added a comment - Duplicates JENKINS-18537 , fixed in 1.557 and 1.554.1

              People

              • Assignee:
                Unassigned
                Reporter:
                pascalav Pascal
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: