You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Bilgin Ibryam <bi...@gmail.com> on 2015/04/23 12:48:48 UTC

Strange cxf behavior with https

Hi all,

I have a Camel cxf proxy route in the following form that is working fine
with http:

from cxf
transform
to cxf

But when I switch to https (both on the produce and consumer) my route is
not returning the result to the client. I can see in the logs that the
service is working fine, the cxf producer is getting a response,
serializing the result, but it never reaches the client (SOAP UI or the
browser).

To fix that I had to add synchronous=true to the cxf consumer. That fixes
the issues but I cannot explain why I have to do it when I switch from http
to https

What I'm missing?

-- 
Bilgin Ibryam

Red Hat, Inc.
Apache Camel & Apache OFBiz committer
Blog: ofbizian.com
Twitter: @bibryam <https://twitter.com/bibryam>

Author of Instant Apache Camel Message Routing
http://www.amazon.com/dp/1783283475

Re: Strange cxf behavior with https

Posted by Willem Jiang <wi...@gmail.com>.
camel-cxf is using the async invocation by default, which means the response could be send back by another thread. I’m not sure if it could cause some side effect on the SSL engine which could leverage the thread local to store some SSL session states.

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On April 23, 2015 at 6:49:21 PM, Bilgin Ibryam (bibryam@gmail.com) wrote:
> Hi all,
>  
> I have a Camel cxf proxy route in the following form that is working fine
> with http:
>  
> from cxf
> transform
> to cxf
>  
> But when I switch to https (both on the produce and consumer) my route is
> not returning the result to the client. I can see in the logs that the
> service is working fine, the cxf producer is getting a response,
> serializing the result, but it never reaches the client (SOAP UI or the
> browser).
>  
> To fix that I had to add synchronous=true to the cxf consumer. That fixes
> the issues but I cannot explain why I have to do it when I switch from http
> to https
>  
> What I'm missing?
>  
> --
> Bilgin Ibryam
>  
> Red Hat, Inc.
> Apache Camel & Apache OFBiz committer
> Blog: ofbizian.com
> Twitter: @bibryam  
>  
> Author of Instant Apache Camel Message Routing
> http://www.amazon.com/dp/1783283475
>