Redundant cluster configuration property

[jbertram]

I recently discovered that the default value for the "Clustered" attribute of the jboss.messaging:service=PostOffice MBean in all the <JBOSS_HOME>/docs/examples/jms/*-persistence-service.xml files changed from "true" to "false" from JBM 1.4.0.SP3_CP03 to 1.4.0.SP3.CP04 (https://jira.jboss.org/jira/browse/JBMESSAGING-1422).

This got me thinking about why there is a "Clustered" attribute for the post-office at all. Would it not be better to programmatically activate post-office clustering based on the presence of a clustered destination in destinations-service.xml? What does a clustered post-office buy you if no destinations are clustered? Also, what happens with a clustered destination if the post-office isn't clustered? These last two questions would be moot if post-office clustering were enabled programmatically.

Thoughts?

[clebert.suconic]

I think this would be confusing.

Say.. the PostOffice stays stand alone in production for 2 weeks till someone accidentally drops a file with a clustered Queue. We would need to transform the PostOffice into a clustered one, from opening the JChannels to filling all the states. (Without also considering other implications on the data already existent on the DB).


But even if that was not an issue, it would require some development (mainly testing) on the PostOffice. IMO it would be better to use that energy towards 2.0.

[timfox]

+1 We're not doing any new features on the 1.x series unless there is very strong pressure from paying customers.

All new stuff is in JBM 2.0, 1.x is bug fixes only