Thursday, October 7, 2004

ActiveMQ 1.1 released with clustered queues and topics and much more Its been lots of hard work and testing but we've finally got the 1.1 version of ActiveMQ released. Many thanks to those of you who've submitted patches, reported issues or taken it for a spin. There are literally heaps of new features, the major things which stick out are distributed queues and topics and clusters of message brokers auto-reconnection of clients across a cluster of brokers support for high performance non-durable queues wildcard support on queues (as well as topics) transaction log and JDBC persistence in addition to JDBM and BDB JNDI support for easy integration HTTP tunnelling support auto-broker discovery using Zeroconf (Apple Rendezvous) for a peer based network using high performance pointcast composite destinations support (allowing a publish or subscribe operation on several queues and/or topics in one atomic operation, such as writing to N queues in one operation) simpler pure-Java configuration API While it was a fairly trivial change, composite destinations are pretty handy. Often folks want something a little bit more flexible than a durable topic - which as a restriction that only 1 consumer can consume for a given clientID and subscriber name at once. e.g. sending a message to 5 different queues and a topic as one logical operation such that each queue can have a cluster of consumers competing for messages and the topic can be used for non-durable notifications. This feature can also be useful in situations like financial market data, where you can subscribe to the market data prices for all the stocks in your portfolio in one single JMS operation. 1:56:28 PM    comment []