[ https://issues.jboss.org/browse/ARQ-1370?page=com.atlassian.jira.plugin.s... ] Oliver Bock commented on ARQ-1370: ---------------------------------- Sure, you're welcome. Regarding your proposed solution (referenced in the description): without admittedly knowing Warp's internals, this looks more like a workaround than a solution. The root cause of this problem seems to be that {{Alpha3}} requires a dedicated custom SSL context (or TrustManager, respectively) while {{Alpha2}} was able to make use of the container's existing SSL context as described in ARQ-1365 and the forum thread (referenced above). The question is: why is that and would it be possible to let {{CommandService}} reuse the existing SSL context as well? Just ignore my comment if I'm totally mistaken ;-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira