Using Message Broker in a HA Environment

-
Previous to Message Broker 7, the Transaction ID (TID) store was standalone and specific to each individual Broker in your system architecture architecture.  This made building HA solutions difficult and potentially error prone.

As a result it was possible for an event to generate duplicate updates as a result of having two different TIDs for the same event in two different TID stores (one for each broker).  


With the introduction of Message Broker 7 support for a shared queue as the TID store was introduced.

This enables a shared TID store to support multiple brokers, by configuring the TID store on a single remote queue manager.

As all brokers use the same central TID Store,  each Message Broker can ensure transaction integrity and avoid duplicate event delivery in the event of a connection failure.

http://www.ibm.com/developerworks/websphere/library/techarticles/1203_agarwal/1203_agarwal.html

Comments

Post a Comment

Popular posts from this blog

ActiveMQ, easy to use open source message oriented middleware (MOM)

-
ActiveMQ is message oriented middleware (MOM), useful for receiving and processing asynchronous messages (queues or topics). It is easily integrated with Java based applications (and others) via  the JMS API . ActiveQ offers enterprise scale features which may be required when implementing complex distributred systems such as   High availability with failover. Scalability and clustering through a distributed Network of Brokers. Pluggable persistence stores (JDBC, BDB, JDBM, file system). Distributed destinations and XA support. Caching. Connection pooling. Support for cross language clients such as . NET , C++. Support for scripting environments such as Perl, Python, and Ruby. Multiple Transport layers ( TCP , UDP, multicast, NIO, SSL , Zeroconf, JXTA, JGroups). Download at http://activemq.apache.org/
Read more

Basic Send Message to MQ with Java and IBM MQ JMS

-
package my.mq.samples;   import javax.jms.JMSException; import javax.jms.Session; import javax.jms.TextMessage; import com.ibm.mq.jms.MQQueue; import com.ibm.mq.jms.MQQueueConnection; import com.ibm.mq.jms.MQQueueConnectionFactory; import com.ibm.mq.jms.MQQueueSender; import com.ibm.mq.jms.MQQueueSession; import com.ibm.msg.client.wmq.WMQConstants; public class MQSend {     public static void main(String[] args) { try { MQQueueConnectionFactory cf = new MQQueueConnectionFactory(); cf.setHostName("localhost"); cf.setPort(1414);       cf.setIntProperty(WMQConstants.WMQ_CONNECTION_MODE, WMQConstants.WMQ_CM_CLIENT); cf.setQueueManager("QM_GRIDSERVER"); cf.setChannel("SYSTEM.ADMIN.SVRCONN");       MQQueueConnection connection = (MQQueueConnection) cf.createQueueConnection(); //MQQueueConnection connection = (MQQueueConnection) cf.createQueueConnection("username","password");  
Read more

Apache Apollo

-
Apache releases new generation of ApacheMQ http://activemq.apache.org/apollo/index.html And it produces some interesting performance results. You can read more at this blog These guys ran STOMP benchmarks against the lastest releases of the 4 most feature packed STOMP servers: Apache ActiveMQ 5.5.1 Apache ActiveMQ Apollo 1.0 Beta 6 (an ActiveMQ Subproject) HornetQ 2.2.5 RabbitMQ 2.7.0
Read more