Error using Jersey with Jira 7.1.6 and Java 1.8.0_131

John Bishop
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 19, 2017

We developed an add-on in Jira 7.1.6 which makes calls to an external web service and receives back an xml response. Then we use Jersey to deserialize the response like this:

GetServiceListResponse serviceListResponse = clientResponse.getEntity(GetServiceListResponse.class);

These are Jersey dependencies we have defined in the pom.xml:

<dependency>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-client</artifactId>
<version>1.8-atlassian-11</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-json</artifactId>
<version>1.8-atlassian-11</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-core</artifactId>
<version>1.8-atlassian-11</version>
<scope>provided</scope>
</dependency>

This worked fine until the Jira environment was upgraded to use the JDK version 1.8.0_131. I've verified that the add-on works fine in all environments which have a java version older than 1.8.0_131.

Now the add-on receives the response from the web service (I've been able to output the raw text), but when we try to run the code as above serviceListResponse is always null. I've verified that Jersey is not throwing any errors or warnings in the logs.

Does anyone know a solution to get Jersey working with this version of the jdk?

I know this version of the jdk has a lot of security updates. Does anyone know if this version of Jira or the Jersey framework that's bundled in it is compatible with this version of the JDK?

1 answer

1 accepted

0 votes
Answer accepted
John Bishop
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 20, 2017

Suggest an answer

Log in or Sign up to answer