[ https://issues.apache.org/jira/browse/CXF-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-4741: ----------------------------- Component/s: Transports > Different conduits are used when configuring stub and sending actual message > ---------------------------------------------------------------------------- > > Key: CXF-4741 > URL: https://issues.apache.org/jira/browse/CXF-4741 > Project: CXF > Issue Type: Bug > Components: Transports > Affects Versions: 2.6.2, 2.6.4 > Reporter: Yaroslav Gnatyuk > > I was trying to set TLS context as described here: [How to configure the > HTTPConduit for the SOAP > Client?|http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport%28includingSSLsupport%29-HowtoconfiguretheHTTPConduitfortheSOAPClient%3F] > However it doesn't work in CXF 2.6.2 and 2.6.4 while it worked perfectly fine > in 2.5.3 > When looking into the code (line numbers are for version 2.6.4) I discovered > that during this configuration a new message is created and passed to conduit > selector (in this case UpfrontConduitSelector) - ClientImpl.getConduit():846. > New conduit is created, assigned to message and returned. > However when I do an actual call, I get to ClientImpl.doInvoke():486 where > another message is created. Later on prepare() is called on conduit selector > at ClientImpl.prepareConduitSelector():850 but the message is different so > another conduit is created. > This results in my conduit config being disregarded and I'm getting > SSLHandshakeException -- This message was sent by Atlassian JIRA (v6.3.15#6346)