RE: Camel supported servicemix version
Hi, Sorry for mis communication. We are using the camel version that is coming as part of service mix vesion 3.4.0 i.e CXF 2.4.4 and Camel 2.8.3. Does it mean that CXF 2.4.4 and Camel 2.8.3 does not support developing REST services ? Regards, Deepthi -Original Message- From: Claus Ibsen Sent: Monday, August 27, 2018 11:43 AM To: users@camel.apache.org Subject: Re: Camel supported servicemix version Hi Can you double check the servicemix version you are using, as 3.x is very very old. In general ServiceMix only support the Camel version that it ships out of the box. On Mon, Aug 27, 2018 at 7:55 AM Ls, Deepthi (Nokia - IN/Bangalore) wrote: > > Hello Team, > > We have a rest service developed using CXF framework and camel version 2.16.4 > deployed in servicemix. > servicemix version used is 3.4.0. But it is not working. > When we try the same with servicemix version 7, it is working. > Is it not supported in servicemix version 3.4.0? > > Please help. > > Thanks and Regards, > Deepthi > -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel supported servicemix version
Hi Can you double check the servicemix version you are using, as 3.x is very very old. In general ServiceMix only support the Camel version that it ships out of the box. On Mon, Aug 27, 2018 at 7:55 AM Ls, Deepthi (Nokia - IN/Bangalore) wrote: > > Hello Team, > > We have a rest service developed using CXF framework and camel version 2.16.4 > deployed in servicemix. > servicemix version used is 3.4.0. But it is not working. > When we try the same with servicemix version 7, it is working. > Is it not supported in servicemix version 3.4.0? > > Please help. > > Thanks and Regards, > Deepthi > -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Manually test smb endpoint connection on linux
What can i use on redhat linux to test if an smb location will be accessible
with camel-jcifs? I tries using 'smbclient' but i get 'LOGON_FAILURE' in for
locations that camel *can* actually write to. Is there anything else i can use?
Background:
I have a small Apache Camel application that picks up files at a smb endpoint:
smb://domain.nl;user-n...@domain.nl/my/file/location?password=Blablabla=${processedFolder}=true=true
Recently we had a glitch and the process failed after moving some of the files
we had lined up. Logs made it clear the files from the smb location suddenly
became inaccesible.
The first thing i tried was checking if i could get to the smb endpoint, like
this:
> smbclient -L domain.nl -U user-name -d 10
This returned session setup failed: NT_STATUS_LOGON_FAILURE after many debug
lines.
Long story short, it turned out it was just a glitch, after rerunning camel all
the files were picked up. So smbclient is not the way to check if apache camel
using Samba JCIFS can access a location. But what is? Next time, how can i
check manually from the linux server if a smb location is available?
I should note that the linux-version is ancient, 5.5 redhat.
camel version: 2.20.1, camel jcifs version: 2.18.0, jcifs version: 1.3.18
Thanks in advance, we have no in-house sys-admins anymore to help with this
kind of deployment questions.
Ivana Cace
* De informatie verzonden in deze
e-mail (inclusief bijlagen) kan vertrouwelijk van aard zijn en is uitsluitend
bestemd voor de geadresseerde(n). Indien deze e-mail niet voor u bestemd is,
verzoeken wij u vriendelijk het bericht te retourneren en vervolgens te
vernietigen. Yarden doet er alles aan om ervoor te zorgen dat verzonden
e-mailberichten vrij zijn van virussen, maar kan dit niet garanderen. Yarden
Holding B.V., statutair gevestigd te Almere, Handelsregisternummer 34155452
Yarden Uitvaartfaciliteiten B.V., statutair gevestigd te Almere,
Handelsregisternummer 30104432 Yarden Uitvaartzorg B.V., statutair gevestigd te
Almere, Handelsregisternummer 04050164 Yarden Uitvaartverzekeringen N.V.,
statutair gevestigd te Almere, Handelsregisternummer 33244450
*
SOAP request causing null namespace URI in SimpleNsStreamWriter camel-cxf/woodstox
Getting NullPointer at
com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:134),
Because parameter nsURI is null.
(full stack trace below)
First call of this method prefix="soapenv", nsURI=null
Second call: prefix="soap", nsURI=="http://schemas.xmlsoap.org/soap/envelope/;
(I changed the value of nsURI in the debugger in the first call to arrive here)
Same SOAP request was working with the same application using an older version
of camel-cxf under Java 1.7
woodstox-core-5.0.3
camel-cxf 2.22.0
Any ideas ?
Regards
Jürgen
===
http://schemas.xmlsoap.org/soap/envelope/;
xmlns:tss="http://axpo.ch/emis/v1/TimeseriesService;>
MySourceSystem
IN1806141130169762894
NA
1234
MW
PT15M
com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:134
10:27:09,294 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default
task-118) Application
{http://axpo.ch/emis/v1/TimeseriesService}TimeseriesService#{http://axpo.ch/emis/v1/TimeseriesService}send
has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Error
during type conversion from type:
org.apache.camel.converter.jaxp.XMLStreamReaderInputStream to the required
type: javax.xml.stream.XMLStreamReader with value
org.apache.camel.converter.jaxp.XMLStreamReaderInputStream@9c55922 due
java.lang.NullPointerException
at
org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.checkFailure(CxfConsumer.java:344)
[camel-cxf-2.22.0.jar:2.22.0]
at
org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.setResponseBack(CxfConsumer.java:318)
[camel-cxf-2.22.0.jar:2.22.0]
at
org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.syncInvoke(CxfConsumer.java:244)
[camel-cxf-2.22.0.jar:2.22.0]
at
org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:162)
[camel-cxf-2.22.0.jar:2.22.0]
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
[cxf-core-3.2.5.jar:3.2.5]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[rt.jar:1.8.0_144]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[rt.jar:1.8.0_144]
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
[cxf-core-3.2.5.jar:3.2.5]
at
org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
[cxf-core-3.2.5.jar:3.2.5]
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
[cxf-core-3.2.5.jar:3.2.5]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
[cxf-core-3.2.5.jar:3.2.5]
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
[cxf-core-3.2.5.jar:3.2.5]
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
[cxf-rt-transports-http-3.2.5.jar:3.2.5]
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
[cxf-rt-transports-http-3.2.5.jar:3.2.5]
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
[cxf-rt-transports-http-3.2.5.jar:3.2.5]
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
[cxf-rt-transports-http-3.2.5.jar:3.2.5]
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216)
[cxf-rt-transports-http-3.2.5.jar:3.2.5]
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301)
[cxf-rt-transports-http-3.2.5.jar:3.2.5]
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220)
[cxf-rt-transports-http-3.2.5.jar:3.2.5]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
[jboss-servlet-api_3.1_spec-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276)
[cxf-rt-transports-http-3.2.5.jar:3.2.5]
at
io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
[undertow-servlet-1.4.18.SP8-redhat-1.jar:1.4.18.SP8-redhat-1]
at
io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
[undertow-servlet-1.4.18.SP8-redhat-1.jar:1.4.18.SP8-redhat-1]
at
Re: Manually test smb endpoint connection on linux
You need to ask to camel-extras guys.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Monday, August 27, 2018, 12:16:32 PM GMT+2, Ivana Cace
wrote:
What can i use on redhat linux to test if an smb location will be accessible
with camel-jcifs? I tries using 'smbclient' but i get 'LOGON_FAILURE' in for
locations that camel *can* actually write to. Is there anything else i can use?
Background:
I have a small Apache Camel application that picks up files at a smb endpoint:
smb://domain.nl;user-n...@domain.nl/my/file/location?password=Blablabla=${processedFolder}=true=true
Recently we had a glitch and the process failed after moving some of the files
we had lined up. Logs made it clear the files from the smb location suddenly
became inaccesible.
The first thing i tried was checking if i could get to the smb endpoint, like
this:
> smbclient -L domain.nl -U user-name -d 10
This returned session setup failed: NT_STATUS_LOGON_FAILURE after many debug
lines.
Long story short, it turned out it was just a glitch, after rerunning camel all
the files were picked up. So smbclient is not the way to check if apache camel
using Samba JCIFS can access a location. But what is? Next time, how can i
check manually from the linux server if a smb location is available?
I should note that the linux-version is ancient, 5.5 redhat.
camel version: 2.20.1, camel jcifs version: 2.18.0, jcifs version: 1.3.18
Thanks in advance, we have no in-house sys-admins anymore to help with this
kind of deployment questions.
Ivana Cace
* De informatie verzonden in deze
e-mail (inclusief bijlagen) kan vertrouwelijk van aard zijn en is uitsluitend
bestemd voor de geadresseerde(n). Indien deze e-mail niet voor u bestemd is,
verzoeken wij u vriendelijk het bericht te retourneren en vervolgens te
vernietigen. Yarden doet er alles aan om ervoor te zorgen dat verzonden
e-mailberichten vrij zijn van virussen, maar kan dit niet garanderen. Yarden
Holding B.V., statutair gevestigd te Almere, Handelsregisternummer 34155452
Yarden Uitvaartfaciliteiten B.V., statutair gevestigd te Almere,
Handelsregisternummer 30104432 Yarden Uitvaartzorg B.V., statutair gevestigd te
Almere, Handelsregisternummer 04050164 Yarden Uitvaartverzekeringen N.V.,
statutair gevestigd te Almere, Handelsregisternummer 33244450
*
RE: Manually test smb endpoint connection on linux
Thanks, will do!
-Oorspronkelijk bericht-
Van: Andrea Cosentino [mailto:ancosen1...@yahoo.com.INVALID]
Verzonden: maandag 27 augustus 2018 12:17
Aan: users@camel.apache.org
Onderwerp: Re: Manually test smb endpoint connection on linux
You need to ask to camel-extras guys.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Monday, August 27, 2018, 12:16:32 PM GMT+2, Ivana Cace
wrote:
What can i use on redhat linux to test if an smb location will be accessible
with camel-jcifs? I tries using 'smbclient' but i get 'LOGON_FAILURE' in for
locations that camel *can* actually write to. Is there anything else i can use?
Background:
I have a small Apache Camel application that picks up files at a smb endpoint:
smb://domain.nl;user-n...@domain.nl/my/file/location?password=Blablabla=${processedFolder}=true=true
Recently we had a glitch and the process failed after moving some of the files
we had lined up. Logs made it clear the files from the smb location suddenly
became inaccesible.
The first thing i tried was checking if i could get to the smb endpoint, like
this:
> smbclient -L domain.nl -U user-name -d 10
This returned session setup failed: NT_STATUS_LOGON_FAILURE after many debug
lines.
Long story short, it turned out it was just a glitch, after rerunning camel all
the files were picked up. So smbclient is not the way to check if apache camel
using Samba JCIFS can access a location. But what is? Next time, how can i
check manually from the linux server if a smb location is available?
I should note that the linux-version is ancient, 5.5 redhat.
camel version: 2.20.1, camel jcifs version: 2.18.0, jcifs version: 1.3.18
Thanks in advance, we have no in-house sys-admins anymore to help with this
kind of deployment questions.
Ivana Cace
* De informatie verzonden in deze
e-mail (inclusief bijlagen) kan vertrouwelijk van aard zijn en is uitsluitend
bestemd voor de geadresseerde(n). Indien deze e-mail niet voor u bestemd is,
verzoeken wij u vriendelijk het bericht te retourneren en vervolgens te
vernietigen. Yarden doet er alles aan om ervoor te zorgen dat verzonden
e-mailberichten vrij zijn van virussen, maar kan dit niet garanderen. Yarden
Holding B.V., statutair gevestigd te Almere, Handelsregisternummer 34155452
Yarden Uitvaartfaciliteiten B.V., statutair gevestigd te Almere,
Handelsregisternummer 30104432 Yarden Uitvaartzorg B.V., statutair gevestigd te
Almere, Handelsregisternummer 04050164 Yarden Uitvaartverzekeringen N.V.,
statutair gevestigd te Almere, Handelsregisternummer 33244450
*
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
* De informatie verzonden in deze
e-mail (inclusief bijlagen) kan vertrouwelijk van aard zijn en is uitsluitend
bestemd voor de geadresseerde(n). Indien deze e-mail niet voor u bestemd is,
verzoeken wij u vriendelijk het bericht te retourneren en vervolgens te
vernietigen. Yarden doet er alles aan om ervoor te zorgen dat verzonden
e-mailberichten vrij zijn van virussen, maar kan dit niet garanderen. Yarden
Holding B.V., statutair gevestigd te Almere, Handelsregisternummer 34155452
Yarden Uitvaartfaciliteiten B.V., statutair gevestigd te Almere,
Handelsregisternummer 30104432 Yarden Uitvaartzorg B.V., statutair gevestigd te
Almere, Handelsregisternummer 04050164 Yarden Uitvaartverzekeringen N.V.,
statutair gevestigd te Almere, Handelsregisternummer 33244450
*
Re: SOAP request causing null namespace URI in SimpleNsStreamWriter camel-cxf/woodstox
Hi
What older version of Camel and camel-cxf were you using that worked?
You are also welcome to log a JIRA about this NPE.
>From the debugger if you change that nsUrl from null, to that SOAP
namespace, does it work then?
And what if you change the nsUrl to be an empty string?
On Mon, Aug 27, 2018 at 11:44 AM Fritz, Jürgen wrote:
>
> Getting NullPointer at
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:134),
> Because parameter nsURI is null.
> (full stack trace below)
>
> First call of this method prefix="soapenv", nsURI=null
> Second call: prefix="soap",
> nsURI=="http://schemas.xmlsoap.org/soap/envelope/; (I changed the value of
> nsURI in the debugger in the first call to arrive here)
>
> Same SOAP request was working with the same application using an older
> version of camel-cxf under Java 1.7
>
> woodstox-core-5.0.3
> camel-cxf 2.22.0
>
> Any ideas ?
>
> Regards
> Jürgen
>
> ===
>
> http://schemas.xmlsoap.org/soap/envelope/;
> xmlns:tss="http://axpo.ch/emis/v1/TimeseriesService;>
>
> MySourceSystem
>
>
>
> IN1806141130169762894
> NA
>
>
> 1234
> MW
> PT15M
>
> quantity="0.041" status="VALID"/>
> quantity="0.036" status="VALID"/>
>
>
>
>
>
>
>
>
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:134
>
> 10:27:09,294 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default
> task-118) Application
> {http://axpo.ch/emis/v1/TimeseriesService}TimeseriesService#{http://axpo.ch/emis/v1/TimeseriesService}send
> has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Error
> during type conversion from type:
> org.apache.camel.converter.jaxp.XMLStreamReaderInputStream to the required
> type: javax.xml.stream.XMLStreamReader with value
> org.apache.camel.converter.jaxp.XMLStreamReaderInputStream@9c55922 due
> java.lang.NullPointerException
>at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.checkFailure(CxfConsumer.java:344)
> [camel-cxf-2.22.0.jar:2.22.0]
>at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.setResponseBack(CxfConsumer.java:318)
> [camel-cxf-2.22.0.jar:2.22.0]
>at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.syncInvoke(CxfConsumer.java:244)
> [camel-cxf-2.22.0.jar:2.22.0]
>at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:162)
> [camel-cxf-2.22.0.jar:2.22.0]
>at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_144]
>at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [rt.jar:1.8.0_144]
>at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>
RE: SOAP request causing null namespace URI in SimpleNsStreamWriter camel-cxf/woodstox
Hi Claus,
2.12.4 was the Camel version that worked with this request.
Changing the nsUrl to the correct value or to an empy string in the debugger
makes it working under Camel 2.22.0.
Kind regards
Jürgen
-Original Message-
From: Claus Ibsen
Sent: Montag, 27. August 2018 14:11
To: users@camel.apache.org
Subject: Re: SOAP request causing null namespace URI in SimpleNsStreamWriter
camel-cxf/woodstox
Hi
What older version of Camel and camel-cxf were you using that worked?
You are also welcome to log a JIRA about this NPE.
From the debugger if you change that nsUrl from null, to that SOAP namespace,
does it work then?
And what if you change the nsUrl to be an empty string?
On Mon, Aug 27, 2018 at 11:44 AM Fritz, Jürgen wrote:
>
> Getting NullPointer at
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWrit
> er.java:134),
> Because parameter nsURI is null.
> (full stack trace below)
>
> First call of this method prefix="soapenv", nsURI=null Second call:
> prefix="soap", nsURI=="http://schemas.xmlsoap.org/soap/envelope/; (I
> changed the value of nsURI in the debugger in the first call to arrive
> here)
>
> Same SOAP request was working with the same application using an older
> version of camel-cxf under Java 1.7
>
> woodstox-core-5.0.3
> camel-cxf 2.22.0
>
> Any ideas ?
>
> Regards
> Jürgen
>
> ===
>
> http://schemas.xmlsoap.org/soap/envelope/;
> xmlns:tss="http://axpo.ch/emis/v1/TimeseriesService;>
>
> MySourceSystem
>
>
>
> IN1806141130169762894
> NA
>
>
> 1234
> MW
> PT15M
>
> quantity="0.041" status="VALID"/>
> quantity="0.036" status="VALID"/>
>
>
>
>
>
>
>
>
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWrit
> er.java:134
>
> 10:27:09,294 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default
> task-118) Application
> {http://axpo.ch/emis/v1/TimeseriesService}TimeseriesService#{http://axpo.ch/emis/v1/TimeseriesService}send
> has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Error
> during type conversion from type:
> org.apache.camel.converter.jaxp.XMLStreamReaderInputStream to the required
> type: javax.xml.stream.XMLStreamReader with value
> org.apache.camel.converter.jaxp.XMLStreamReaderInputStream@9c55922 due
> java.lang.NullPointerException
>at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.checkFailure(CxfConsumer.java:344)
> [camel-cxf-2.22.0.jar:2.22.0]
>at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.setResponseBack(CxfConsumer.java:318)
> [camel-cxf-2.22.0.jar:2.22.0]
>at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.syncInvoke(CxfConsumer.java:244)
> [camel-cxf-2.22.0.jar:2.22.0]
>at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:162)
> [camel-cxf-2.22.0.jar:2.22.0]
>at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_144]
>at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [rt.jar:1.8.0_144]
>at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
> [cxf-rt-transports-http-3.2.5.jar:3.2.5]
>at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216)
