TIBCO FORUM :: Tibco Developer Community :: A Land of TIBCO Masters
February 07, 2016, 03:19:14 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: A Tibco Developer community and a public TIBCO FORUM and top in tibco forums, targetting tibco solutions. You can learn TIBCO, help others to solve their TIBCO issues, or find solution for your TIBCO issues. This site Strickly for the people who has interest in using TIBCO and looking for TIBCO HELP, use this tibco forum for all your tibco problems, very helpful for Tibco begginers.
   Home   Help Login Register  
Pages: [1]
Author Topic: Queues Vs Topics in TIBCO EMS  (Read 19478 times)
Hero Member
Posts: 1576

« on: May 08, 2008, 12:45:11 PM »

There are two major models for messaging supported by JMS: queues and topics. Queues are based on a point-to-point messaging model. Topics make use of the new publish-and-subscribe messaging model.

Regardless whether queues or topics are used, the messages are not sent directly peer-to-peer. Messages are forwarded to a JMS infrastructure that is composed of one or more JMS servers. The servers are responsible for providing the quality-of-services to JMS and responsible for implementing all the components not addressed by JMS Specification.

When determining when to use queues versus topics consider the two fundamental messaging mechanisms. The first is point-to-point messaging, in which a message is sent by one publisher (sender) and received by one subscriber (receiver). The second is publish-subscribe messaging, in which a message is sent by one or more publishers and received by one or more subscribers. The messaging model as listed below will dictate when to use a queue or a topic:

One-to-one messaging                   Queue    point-to-point   
One-to-many messaging   Topic   publish-subscribe   
Many-to-many messaging   Topic    publish-subscribe model

« Last Edit: May 12, 2008, 07:51:23 AM by architekt » Logged
Posts: 3

« Reply #1 on: June 16, 2009, 12:35:42 AM »

Thanks Architekt.Can you please explain me in brief the following? Difference between Exclusive and Non Exclusive Queues. I am bit confused.Thanks again.This forum is really helping me to study.
Jr. Member
Posts: 59

« Reply #2 on: June 16, 2009, 01:47:19 AM »

you can define a queue as exclusive to make sure that all the messages are always sent to the same consumer, even if you have more than one connected to it. If you make it exclusive the rest of the consumers are "on standby" so if the primary fails another one is set as primary and starts receiving.

If you set them to non-exclusive (the default value) and you have more than one consumer connected to the queue the messages are delivered in a round robin fashion to balance the load.


Haritza Zubillaga
SOA-BPM Architect
Pages: [1]
Jump to:  

Powered by SMF 1.1.20 | SMF © 2013, Simple Machines
SMFAds for Free Forums