Post

5 followers Follow
0
Avatar

Cannot connect to Xebia Deploy server from Jenkins

My Jenkins server and Xebia server are on the same machine.

I can connect to my Xebia server from a different Jenkins server (so firewall ports are OK) and I assume my Xebia server is fine as well (no issue through the browser)

When I enter my configration in Jenkins/Manage jenkins/COnfigure System, I get the following error:

XL Deploy configuration is not valid! com.xebialabs.deployit.ci.DeployitPluginException: org.jboss.resteasy.spi.ReaderException: javax.ws.rs.ProcessingException: RESTEASY003145: Unable to find a MessageBodyReader of content-type application/xml;charset=UTF-8 and type interface java.util.List

What am I doing wrong? I assume I have something missing on my Jenkins server but I could not find any specific requirement tied to the Xebia plugin. I checked my plugins with the other instance that can access multiple Xebia servers.

Thanks

Laurent Rochette

Please sign in to leave a comment.

6 comments

1
Avatar

Hello Laurent,

This sounds like known issue - DEPL-12107.

From http://www.oracle.com/technetwork/java/javase/8u144-relnotes-3838694.html -

java.util.zip.ZipFile.getEntry() now always returns the ZipEntry instance with a / ended entry name for directory entry

The java.util.zip.ZipEntry API doc specifies "A directory entry is defined to be one whose name ends with a /". However, in previous JDK releases, java.util.zip.ZipFile.getEntry(String entryName) may return a ZipEntry instance with an entry name that does not end with / for an existing zip directory entry when

    the passed in argument entryName does not end with a /, and
    there is a matching zip directory entry with name entryName + / in the zip file.

With this release, the name of the ZipEntry instance returned from java.util.zip.ZipFile.getEntry() always ends with / for any zip directory entry.

To revert to the previous behavior, set the system property jdk.util.zip.ensureTrailingSlash to "false".

This change was made in order to fix a regression introduced in JDK 8u141 when verifying signed JARs that has caused some WebStart applications to fail to load.

You should be able to work around this by adding -Djdk.util.zip.ensureTrailingSlash=false to the Java startup commands of Jenkins.

Regards,
Adam

Adam Adrianson 1 vote
0
Avatar

Hello,

 

I am having the same issue. What is the location of this fix? Can you please let me know. 

 

 

 

Thanks 

Mohsien 0 votes
1
Avatar

Sidankar,

 

the fix is explained above, simply add -Djdk.util.zip.ensureTrailingSlash=false to your jenkins startup script. Nothing to download or install

Laurent Rochette 1 vote