OnJava: Designing Messaging Applications with Temporary Queues

OnJava has published Thakur Thribhuvan's "Designing Messaging Applications with Temporary Queues," an article explaining how to use JMS' temporary queue capability to allow applications to "efficiently scale because you can easily expand the number available at runtime."
Temporary Destinations: An OverviewTemporary destinations (temporary queues or temporary topics) are proposed as a lightweight alternative in a scalable system architecture that could be used as unique destinations for replies. Such destinations have a scope limited to the connection that created it, and are removed on the server side as soon as the connection is closed. Only a single well-known static queue is required for producers/senders to connect with consumers using temporary destinations. The JMS header field JMSReplyTo is always used in conjunction with temporary destinations.Since the identity of the temporary destination is known only by the connection or session that created it, the consumer/receiver cannot know the destination name. The solution is to have the producer/sender send the name of its temporary destination as a header field (JMSReplyTo), as part of a message, sent to a known static queue listened to by the producer/sender.Limitations of Temporary DestinationsThere are a few limitations that must be recognized regarding temporary destinations:
A temporary destination can only be consumed by the connection that created it.
The life span of temporary destinations is only for the duration of the connection where they are created.
When you close the connection that has a temporary destination, the destination is closed and its contents are lost.
You cannot have durable subscriptions to a TemporaryTopic.
Each temporary destination is unique and cannot be copied.
Temporary destinations cannot be routed using an enterprise messaging service.
Threaded replies
·
OnJava: Designing Messaging Applications with Temporary Queues by Joseph Ottinger on Mon Apr 23 10:17:09 EDT 2007
·
Grids? by Konstantin Ignatyev on Mon Apr 23 14:51:13 EDT 2007
·
Re: Grids? by nati shalom on Tue Apr 24 20:22:41 EDT 2007
·
dead horse by Cameron Purdy on Tue Apr 24 23:28:42 EDT 2007
·
Re: dead horse by James Strachan on Wed Apr 25 01:34:27 EDT 2007
·
Re: dead horse by Jan de Jonge on Wed Apr 25 06:45:18 EDT 2007
·
Re: dead horse by Cameron Purdy on Wed Apr 25 16:05:14 EDT 2007
·
Re: dead horse by Will Hartung on Wed Apr 25 16:25:03 EDT 2007
·
Re: dead horse by Will Hartung on Wed Apr 25 16:25:04 EDT 2007
·
Re: dead horse by Shay Banon on Wed Apr 25 10:47:41 EDT 2007
·
Re: dead horse by Shay Banon on Wed Apr 25 10:49:53 EDT 2007
·
Re: dead horse by Cameron Purdy on Wed Apr 25 15:56:06 EDT 2007
·
Re: dead horse by Shay Banon on Thu Apr 26 04:05:34 EDT 2007
·
Re: dead horse by Cameron Purdy on Mon Apr 30 16:12:27 EDT 2007
·
Re: Grids? by nati shalom on Tue May 08 09:45:55 EDT 2007
·
Scaling the number of queues. by Peter Lawrey on Tue Apr 24 11:01:57 EDT 2007
·
Re: OnJava: Designing Messaging Applications with Temporary Queu by James Strachan on Tue Apr 24 12:46:47 EDT 2007
·
Re: OnJava: Designing Messaging Applications with Temporary Queu by Maurizio Turatti on Sat Apr 28 06:58:00 EDT 2007