Hi Andre, I'm not very clear on exactly what you're trying to do, but a few thoughts and questions come to mind.
Did you consider joining the two zones into a single network using an inter-router connection instead of a route-container connection? This would provide link-route access from both zones to your destinations. Assuming you have good reasons for using a route-container connection between the zones: Does your remote-amq-mesh connection successfully connect? If so, did you create a link-route configuration in _both_ zones? I don't believe that the router normally issues an "amqp:not-found" error. Is it possible that the "address:queue" node does not exist on your destination and that your destination (broker?) is issuing the error? -Ted On Tue, Mar 9, 2021 at 2:48 PM André van der Heijden < [email protected]> wrote: > Dear qpid developers, > > I am wondering if it's possible to use linkrouting when you connect a mesh > in ZoneA (for example in Azure) to a mesh in ZoneB (for example in AWS). We > have established such a network and connect the two meshes via a connector > that looks like this: > > connector { > name: remote-amq-mesh > host: zone-b.example.azure.address.io > port: 443 > saslMechanisms: EXTERNAL PLAIN > > sslProfile: client_tls > saslUsername: remote_connection@amq-interconnect-mesh > saslPassword: ***** > > role: route-container > verifyHostname: false > idleTimeoutSeconds: 0 > messageLoggingComponents: all > } > > When trying to connect to an address:queue that is in the other Zone and is > exposed via linkrouting, we get the following error: > > java.util.concurrent.ExecutionException: > javax.jms.InvalidDestinationException: Node not found [condition = > amqp:not-found] > at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191) > > So at first sight, it seems that the above solution isn't working and we > cannot use linkrouting in a inter-cloud setup with the meshes connected > over a TLS route. Do you think this is plausible or do you have other > experiences? > > If the above is indeed impossible, would creating some routes that expose > AMQPS directly between different cloud environments, so that we can connect > the meshes inter-cloud via AMQPS directly be a good idea? Are there any > obvious downsides to this approach? > > Thanks a lot for your time. > > Kind regards, > > André van der Heijden >
