Thanks for the reply James, To answer your question, I would have describe our application in brief.
Our application consists of a pair of geographically redundant servers both of which are active all the time, and each with with identical set of processes communicating over JMS. The fault-tolerance is not just at JMS level, but at application and database levels as well (complete site failure). It is not feasible to forward messages across sites (store forward/network between brokers) due to the volume and duplication (nature of the application- both servers would generate same information) of mesages. Also a message flow from a client to Site A via Site B should be preferrably avoided. The client(s)/GUI user(s) would choose one or the other server to work with, but would be aware of the complete application level availabilty of each which is why we need simultaneous connection to both. Using a full-fledged JNDI server and registering ConnectionFactory with it would solve the problem, but was wondering if we could achive the same with ActiveMQInitialContextFactory wherein, we could associate connectionFactorty with a particular JMS server (transport connector) I hope this gives you an idea of the problem. karthik -- View this message in context: http://www.nabble.com/Connecting-to-2-JMS-servers-t1631467.html#a4420398 Sent from the ActiveMQ - User forum at Nabble.com.
