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 for Jira 7.1.6 which contacts 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);

 This has worked great until the Jira environment was updated to use Java version 1.8.0_131. This continues to work great in all our dev environments which are still using older java versions.

Now the plugin still receives the complete response from the web service, but Jersey returns a null object when we use the getEntity method as above. We've verified that Jersey isn't throwing any errors in the logs. The clientResponse object also shows that the status of the call is 200.

Does anyone know how to resolve this? Do you know if this version of Jira and the version of Jersey that's bundled in Jira is compatible with Java 1.8.0_131?

We have defined the dependencies for Jersey in our pom.xml like this:

<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>

 

0 answers

Suggest an answer

Log in or Sign up to answer