Biagio- The Bridge is probably not where you want to go, since it has to be setup on a queue-by-queue basis. It is generally geared for moving data from one queue to another non-ActiveMQ JMS provider.
Virtual Topics + Network Connectors and Mirrored Queues + Network Connectors would allow you to shape the “copy” of the data as you see if and then forward the copies of messages from PROD to the ACC env. If you are using a Queue, a Camel route is a better option since it provides process control and a bunch of other features (concurrentConsummers, throttling, process control, etc). Side note— Camel was born out of the ActiveMQ project to address these scenarios in a more manageable way vs having server-side static configuration — like the JMS bridge feature. -Matt > On Apr 14, 2021, at 3:31 AM, Zampogna, Biagio <biagio.zampo...@ns.nl.INVALID> > wrote: > > Hi > > > In my scenario I want that each msg reaching activemq PROD is processed by > the client application of the specific queue in PROD. > > At the same time, the msg if forwarded/bridged to the activemq ACC, and is > processed by the client application of the specific queue in ACC as well. > > The PROD env and the ACC env are NOT co-hosted, they are sitting on different > machines and different subnets. > > > Regarding Camel, I'm interested about this > > https://activemq.apache.org/enterprise-integration-patterns > > and specifically about the following statements > > "You can easily add any of the supported Enterprise Integration > Patterns<https://activemq.apache.org/enterprise-integration-patterns> into > ActiveMQ (either on the JMS client or in the broker process) to support smart > routing, transformation and a whole host of other powerful patterns." > > > Using EIP in the ActiveMQ Broker > > The broker's activemq.xml file comes already configured to support Camel; you > just need to customize the routing rules. > > > Can anyone share the activemq.xml that shows me how, in the activemq.xml?, I > shows how to implement the JMS - JMS Bridge? > > > Thanks in advance > > > kind regards > > > Biagio Zampogna > > > > > > > > ________________________________ > From: Zampogna, Biagio > Sent: Tuesday, April 13, 2021 8:23 PM > To: users@activemq.apache.org > Subject: AchiveMQ 5 - JMS to JMS bridge > > > Hello, > > > In my solution the inbound msgs are coming in via achivemq 5.15 (Artemis is > not an option at the moment). > > I want to duplicate the PROD env inbound msgs, and send it to the ACC env > achivemq. > > Obviously the prod achivemq is sitting on a different cluster than the ACC > activemq. > > I was looking at the > > https://activemq.apache.org/jms-to-jms-bridge > > But I don't fully understand how to adapt it for my scenario. > > I mean if I look at this example > > http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/network/jms/queue-xbean.xml > > This is only if the remote broker is in the same host (localhost), therefore > doesn't work in my case. > > > If I definein the XMLConfiguration the remote like this > > <broker xmlns="http://activemq.apache.org/schema/core"; id="remotebroker" > brokerName="remotebroker" persistent="false"> > <transportConnectors> > <transportConnector uri="tcp://<remote-Host>:61616"/> > </transportConnectors> > </broker> > > > I obviously get a startup error > > > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'remotebroker' defined in class path resource [activemq.xml]: > Invocation of init method failed; nested exception is java.io.IOException: > Transport Connector could not be registered in JMX: java.io.IOException: > Failed to bind to server socket: > tcp://test3-vt.northeurope.cloudapp.azure.com:61616 due to: > java.net.BindException: Cannot assign requested address: JVM_Bind? > > > So, any help/hint how to implement the JMS to JMS bridge in my scenario? > > > Kind regards > > > Biagio > > > > ________________________________ > > Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor > (gebruik door) de geadresseerde. De e-mail kan persoonlijke of vertrouwelijke > informatie bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of > verstrekking van (de inhoud van) deze e-mail (en eventuele bijlagen) aan > derden is uitdrukkelijk niet toegestaan. Indien u niet de bedoelde > geadresseerde bent, wordt u vriendelijk verzocht degene die de e-mail verzond > hiervan direct op de hoogte te brengen en de e-mail (en eventuele bijlagen) > te vernietigen. > > Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
