JMS Bridge implementation question

[progMetal <er...@infor.com>]

For connecting two Artemis messaging systems across the internet, would each
need to implement a JMS bridge? From the documentation, it just says that
"a" bridge is needed (read as singular). Does that mean "a" bridge at each
end or really just one (pick a side)?

thanks  



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: JMS Bridge implementation question

[progMetal <er...@infor.com>]

Thanks Justin, that helps.



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: JMS Bridge implementation question

[Justin Bertram <jb...@apache.org>]

You've got a couple of options here...

The JMS bridge [1] implementation shipped with ActiveMQ Artemis can "push"
or "pull" meaning it can consume messages from a local queue and send them
to a remote address (that's "push") or it can consume messages from a
remote queue and send them to a local address (that's "pull"). There's no
need to deploy a bridge on both brokers. To be clear, the JMS bridge
implementation is just a POJO so in order to deploy it on the broker you'd
need to wire it up in a Spring web app for example.

You can also use one or more "core" bridges [2]. A core bridge can only
"push" messages so if you need to actually exchange messages between the
brokers you'd need to deploy a core bridge on both so you can push messages
from both brokers to the other.


Justin

[1]
http://activemq.apache.org/components/artemis/documentation/latest/jms-bridge.html
[2]
http://activemq.apache.org/components/artemis/documentation/latest/core-bridges.html

On Thu, Apr 11, 2019 at 1:06 PM progMetal <er...@infor.com> wrote:

> For connecting two Artemis messaging systems across the internet, would
> each
> need to implement a JMS bridge? From the documentation, it just says that
> "a" bridge is needed (read as singular). Does that mean "a" bridge at each
> end or really just one (pick a side)?
>
> thanks
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>