[Hawkular-dev] ActiveMQ and JMS

[Jiri Kremser]

+1 on async messages
+1 on switching to Artemis, because afaik ActiveMQ is currently used as a common third part library + the resource adapter thing, while Artemis integration can be done in the standalone.xml (a subsystem - [1][2])

[1] http://javalibs.com/artifact/org.wildfly/wildfly-messaging-activemq
[2] http://git.io/vCXKy

jk

----- Original Message -----
| From: "John Sanda" <jsanda at redhat.com>
| To: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
| Sent: Thursday, 15 October, 2015 3:33:17 PM
| Subject: [Hawkular-dev] ActiveMQ and JMS
| 
| Hawkular uses ActiveMQ for JMS. I learned earlier this week that ActiveMQ
| implements JMS 1.1 but not 2.0 which has been out for some time and is in
| WildFly 9. JMS 2.0 has some nice changes including async sending of
| messages. In JMS 1.1 the client blocks until the server acknowledges
| successful delivery of the message. In 2.0 the sender can receive that
| acknowledgement asynchronously via a callback.
| 
| HornetQ is the default JMS provider in WildFly 8/9. If I am not mistaken part
| of the reason to go with ActiveMQ was due to the uncertainty around the
| future of HornetQ. HornetQ is now ActiveMQ Artemis[1] and will be the JMS
| provider in WlidFly 10haw. It does not look like ActiveMQ will implement JMS
| 2.0 any time soon which again, has been out for some time. Can/should we
| consider switching to HornetQ/Artemis?
| 
| [1] https://activemq.apache.org/artemis/
| 
| 
| - John
| 
| _______________________________________________
| hawkular-dev mailing list
| hawkular-dev at lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/hawkular-dev
|