Hi, Can you check the log file ? If camel-cxf producer get some thing wrong, you should be able to tell from the stack trace in the log file.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: willemjiang On Thursday, November 15, 2012 at 11:35 PM, muruga wrote: > I am able to successfully negotiate the SSL handshake and after that it fails > with HTTP Status Code: 500. > > We are using the DataPower to access the secured WS. I am able to invoke the > service through SoapUI and it goes through fine. It fails when I invoke from > Camel. Our DataPower guys says that they are seeing the response coming back > and returned to the application. Any thoughts, would be greatly appreciated. > > org.apache.camel.component.http.HttpOperationFailedException: HTTP operation > failed invoking https://xx.x.x.x.x.x:5618/Reservation with statusCode: 500 > at > org.apache.camel.component.http.HttpProducer.populateHttpOperationFailedException(HttpProducer.java:229)[camel-http-2.10.2.jar:2.10.2] > at > org.apache.camel.component.http.HttpProducer.process(HttpProducer.java:157)[camel-http-2.10.2.jar:2.10.2] > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-HTTPS-Webservice-Consumption-HTTP-Status-Code-500-tp5722782.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
