Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-6715

The use of the localPort attribute would not prevent the broker from using random ports

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • AMQ 7.8.5.GA
    • broker-core
    • None
    • False
    • None
    • False
    • Release Notes, User Experience
    • Hide
      • Please create a two-node cluster
      • Please configure a localPort in the connector configuration as outlined above in both broker instances
      • Please start the BrokerA then BrokerB
      • Please check the local ports, the broker would still create a random local port
      • The broker would not form a cluster should you specify the localPort attribute in the acceptor configuration. (This step is optional)
      Show
      Please create a two-node cluster Please configure a localPort in the connector configuration as outlined above in both broker instances Please start the BrokerA then BrokerB Please check the local ports, the broker would still create a random local port The broker would not form a cluster should you specify the localPort attribute in the acceptor configuration. (This step is optional)

    Description

      The AMQ 7.8.5 broker offers the localPort attribute to prevent the broker from creating random ports when creating cluster connections or core bridges. However, the broker still creates a localPort for communication:

      Configuration:

      <connectors>
    <connector name="netty-connector">tcp://192.168.1.113:61616</connector>
    <connector name="netty-connector-remote">tcp://192.168.1.116:61616?localPort=42000</connector>
</connectors>

      Output:

      tcp6       0      0 192.168.1.113:42000     192.168.1.116:61616     ESTABLISHED
tcp6       0      0 192.168.1.113:61616     192.168.1.116:50508     ESTABLISHED
tcp6       0      0 192.168.1.113:61616     192.168.1.116:60016     ESTABLISHED
tcp6       0      0 192.168.1.113:61616     192.168.1.116:42000     ESTABLISHED
tcp6       0      0 192.168.1.113:37278     192.168.1.116:61616     ESTABLISHED

      The broker would not create a random port should there be a localPort setting in the acceptor configuration. However, that results in failing to establish a cluster connection.

       

      Attachments

        Activity

          People

            rhn-support-jbertram Justin Bertram
            rhn-support-tywickra Tyronne Wickramarathne
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: