[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    RE: Migrating plugins from ActiveMQ to Artemis
From:       Burt Repine <brepine () 24hourfit ! com>
Date:       2021-11-10 0:07:53
Message-ID: BYAPR03MB4854B5D194132D23B747BC5AAF939 () BYAPR03MB4854 ! namprd03 ! prod ! outlook ! com
[Download RAW message or body]

Justin, you were correct, I was able to use the inter-broker-bridge example along \
with the Qpid client to configure a bridge successfully. Thanks a bunch for the help.

-----Original Message-----
From: Justin Bertram <jbertram@apache.org> 
Sent: Monday, November 8, 2021 3:23 PM
To: dev@activemq.apache.org
Subject: Re: Migrating plugins from ActiveMQ to Artemis

CAUTION: This email originated outside 24 Hour Fitness. Do not click links or open \
attachments unless you recognize the sender and know the content is safe.


I'm not an expert in 5.x plugin architecture so I can't deduce anything from the \
classes being used unfortunately. However, given the description of your use-case it \
sounds like you could in fact use a simple bridge (or set of bridges) to move the \
messages from Azure to local queues as demonstrated in the inter-broker-bridge \
example.

My answer on Stack Overflow was in the context of the question about using AMQP with \
spring-boot-starter-artemis. The Spring code in question was using the core JMS \
client (i.e. ActiveMQ Artemis' native JMS client) but the user was just trying to \
change the port number and expecting it to use AMQP instead. This really isn't \
relevant to your use-case as far as I can tell.


Justin

On Mon, Nov 8, 2021 at 3:45 PM Burt Repine <brepine@24hourfit.com> wrote:

> Thank you for the quick response.
> I inherited this code and the group responsible is long gone...anyway 
> best I can tell it listens on 4 Azure queues in the cloud and places 
> any messages to those queues onto a corresponding on-prem ActiveMQ queue.
> Any errors encountered during the process are placed onto an ActiveMQ 
> error queue.
> It was built on ActiveMQ 5.13.3.
> 
> The classes in question are:
> 
> org.apache.activemq.broker.ConnectionContext
> org.apache.activemq.broker.region.Destination
> org.apache.activemq.broker.Broker
> org.apache.activemq.broker.ProducerBrokerExchange
> 
> Your comment on the Qpid client is interesting - I diverted from that 
> path after reading this post (coincidentally from you) but will 
> certainly give it another go:
> 
> https://stackoverflow.com/questions/68560819/spring-boot-starter-artem
> is-with-amqp-protocol
> 
> 
> -----Original Message-----
> From: Justin Bertram <jbertram@apache.org>
> Sent: Monday, November 8, 2021 10:36 AM
> To: dev@activemq.apache.org
> Subject: Re: Migrating plugins from ActiveMQ to Artemis
> 
> CAUTION: This email originated outside 24 Hour Fitness. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
> 
> 
> Can you elaborate on what the plugin does? I assume it's more than 
> just a bridge otherwise you could just use something like a Camel 
> route and avoid having a plugin altogether.
> 
> Also, what exact problems did you run into with creating a bridge to 
> Azure following the inter-broker-bridge example? It should be pretty 
> straight-forward to adapt it to use the Qpid JMS client which speaks 
> AMQP 1.0.
> 
> 
> Justin
> 
> On Mon, Nov 8, 2021 at 12:11 PM Burt Repine <brepine@24hourfit.com> wrote:
> 
> > Hi All,
> > 
> > 
> > 
> > We're in the same boat as the poster from last month.
> > 
> > 
> > 
> > Our plugin creates a bridge between Azure Service Bus and ActiveMQ.
> > 
> > A number of ActiveMQ classes that the plugin was built upon are not 
> > available in Artemis obviously - or if they are - I can't find them 
> > or don't know their equivalents.
> > 
> > Any suggestions on migrating this plugin?
> > 
> > 
> > 
> > On a side note, I've tried creating an artemis-jms-bridge following 
> > the Artemis inter-broker-bridge example but ran into problems 
> > connecting to Azure via the required amqp.
> > 
> > Thanks much,
> > Burt Repine
> > 
> > 
> 


[prev in list] [next in list] [prev in thread] [next in thread]