[
https://issues.apache.org/jira/browse/AMQ-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5917.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.16.0
https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=8bb3a77270775e69c1053ed789c5a1999cae2f51
> networkConnectorStartAsync="true" results in "WARN | Could not connect to
> remote URI: ssl://... SSLContextImpl is not initialized" and failure to
> connect
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-5917
> URL: https://issues.apache.org/jira/browse/AMQ-5917
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.10.0, 5.11.1
> Reporter: Gregg Saffell
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.16.0
>
>
> With both 5.10.0 and 5.11.1, the networkConnectorStartAsync="true" is broken
> for ssl. With two networkConnectors defined, only one connection is made and
> a warning is logged for the other.
> Snippets from my activemq.xml:
> <broker xmlns="http://activemq.apache.org/schema/core" ...
> networkConnectorStartAsync="true">
> ...
> <networkConnector name="GSTEST-96_ILSTECHNOLOGY_COM-SSO"
> uri="static:(ssl://172.27.11.96:5902)?useExponentialBackOff=false&initialReconnectDelay=5000&maxReconnectDelay=5000"
> duplex="true" conduitSubscriptions="true" >
> ...
> networkConnector name="ECENTRESERVER_ILSTECHNOLOGY_COM-SSO"
> uri="static:(ssl://172.27.11.95:5902)?useExponentialBackOff=false&initialReconnectDelay=5000&maxReconnectDelay=5000"
> duplex="true" conduitSubscriptions="true" >
> The specific warning that was generated is:
> 2015-08-05 10:46:31,569 | WARN | Could not connect to remote URI:
> ssl://172.27.11.96:5902: SSLContextImpl is not initialized |
> org.apache.activemq.network.DiscoveryNetworkConnector | NetworkConnector
> Start Thread-0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)