Odd, it certainly seems like it from my logging. I have yet to reproduce it
in a debugger. But we just do a simple log.error("Unexpected error.", e) on
that exception. For all other exceptions this will typically also print out
the cause.
On Fri, Feb 19, 2016 at 3:49 PM, Pavel Bucek <pavel.bucek_at_oracle.com> wrote:
> Hi Robert,
>
> are you sure there is no "cause" set for this exception?
>
> Regards,
> Pavel
>
>
> On 20/02/16 00:36, Robert DiFalco wrote:
>
> I'm getting this exception with no message and no caused by. This is just
> calling a GET method. Simple app using latest Jersey Client and Jackson.
> The stack trace is here:
>
> javax.ws.rs.client.ResponseProcessingException
> at
> org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:869)
> ~[XXXX-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.client.JerseyInvocation.access$800(JerseyInvocation.java:92)
> ~[XXXX-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.client.JerseyInvocation$3.call(JerseyInvocation.java:722)
> ~[XXXX-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> ~[XXXX-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> ~[XXXX-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
> ~[XXXX-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444)
> ~[XXXX-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:718)
> ~[XXXX-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
>
>
>