View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820457#3820457
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820457 "ivelin" wrote : "ivelin" wrote : "ivelin" wrote : HA JMS is now in Branch 3.2 and will be released with JBoss 3.2.3RC2. Help us test it. Report problems on this thread. Ivelin Ivelin Is it possible to provide a singleton service for JMS Destinations (queue/Topic) also ? Example scenario : 1) Two clustered node with identical setup 2) JMS Persistent Manager in both the node points to same database tables (JMS_MESSAGES & JMS_TRANSACTIONS). 3) When the Nodes are started, Connection Factory (HAIL) will be available only in one server but the destinations(Queue) will be active in both the nodes. The problem in having destination active in both the nodes is that, if there are any pending messages in the database then they will get de-queued by both the nodes during startup. So if we implement a Singleton service for Queues/Topics, we can overcome this issue. i.e. Queue/Topic will be available only in one node and whenever a node crashes then the other node can become a singleton and start the Queue/Topic( Destination). All the clients can use HA JNDI to access the queue. Please correct me if am i wrong Thanks & Regards Devaraj ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
