Please suggest the option to deploy multi-region fail-over with ActiveMQ Artemis?
Any functionality in Artemis similar to network of brokers?
Related
I am deploying a kafka cluster on Kubernetes using Strimzi kafka operator. I need to be able to query Kafka JMX MBEANS remotely through HTTP/REST using Jolokia (Jolokia is an agent that converts and exposes JMX MBEAN measurements for querying over HTTP…).
AFAIK, Strimzi documentation does not provide any hint on how to attach Jolokia to kafka brokers. Hence can you please provide a hint on what kind of modifications to the deployment files (strimzi operator and/or cluster deployment files) so that Jolokia is attached to the brokers/Zookeeper instances.
Last I checked, Strimzi offers Prometheus JMX Exporter already, not Jolokia. Prometheus also offers Mbeans over HTTP. https://strimzi.io/docs/operators/latest/overview.html#metrics-overview_str
But the concept is the same, and the fact you're using Strimzi doesn't really matter, since the process is the same regardless of how Kafka is running - you need that JVM agent added into KAFKA_OPTS environment variable. You might want to use a custom docker image that has the Jolokia agent available
We are currently using IBM MQ for messaging and moving to ActiveMQ, but the challenge is there are few producers who would continue to use IBM MQ for sometime whereas consumers are ready to migrate.
Is there a way we can bridge IBM MQ and ActiveMQ Artemis, so that any message that arrives in IBM MQ queue should get auto replicated in ActiveMQ and consumer pick up from there ( same goes in reverse order)?
Implementing a new service which consume from IBM MQ and put of ActiveMQ does not seem feasible as there are huge list of services and this redundant work does not seems feasible at enterprise level.
I'm using ActiveMQ Artemis in a master / slave cluster with HA. I access it through the host of each master, but through the VIP that delivers the hosts, he keeps asking me to login in loop.
Here is an image of the topology that is currently working.
Only the access to the console by the VIP does not work. I use the same topology for ActiveMQ and it works. I am balanced for the master host.
Is it possible to access the ActiveMQ Artemis web console through a single point?
Is it possible to connect to HornetQ server using ActiveMQ Artemis client libraries (1.5.x or 2.x)?
ActiveMQ Artemis has kept compatibility with HornetQ in that HornetQ clients can connect to an ActiveMQ Artemis broker. Compatibility has also been maintained so that newer ActiveMQ Artemis clients can connect to older ActiveMQ Artemis brokers. However, there's no tests that cover ActiveMQ Artemis clients connecting to a HornetQ broker. It may work, but there's no guarantee. The recommendation would be to simply continue using HornetQ clients to connect to HornetQ brokers.
I am trying to connect an Apache Artemis broker with an Amazon MQ broker to create a hybrid architecture. I have tried connecting ActiveMQ with Amazon MQ, and I could achieve it by using "network connectors" in the broker.xml file and it worked fine.
For connecting Amazon MQ and Artemis brokers I have added below shown "bridge configuration" and the "connector" to the Artemis broker.xml file
<bridges>
<bridge name="my-bridge">
<queue-name>factory</queue-name>
<forwarding-address>machine</forwarding-address>
<filter string="name='rotor'"/>
<reconnect-attempts>-1</reconnect-attempts>
<user>admin</user>
<password>12345678</password>
<static-connectors>
<connector-ref>netty-ssl-connector</connector-ref>
</static-connectors>
</bridge>
</bridges>
<connectors>
<connector name="netty-ssl-connector">ssl://b-...c-1.mq.us-west-2.amazonaws.com:61617?sslEnabled=true;</connector>
</connectors>
I'm getting an exception: ssl schema not found.
So I'm trying to understand whether connecting the Artemis and AmazonMQ brokers is same as connecting Activemq and AmazonMQ brokers (i.e by changing the configuration in the broker.xml file)? If so, what are the changes I need to make to the above shown configuration?
ActiveMQ Classic (i.e. 5.x) and Amazon MQ use the OpenWire protocol to establish connections in a network of brokers. ActiveMQ Artemis supports clients using the OpenWire protocol. However, ActiveMQ Artemis uses its own "core" protocol for bridges and clustering. Therefore you won't be able to create a bridge from ActiveMQ Artemis to ActiveMQ Classic or Amazon MQ since those brokers don't understand the Artemis "core" protocol.
The ssl schema is used by OpenWire clients, not "core" clients. That is why you can't create an Artemis bridge using it.
If you want to integrate Artemis and Amazon MQ I'd recommend something like Camel or even possibly the JMS bridge that ships with Artemis. You can see examples of both in this example which ships with Artemis.