Avoiding Message Broker from stopping when ESB goes down

[sakkew]

I understand that FUSE ESB uses FUSE Message Broker as its underlying messaging infrastructure.

What are the alternatives if I want to prevent FUSE Message Broker of stopping if Fuse ESB goes down or is stopped?

One alternative is to remove the included broker and install FUSE Message Broker separately. Is this a good approach, or are there better alternatives?

best regards,

Sakke Wiik

[exto]

I also have the same question, I figure deploying ActiveMQ in a cluster will avoid most issues since if one ServiceMix instance goes down (perhaps OOM) everything will still work properly with the secondary broker.

I am worried about other bundles/services perhaps taking up too much memory or resources and inadvertently affecting the performance/stability of the messaging layer.  Does anyone else have any best practices in this regard?