activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-4622) Broter connect to themselves when using the Multicast Transport in NetworkConnector
Date Mon, 08 Jul 2013 19:55:49 GMT


Timothy Bish commented on AMQ-4622:

Have you tested a recent SNAPSHOT build, this appears to be a duplicate of AMQ-4408.  If you
still have an issue please attach a unit test to reproduce.  
> Broter connect to themselves when using the Multicast Transport in NetworkConnector
> -----------------------------------------------------------------------------------
>                 Key: AMQ-4622
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Connector, JMS client, Message Store
>    Affects Versions: 5.8.0
>         Environment: pc(computer), windows 7(os),Multicast Transport,networkConnector
>            Reporter: Hank.X.Hua
>             Fix For: 5.x
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> ActiveMQ Configuration´╝Ü
> <broker useJmx="true" xmlns="" brokerName="Hank1"
>     <transportConnectors>
>            <transportConnector name="openwire" uri="tcp://;wireformat.maxFrameSize=104857600"

> 		discoveryUri="multicast://"/>
>     </transportConnectors>
>     <networkConnectors>
> 	<networkConnector name="MQ1" uri="multicast://"/>
>     </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

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:

View raw message