Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / April 2006

Tip: Looking for answers? Try searching our database.

JMS Overview

Thread view: 
Major - 20 Apr 2006 13:28 GMT
I have been looking on JMS these days and will work on JMS in near
future. Below is what I learned from the tutorials -

JMS provider is a server/provider that manages the queue/topic
depending upon the messaging models used. The sender sends the messages
to the queue that exist on provider and receiver fetches the messages
from the provider.

2 types of messaging domains are there -

Point to Point
-    As the name suggest, this is one to one messaging. For every message
there will be a consumer/receiver.
-    A queue is assigned for a receiver and the receiver receives the
messages from that queue only.
-    One queue can be assigned for multiple receivers.
-    The receiver can retrieve the messages from the queue independent of
the time (i.e. before the message is timed out). It can be possible
that the sender put the message on the queue when the receiver was not
running, but still receiver can receive the message when it wakes up.
-    On successful processing of messages, receiver gives acknowledgement.

Publish/Subscribe
-    This is one to many messaging. Each message may have multiple
consumers.
-    Publishers & Subscribers have time dependency. The subscriber must be
active in order for it to consume message.

Please put on your comments on this or you can extend it further if you
want to add some to this. Tell me whether my understanding is correct
or not. Ideas of application that utilizes various features of JMS will
be a great help.
andreherzergil@gmail.com - 20 Apr 2006 15:03 GMT
Hi,

On publish and subscribe there isn't any ensure that the message will
be received by the subscribe.

 Any distribute software can take advanced of this mensageing system.
On of the most knowlegded system is a Chat program. One other can be a
batch process you send some message for one process you know that can
take a longer time.

I hope that can help
Jim - 21 Apr 2006 03:52 GMT
>I have been looking on JMS these days and will work on JMS in near
>future. Below is what I learned from the tutorials -
[quoted text clipped - 9 lines]
>-    As the name suggest, this is one to one messaging. For every message
>there will be a consumer/receiver.

Almost. You can have multiple senders. This can be used to advantage
in a multi-threaded application. Each thread does work and posts its
result to a common consumer.

>-    A queue is assigned for a receiver and the receiver receives the
>messages from that queue only.
[quoted text clipped - 15 lines]
>or not. Ideas of application that utilizes various features of JMS will
>be a great help.

Remember that the message consumer can set up MessageListeners
so that data may be received asynchronously. Makes life much easier.


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.