Loading
JMS Topic VS Queue

Java Quick Notes

Refresh Your Java - Before Java Interview

We are Agile, believe in less Documentation - Only Quick notes (Java Interview Questions) of Java/J2ee Read more....


Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet
Not Included Yet

Go to SiteMap

Q)  JMS Topic VS Queue ?


Ans)

 

Queue Topic
 Follows “Point-to-point ”  Model Follows “Publish and subscribe” Model.
Only One Consumer (Client) could read the message. Zero or more consumers will receive the message.
Given Message would be available in Queue until that is read by a Client. There is a timing dependency between publishers and subscribers. The publisher has to create a message topic for clients to subscribe. The subscriber has to remain continuously active to receive messages, unless it has established a durable subscription.
With a “Queue Browser”  you could browse (View) the messages that are in Queue, but can’t consume , messages will remain in Queue even after browsing through Queue Browser.            



Back to top

------------------------- We hope you got necessary Info On -----------------------------------------

JMS Topic VS Queue


JMS Topic VS Queue

-------------------------------------------------------------------------------------------------------



Face Book
Request for a Mock Interview/Training

Get a PDF

Face Book
Same look (Read) on any device, this is Ads free