[jira] [Created] (AMQ-6946) PeerBrokers contains raw URI from transportConnector

[Martin Theiss (JIRA)]

Martin Theiss created AMQ-6946:
----------------------------------

             Summary: PeerBrokers contains raw URI from transportConnector
                 Key: AMQ-6946
                 URL: https://issues.apache.org/jira/browse/AMQ-6946
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker, Connector
    Affects Versions: 5.15.3
            Reporter: Martin Theiss


When two transportConnectors are configured and one has updateClusterClients or 
rebalanceClusterClients enabled, a client connecting to the transportConnector 
will not work reliable.

In org.apache.activemq.broker.BrokerService.getDefaultSocketURIString(), it 
loops over all transportConnectors and deteremines the defaultSocketURI. This 
is used, when no peer has joined the cluster.

Depending on the order of the transportConnectors, this results in a peer with 
0.0.0.0 being declared. This is due to the second connector not being started 
at the point where defaultSocketURI is needed.

Working:
{code:java}
            <transportConnector name="openwire_ssl" 
uri="ssl://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=2147483648"updateClusterClients="true"
 rebalanceClusterClients="true" updateClusterClientsOnRemove="true" />
            <transportConnector name="openwire" 
uri="tcp://0.0.0.0:61617?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"
 />
{code}

NOT working:
{code}
            <transportConnector name="openwire" 
uri="tcp://0.0.0.0:61617?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"
 />
            <transportConnector name="openwire_ssl" 
uri="ssl://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=2147483648"updateClusterClients="true"
 rebalanceClusterClients="true" updateClusterClientsOnRemove="true" />
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)