activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Help with architecture/setup
Date Thu, 20 Jul 2006 05:50:48 GMT
On 7/18/06, Marc Dumontier <marc@mdumontier.com> wrote:
>
> Hi
>
> I've got an application which needs to use jms to send messages with
> guaranteed delivery in the correct order.
>
> Here is the basic scenario
> Servers A,B, and C run the web application CAISI
> Server X runs the integrator software (no users - web services/jms only)
> (and the jms server?)
>
>
> Server A needs to send a message to the integrator. If the internet is down
> and server A cannot contact server X, how does the message get queued into
> the system properly?

So A and X are seperated by the internet right?

If so, one option is to use the failover transport in A so that the
JMS clients auto-reconnect to X when it becomes available - though
this could cause A to hang while X is down....
http://incubator.apache.org/activemq/how-can-i-support-auto-reconnection.html

Another option which removes the blocking of A is to use an embedded
broker inside A, so that the application can keep sending messages
even if there is no connection to X - then things will just spool to
disk locally...
http://incubator.apache.org/activemq/how-do-i-embed-a-broker-inside-a-connection.html

then to move the messages from the broker in A to X when there is
connectivity, use a store-forward network between the brokers...

http://incubator.apache.org/activemq/networks-of-brokers.html

-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message