I have Sun's Message Queue 4.3. Default installation on localhost using imqbroker daemon. Opened one queue.
I want to consume messages written to the queue above from .NET.
I understood there is ActiveMQ solution, version 5.3.
Checked ActiveMQ for .NET (version 1.1) and it works OK for ActiveMQ queues which are similar to Sun JMS.
My problem is that I want to bridge my existing Sun MQ 4.3 to an ActiveMQ queue and the documentation in http://activemq.apache.org/jms-to-jms-bridge.html
is not very clear.
can someone point exactly how to map activemq's config file to bridge:
Sun MQ queue named QUEUE1 on imqbroker#localhost:7676 (maybe jms port 1545? default install)
to
ActiveMQ queue named QUEUE2 on activemq:tcp://localhost:61616
I'm loosing it .... Thanx
You can use Apache Camel JMS component to connect the different brokers:
AFAIK Camel is included in ActiveMQ.
Related
I have a requirement to create a bridge between a Queue in ActiveMQ and a Queue in Solace. When ever there is a message in ActiveMQ Queue it should automatically get transferred to SolaceQ.
I'm struggling to find the steps for this configuration. I have ActiveMQ installed on my local machine. Request you to please throw some light on this.
FYI: I'm very new to ActiveMQ/Solace
I think you'll need to do this via JMS since both ActiveMQ and Solace support it. Check out ActiveMQ's docs here: https://activemq.apache.org/jms-to-jms-bridge
I'm using Apache ActiveMQ Artemis (N1) for my work, and recently I've got a task to send some messages to another ActiveMQ "Classic" (N2) which is used by another system. However, I don't know how should I write divert configurations at broker.xml file. Is it possible? Could you give an example of divert to another URL-address and queue. Where should I write login/password for connection to N2?
Diverts in ActiveMQ Artemis only work with local resources. To send messages to another instance of ActiveMQ Artemis you'd use a core bridge. However, that only works between instances of ActiveMQ Artemis. ActiveMQ "Classic" doesn't support the protocol which the core bridge uses.
In order to send messages from ActiveMQ Artemis to ActiveMQ "Classic" you'd need to use something like Camel or the JMS bridge shipped with ActiveMQ Artemis. Both of these solutions can be deployed as web applications using the embedded web application server in ActiveMQ Artemis. We ship examples of both. The Camel example is in examples/features/standard/camel/ and the JMS bridge example is in examples/submodules/inter-broker-bridge.
I have a HornetQ project on JBoss 6 using JDK-6, and an ActiveMQ project on WildFly 18 using JDK-11. Can I access the HornetQ topic in the ActiveMQ project or vice versa?
If you're using ActiveMQ Artemis embedded in WildFly 18 then you should be able to connect to it from your HornetQ client because ActiveMQ Artemis is based on the HornetQ code-base and has maintained backwards compatibility with older HornetQ clients.
However, you will not be able to use the ActiveMQ Artemis JMS client to talk to HornetQ.
I am using the ActiveMQ Connector to connect to an ActiveMQ Artemis broker. While Mule and ActiveMQ Artemis are running if suddenly I stop and start again or restart the ActiveMQ Artemis instance alone then Mule is not able to connect again.
You need to configure appropriate re-connection strategy, in the global elements properties JMS Config, Advanced tab. change it to forever and should work.
I successfully completed a POC using Spring Reactor Netty Stomp client (Spring messaging framework) to connect to RabbitMQ on port 61613 (port dedicated for STOMP). That was just a POC. Now I have to build something concrete to be able to deploy in prod environments. I was Googling Spring Messaging vs Spring Integration and stumbled upon Apache Camel.
RabbitMQ component page in the Camel documentation talks about port 5672 and that is AMQP. The STOMP component page talks about ActiveMQ.
I did not see any examples or documentation regarding Camel in conjunction with RabbitMQ and STOMP.
Can Apache Camel be used to connect to RabbitMQ on port 61613?
The Camel documentation for the STOMP component states:
The Stomp component is used for communicating with Stomp compliant message brokers, like Apache ActiveMQ or ActiveMQ Apollo.
Notice that it says like Apache ActiveMQ. It doesn't say it has to be Apache ActiveMQ. It just uses ActiveMQ as an example of a "Stomp compliant" message broker. If RabbitMQ supports STOMP then Camel's STOMP component should work without issue.
Looking at Camel's StompEndpoint it clearly uses the brokerURL from the configuration to make the connection to the Stomp broker. It uses the Fusesource Stomp client implementation which should work with any Stomp compliant broker.
It's also worth noting that Camel is an integration framework and Stomp is a simple, open messaging protocol so it doesn't make much sense for the Stomp component within Camel to only work with a couple of ActiveMQ brokers. It can (and will) work with any Stomp compliant broker (just as the documentation states).