Hi Giovanni, We already saw that issue in earlier versions [1] but it turned to be an issue with the domain classes having more than one constructor. Looking at your stacktrace I can see the issue is raised here [2], when jclouds tries to deserialize the list of regions and determine which json field maps to each Java object field by checking the SerializedNames annotation [3].
I can't figure out why that is happening and is not reproducible, so it would be very helpful if you can provide: * The exact Maven and Java version that is being used to run the build. * The output of the "mvn dependency:tree" executed in the machine where you run the builds. Just to have the exact pictures of which dependencies and versions are being used in the build that fails. * The jclouds.wire logs [4] corresponding to the response returned in that call that fails I. [1] https://issues.apache.org/jira/browse/JCLOUDS-857 [2] https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/json/internal/NamingStrategies.java#L183 [3] https://github.com/jclouds/jclouds-labs/blob/jclouds-labs-1.9.1/digitalocean2/src/main/java/org/jclouds/digitalocean2/domain/Region.java#L33 [4] http://jclouds.apache.org/reference/logging/ On 23 October 2015 at 11:06, Giovanni Toraldo <[email protected]> wrote: > Hi, > > we are repeatedly getting a JsonSyntaxException during nightly builds, > but we are not able to reproduce this one locally, everything works > fine. > > https://gist.github.com/gionn/e2eb0bae94369ec8ca7c > > Suggestions? > > -- > Giovanni Toraldo > Lead Developer > https://cloudesire.com
