Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Duplicate
-
Component/s: core
-
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
Issue Links
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
-
JENKINS-21047 Update XStream 1.4.4. to 1.4.6
-
- Resolved
-
Activity
Pascal
created issue -
Pascal
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | file-1.txt [ 25519 ] | |
| Description |
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 :) |
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 :) |
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).
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). 
K P
made changes -
| Link |
This issue is related to |
K P
made changes -
| Link |
This issue is related to |
K P
made changes -
| Link |
This issue is related to |
K P
made changes -
| Link |
This issue is related to |
K P
made changes -
| Link |
This issue is related to |
I suppose this is now resolved by JENKINS-18537 ?
K P
added a comment - I suppose this is now resolved by JENKINS-18537 ? Duplicates JENKINS-18537, fixed in 1.557 and 1.554.1
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 154160 ] | JNJira + In-Review [ 194810 ] |
I've added a pull request for https://issues.jenkins-ci.org/browse/JENKINS-21047 which may be related