activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ttmdev <>
Subject Re: Is ActiveMQ suitable for this Store-And-Forward scenario?
Date Thu, 25 Oct 2007 21:30:10 GMT

Yes, ActiveMQ will meet your requirements. You can have the ActiveMQ message
broker, on your local client machine, persist the XML messages so that when
the network is available it can forward the messages on to the ActiveMQ
broker that you have deployed on the server machine. 

If your client application is somewhat transitory, then you may want to
elect not to use an embedded broker and instead deploy a standalone or
daemon-like broker on your client machine. Thus you are assured that the
persisted messages are forwarded immediately upon the network becoming


azbel wrote:
> Good afternoon.
> I'm currently evaluating existing JMS Servers in order to fulfill the
> following requirement:
> A Java client application must send XML messages to JMS on the application
> server, but the network is not available most of the time. XML messages
> must be persisted in the local client machine and be forwarded when the
> connection is available. I suppose that configuring an embedded broker
> with ActiveMQ would be the solution since it will persist the messages,
> but only if it provides the required funcionality of sending the message
> when the network is available again.
> Are my assumptions correct? Does ActiveMQ fulfill the requirement?
> Thanks in advance.

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message