JMS is good to talk between servers in a cluster. Frinstance we keep track of who's logged on. When you log on or off one server it publishes a message to let the other servers know. That's a variety of "distributed cache" which has many other applications.
You can use JMS to kick off long-running asynchronous processes. You're not supposed to start new threads inside an EJB container, but you can send a message to a Message Driven Bean on the same machine that will run in its own thread.
You can play with others outside your server. My company uses MQ-Series for all kinds of communication, and with an IBM JMS provider we can send to and receive from other systems. We use the "assured delivery" and "persistent queue" features to make sure that we get all inbound messages, even if we happen to be down for a while.
Any of that sound useful to you?
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
The last scenario seems most common. Does that mean - a message string received through MQ is received by MDB - the JMS client....and then what???...from here the jms pings the ??? about the received info and updates the web applications accordingly.
<blockquote><font size="1" face="Verdana, Arial">quote:</font><hr>I have no special talent. <b>I am only passionately curious.</b> <br /> <br />Albert Einstein <hr></blockquote>
I can't beleive you just said that. Now I need to calm down with this tiny ad: