You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Alexander Trauzzi (Jira)" <ji...@apache.org> on 2020/11/10 16:51:00 UTC

[jira] [Created] (ARTEMIS-2981) Core bridge failing

Alexander Trauzzi created ARTEMIS-2981:
------------------------------------------

             Summary: Core bridge failing
                 Key: ARTEMIS-2981
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2981
             Project: ActiveMQ Artemis
          Issue Type: Bug
    Affects Versions: 2.15.0
         Environment: I am running on freshly created broker directories with no customizations done except to the {{broker.xml}} files, which I am attaching to this issue.
            Reporter: Alexander Trauzzi
         Attachments: global-broker.xml, regional-broker.xml

I'm encountering a situation where any bridge configured between two brokers is failing with the following errors showing up in the logs:

*On the receiving broker:*

 
{code:java}
411 WARN [org.apache.activemq.artemis.core.client] AMQ212037: Connection failure to /172.27.0.12:61627 has been detected: AMQ229014: Did not receive data from /172.27.0.12:61627 within the 60,000ms connection TTL. The connection will now be closed. [code=CONNECTION_TIMEDOUT]{code}
 

*On the outbound broker:*

 
{code:java}
780 WARN [org.apache.activemq.artemis.core.server] AMQ224091: Bridge BridgeImpl@3a8e6648 [name=region-s-to-global, queue=QueueImpl[name=laravel:global:default, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID=29f37694-2371-11eb-90ba-0242ac1b000c], temp=false]@34498f69 targetConnector=ServerLocatorImpl (identity=Bridge region-s-to-global) [initialConnectors=[TransportConfiguration(name=global, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?localPort=61627&port=61616&host=global-broker], discoveryGroupConfiguration=null]] is unable to connect to destination. Retrying
{code}
 
----

The nature of the problem does not to my eye indicate a communication or network visibility issue. Despite that, we've still ensured there is full connectivity between the brokers by doing some manual testing with {{nc}} and {{telnet}} with everything checking out fine.

Going off of the error messages alone, it looks as though the connection to {{61627}} is being successfully made, but that for some reason, the receiving broker is closing the connection after 60s.

It is not apparent whether this is due to a misconfiguration on my part or due to an issue in Artemis that is causing that connection to become unstable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)