Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-4622

Broter connect to themselves when using the Multicast Transport in NetworkConnector

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 5.8.0
    • Fix Version/s: None
    • Labels:
      None
    • Environment:

      pc(computer), windows 7(os),Multicast Transport,networkConnector

      Description

      ActiveMQ Configuration´╝Ü
      <broker useJmx="true" xmlns="http://activemq.apache.org/schema/core" brokerName="Hank1" dataDirectory="${activemq.data}">
      <transportConnectors>
      <transportConnector name="openwire" uri="tcp://0.0.0.0:61623?maximumConnections=1000&wireformat.maxFrameSize=104857600"
      discoveryUri="multicast://239.254.254.254:6255?group=mq"/>
      </transportConnectors>
      <networkConnectors>
      <networkConnector name="MQ1" uri="multicast://239.254.254.254:6255?group=mq"/>
      </networkConnectors>

      With this configuration, after starting the MQ, the MQ will appear " Network connection between vm://Hank1#0 and tcp://Computer name/IP:61623@50576(Hank1) has been established" in the activemq.log, When a consumer is listening, it will appear two consumer in "Number of Consumer" of "http://localhost:8168/admin/queues.jsp".This will lead to not receive the complete message(for example producer send 100 messages, the consumer of "ID:WCMIS147-50871-1373073323074-0:1" will receive 73 messages,and another one of "TalendESB-MQ1_Hank1_inbound_Hank1
      " will receive 27 messages)

      So ,I think this bug is dangerous,if it was really exsit

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              hank.hua Hank.X.Hua
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 24h
                24h
                Remaining:
                Remaining Estimate - 24h
                24h
                Logged:
                Time Spent - Not Specified
                Not Specified