You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/07/09 21:35:33 UTC
[jira] [Closed] (AMQ-2650) Multicast discovery seems to stop to
work.
[ https://issues.apache.org/jira/browse/AMQ-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-2650.
-----------------------------
Resolution: Incomplete
No test provided to try to reproduce this issue, recommend upgrades to the latest release to capture all the current fixes.
> Multicast discovery seems to stop to work.
> ------------------------------------------
>
> Key: AMQ-2650
> URL: https://issues.apache.org/jira/browse/AMQ-2650
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.2.0
> Environment: ActiveMQ 5.2. Linux Redhat 64bits. Java 1.6 - multi network interfaces
> Reporter: Eric
> Fix For: 5.x
>
> Attachments: Bug Multicast.doc
>
>
> We are on a production system for an ERDF major project.
> We have about 15 servers called tpnocp"XY"v [ "XY" = 01,02,03,04,.. ]. On these servers, some Java processes are launched. Some of them have ActiveMQ embedded brokers. Generally speaking, these brokers are linked together by about 4 different networks of brokers with duplex or not duplex network connectors. Multicast discovery mechanism is used to dynamically create brokers connections. Default Multicast IP is used with different groups.
> I'm currently in a situation where
> - a java process is launched on tpnoc09v server, and has an embedded broker named "BEA-tpnocp09v"
> - this embedded broker dynamically discovered 4 brokers that are embedded in 4 java process that are launched on the tpnocp13v server (tpnocp13v-bus IP address is used), and connected in full duplex to them.
> - a fifth process is executed on the same tpnocp13v server, has an embedded broker which has the same ActiveMQ configuration as the 4 others that are connected to the "BEA-tpnocp09v" broker.
> - the "BEA-tpnocp09v" embedded broker is not connected to the fifth embedded broker.
> - Multicast packets relative to this fifth broker, seem to be correctly received by tpnocp09v server (tcpdump)
> - All seems stable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira