This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Spring Integration, WebSphere MQ, Tomcat, & Availability

Jan 13th, 2012, 12:10 AM

Hello,

How can I configure Spring Integration, Tomcat (JNDI), and WebSphere MQ technologies to dynamically handle Availability?

Availability = when the primary MQ server is down, configure the application to dynamically use the secondary MQ server. The primary and secondary MQ servers are exactly identical apart from their host name.

Comment

If you are running active-active MQ queue managers, this is not a trivial problem. MQ clustering is the area you should be looking at.

We run active-passive. If MQ fails on one server, we fail over to another server, but also take a floating IP across as well. So an IP address is always assigned to a server that is running the active MQ node. Then we create a DNS entry that points at that floating IP and thus we always connect to the correct node that is running the queue manager.

It's been a while since I worked with WebsphereMQ, but IIRC, you configure a local connection definition table (or something named similarly) that knows about the HA broker locations and the URL you provide to the connection factory points to the local client and it deals with failover transparently.

I suggest you dig around in the IBM documentation. I'll see if I can find any more info in my email archive.