The only way you will loose an embedded broker is if you loose the entire JVM - so your application will go down too. If you are running multiple JVMs of your application and you want a hot standby then use Master/Slave.
On 6/11/06, ENP <[EMAIL PROTECTED]> wrote:
Hi, I need to use some advanced message processing inside JMS server: in some cases some messages must be created on one message arriving or instead of it. Simplest way to do it (without complex J2EE server with MDB) is embedding AMQ in my simple application which will be responsible for listening messages such as AMQ web console and reading them or creating another messages. But how can I provide fault tolerance in this case? Can I use two instances of my application with embedded AMQ in Master/Slave configuration? Can I use network of brokers? What will be happen with my custom message processing? -- View this message in context: http://www.nabble.com/Embedded-broker-fault-tolerance-t1770742.html#a4819396 Sent from the ActiveMQ - User forum at Nabble.com.
-- James ------- http://radio.weblogs.com/0112098/
