ppalaga commented on issue #5218:
URL: https://github.com/apache/camel-quarkus/issues/5218#issuecomment-1728340755

   Thanks for the new reproducer and sorry for the delay, @jochenr. 
   
   I was able to reproduce all you mention, but at the first sight, it seems 
expected: if you do not tell the client which certs it should trust, then it 
cannot connect. Of course it should throw a clear exception, something like 
`PKIX path building failed` you report with 3.0.3, rather than hang. I'll check 
this aspect with newer quarkus and quarkus-cxf tomorrow. 
   
   So if your production env. behaves the same as test env without trust store 
set, then I'd say either the default java truststore is ignored for some 
reason, or your default java truststore is different than you think. I'll 
perform some experiments tomorrow to see which one is the case. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to