You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Eric (JIRA)" <ji...@apache.org> on 2010/03/15 17:21:44 UTC
[jira] Created: (AMQ-2650) Multicast discovery seems to stop to
work.
Multicast discovery seems to stop to work.
------------------------------------------
Key: AMQ-2650
URL: https://issues.apache.org/activemq/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
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2650) Multicast discovery seems to stop to
work.
Posted by "Eric (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58328#action_58328 ]
Eric commented on AMQ-2650:
---------------------------
Can it be the result of the problem shown in AMQ-1855 ?
> Multicast discovery seems to stop to work.
> ------------------------------------------
>
> Key: AMQ-2650
> URL: https://issues.apache.org/activemq/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
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2650) Multicast discovery seems to stop to
work.
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder updated AMQ-2650:
------------------------------
Fix Version/s: 5.5.0
(was: 5.4.1)
> Multicast discovery seems to stop to work.
> ------------------------------------------
>
> Key: AMQ-2650
> URL: https://issues.apache.org/activemq/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.5.0
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2650) Multicast discovery seems to stop to
work.
Posted by "Eric (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric updated AMQ-2650:
----------------------
Attachment: Bug Multicast.doc
A word file that contains
the tcpdump trace
a Thread dump of the BEA-tpnocp09v process that doesn't want to connect to the fifth embedded broker on tpnocp13v (some queues threads and some non activemq threads were deleted)
Some JConsole screenshots of the BEA-tpnocp09v process
The activeMQ.xml file of the embedded broker of
- the BEA-tpnocp09v process
- the fifth process
- a fourth process, on the same server, that is correctly connected.
> Multicast discovery seems to stop to work.
> ------------------------------------------
>
> Key: AMQ-2650
> URL: https://issues.apache.org/activemq/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
> 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.
-
You can reply to this email to add a comment to the issue online.