[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Simplifying the JBM beans deployment

[timfox]

I came across an issue when writing an automatic failover example using JMS.

Currently when we start a backup node, it doesn't actually activate until its live node has contacted it and told it to activate, this is because the live node needs to send it it's node id since live and backup must have the same node id.

However with the way beans are currently created in the jbm-standalone-beans.xml file. The deployers are created and injected and everything is started, but this means the deployers start deploying stuff on the backup node before the live node has activated it, so it fails.

I'm considering simplifying our beans file and removing most of the beans, so we really just have MessagingServerBean and a JMSServerBean. All the deployers, configuration etc can just be internal objects of this beans and do not have to be exposed in the beans file.

We can then control the dependent beans lifecycles directly from inside MessagingServerBean/JMSServerBean.

Comments please?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224310#4224310

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224310