Artemis supports all the same clients plus an extra one. It supports the Core protocol (The Artemis native protocol), OpenWire(which is the ActiveMQ 5.x native protocol), AMQP, MQTT, and STOMP. So any of your existing clients will work with the broker as long as you have enabled the protocol support. So if you want to use existing ActiveMQ clients then you would need to enable OpenWire.
Take a look at https://activemq.apache.org/artemis/docs/2.1.0/protocols-interoperability.html for information on enabling protocols. Also, I just noticed on that documentation page under the OpenWire section that it says "Apache ActiveMQ Artemis JMS client" which should say "Apache ActiveMQ 5.x JMS client". I'll fix that in the documentation. On Thu, Jun 8, 2017 at 3:40 AM, xabhi <xabh...@gmail.com> wrote: > How hard would be to switch just the messaging server from ActiveMQ to > Artemis. There are a lot of JMS, Perl, Python clients connecting to our > ActiveMQ instance. > > Is Artemis being developed as drop-in replacement for ActiveMQ that can > work > seamlessly with activemq-client libraries without much changes? It would be > great if I can use it as a drop-in replacement for my current ActiveMQ > instance without disturbing client side code, much easier to test if it is > possible. > > Thanks, > Abhi > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Switch-to-Artemis-from-ActiveMQ-v5-14-4-tp4727014p4727185.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
