The only explanation I can think of is that in this line ex.getCause()
returns null, meaning that ex is the important part and not ex.getCause().
} catch (final ProcessingException ex) {
throw new ResponseProcessingException(new
InboundJaxrsResponse(response, scope), ex.getCause());
On Fri, Feb 19, 2016 at 4:01 PM, Robert DiFalco <robert.difalco_at_gmail.com>
wrote:
> Here's the complete stack trace. I'm just not sure how it could not be
> showing a cause.
>
> javax.ws.rs.client.ResponseProcessingException
> at
> org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:869)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.client.JerseyInvocation.access$800(JerseyInvocation.java:92)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.client.JerseyInvocation$3.call(JerseyInvocation.java:722)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:718)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:430)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:321)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.tags.client.TagsClient.organizationMappings(TagsClient.java:58)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.collector.TagsManager.getMappings(TagsManager.java:62)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.collector.TagsManager.lambda$createContext$7(TagsManager.java:56)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at com.XXXX.pipeline.collector.TagsManager.measure(TagsManager.java:132)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.collector.TagsManager.createContext(TagsManager.java:50)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.billing.processing.aws.AwsBillProcessor.parseXyz(AwsBillProcessor.java:109)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.billing.processing.aws.AwsBillProcessor.process(AwsBillProcessor.java:92)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.billing.processing.aws.AwsBillProcessor.accept(AwsBillProcessor.java:74)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.billing.processing.aws.AwsBillProcessor.accept(AwsBillProcessor.java:31)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.common.sqs.SQSLeasedMessageConsumerService.process(SQSLeasedMessageConsumerService.java:234)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> com.XXXX.pipeline.common.sqs.SQSLeasedMessageConsumerService.lambda$process$35(SQSLeasedMessageConsumerService.java:190)
> ~[foo-bar-1.32-SNAPSHOT.jar:1.32-SNAPSHOT]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_66]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_66]
>
> On Fri, Feb 19, 2016 at 3:57 PM, Robert DiFalco <robert.difalco_at_gmail.com>
> wrote:
>
>> 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]
>>>
>>>
>>>
>>
>