• Type: Bug
• Resolution: Duplicate
• Priority: Blocker
• Component/s: core
• Labels:

  • ArrayIndexOutOfBoundsException
  • XStream

1. file-1.txt

   21 kB

   2014-03-07 10:11

2. file-1.txt

   21 kB

   2014-03-07 10:16

[JENKINS-22081] XStream deserialization errors at service startup

Pascal created issue - 2014-03-07 10:11

Pascal made changes - 2014-03-07 10:16

Attachment		New: file-1.txt [ 25519 ]
Description	Original: Hello, I could found other related 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 :)	New: 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 :)

Collapse comment: martin brook added a comment - 2014-03-08 18:19

martin brook added a comment - 2014-03-08 18:19

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

Expand comment: martin brook added a comment - 2014-03-08 18:19

martin brook added a comment - 2014-03-08 18:19 I've added a pull request for https://issues.jenkins-ci.org/browse/JENKINS-21047 which may be related

Collapse comment: Pascal added a comment - 2014-03-10 08:03, Edited by Pascal - 2014-03-10 08:05

Pascal added a comment - 2014-03-10 08:03 - 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).

Expand comment: Pascal added a comment - 2014-03-10 08:03, Edited by Pascal - 2014-03-10 08:05

Pascal added a comment - 2014-03-10 08:03 - 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).

K P made changes - 2014-03-21 16:19

Link

New: This issue is related to JENKINS-22270 [ JENKINS-22270 ]

K P made changes - 2014-03-21 16:20

Link

New: This issue is related to JENKINS-22270 [ JENKINS-22270 ]

K P made changes - 2014-03-21 16:20

Link

Original: This issue is related to JENKINS-22270 [ JENKINS-22270 ]

K P made changes - 2014-03-21 16:26

Link

New: This issue is related to JENKINS-21047 [ JENKINS-21047 ]

K P made changes - 2014-03-26 10:08

Link

New: This issue is related to JENKINS-18537 [ JENKINS-18537 ]

Collapse comment: K P added a comment - 2014-04-08 15:06

K P added a comment - 2014-04-08 15:06

I suppose this is now resolved by JENKINS-18537 ?

Expand comment: K P added a comment - 2014-04-08 15:06

K P added a comment - 2014-04-08 15:06 I suppose this is now resolved by JENKINS-18537 ?

Load more newer events