You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jeff Mesnil (JIRA)" <ji...@apache.org> on 2015/10/12 13:44:05 UTC
[jira] [Commented] (ARTEMIS-253) Cluster is not formed using
replication
[ https://issues.apache.org/jira/browse/ARTEMIS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953022#comment-14953022 ]
Jeff Mesnil commented on ARTEMIS-253:
-------------------------------------
I'm not sure if that's relevant but we use JGroups with a UDP stack for group communication.
> Cluster is not formed using replication
> ---------------------------------------
>
> Key: ARTEMIS-253
> URL: https://issues.apache.org/jira/browse/ARTEMIS-253
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.1.0
> Reporter: Jeff Mesnil
>
> We have an intermittent failure when using a cluster
> of 2 replicated nodes (both are live nodes).
> In the logs, I have:
> {noformat}
> 18:28:39,833 INFO [org.apache.activemq.artemis.core.server]
> (ServerService Thread Pool -- 70) AMQ221007: Server is now live
> 18:28:39,834 INFO [org.apache.activemq.artemis.core.server]
> (ServerService Thread Pool -- 70) AMQ221001: Apache ActiveMQ Artemis
> Message Broker version 1.1.0-wildfly-6
> [nodeID=f94b61cc-6146-11e5-937b-a3e9631a50ac]
> ...
> 18:28:45,794 INFO [org.apache.activemq.artemis.core.server]
> (ServerService Thread Pool -- 71) AMQ221007: Server is now live
> 18:28:45,794 INFO [org.apache.activemq.artemis.core.server]
> (ServerService Thread Pool -- 71) AMQ221001: Apache ActiveMQ Artemis
> Message Broker version 1.1.0-wildfly-6
> [nodeID=fe8b1275-6146-11e5-b3c8-596354b7fc76]
> ...
> 18:28:46,367 INFO [org.apache.activemq.artemis.core.server] (Thread-4
> (ActiveMQ-server-ActiveMQServerImpl::serverUUID=fe8b1275-6146-11e5-b3c8-596354b7fc76-7203298))
> AMQ221027: Bridge ClusterConnectionBridge@7edf20
> [name=sf.my-cluster.f94b61cc-6146-11e5-937b-a3e9631a50ac,
> queue=QueueImpl[name=sf.my-cluster.f94b61cc-6146-11e5-937b-a3e9631a50ac,
> postOffice=PostOfficeImpl
> [server=ActiveMQServerImpl::serverUUID=fe8b1275-6146-11e5-b3c8-596354b7fc76]]@1a3e7c0
> targetConnector=ServerLocatorImpl
> (identity=(Cluster-connection-bridge::ClusterConnectionBridge@7edf20
> [name=sf.my-cluster.f94b61cc-6146-11e5-937b-a3e9631a50ac,
> queue=QueueImpl[name=sf.my-cluster.f94b61cc-6146-11e5-937b-a3e9631a50ac,
> postOffice=PostOfficeImpl
> [server=ActiveMQServerImpl::serverUUID=fe8b1275-6146-11e5-b3c8-596354b7fc76]]@1a3e7c0
> targetConnector=ServerLocatorImpl
> [initialConnectors=[TransportConfiguration(name=http-connector,
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?httpUpgradeEnabled=true&port=8080&host=localhost&http-upgrade-endpoint=http-acceptor],
> discoveryGroupConfiguration=null]]::ClusterConnectionImpl@17494988[nodeUUID=fe8b1275-6146-11e5-b3c8-596354b7fc76,
> connector=TransportConfiguration(name=http-connector,
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?host=localhost&http-upgrade-endpoint=http-acceptor&httpUpgradeEnabled=true&port=8180,
> address=jms, server=ActiveMQServerImpl::serverUUID=fe8b1275-6146-11e5-b3c8-596354b7fc76]))
> [initialConnectors=[TransportConfiguration(name=http-connector,
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?httpUpgradeEnabled=true&port=8080&host=localhost&http-upgrade-endpoint=http-acceptor],
> discoveryGroupConfiguration=null]] is connected
> {noformat}
> This AMQ221027 is a bit hard to read but it basically says that I have
> a connection from server f94b61cc to server fe8b1275...
> However I don't have a corresponding log to show that the bridge is
> also connected from server fe8b1275to server f94b61cc
> When the test passes, I do have a 2nd AMQ221027 in the opposite direction.
> How can I check that a cluster is properly formed? And why is it not always the case?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)