Behaviors in AMQ Network Connectors environment
Issue
-
As per How to configure AMQ connection between inner and outer network, AMQ brokers are deployed to an outer network and an inner network.
-
The broker in inner network configures
networkConnectors
below to send messages to consumers in the outer network(In this example, 10.72.45.226 is the outer network broker IP address).<networkConnectors> <networkConnector uri="static:(tcp://10.72.45.226:61616)" name="internal_to_external" duplex="true"/> </networkConnectors>
- The broker in the outer network does not configure
networkConnectors
so that this broker could not actively establish a new connection to send messages to consumers in the inner network.
-
-
Inside both outer and inner network, there are a pair of Producer & Consumer applications running to send/receive messages to/from the local broker. Also, there are a pair of Publisher & Subscriber applications configured to publish/subscribe messages to/from the local broker. To ease the description further, the names of the applications are described below:
Client Outer network Inner network Consumer ext-c int-c Producer ext-p int-p Durable Subscriber ext-s int-s Non-Durable Subscriber ext-s-non int-s-non Publisher ext-pub int-pub -
In the
networkConnectors
enabled AMQ environment, I want to understand the behaviors for my producer/consumer clients. - Sometimes due to network instability, the connection might be failed between outer and inner networks. Will there be messages loss for cross-network transmission?
- In what condition the broker will replicate the messages across the network?
- How durable subscribers differ from non-durable subscribers in the message consumption process?
Environment
- Red Hat AMQ
- 6.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.