JBOSS 5.1 config properties for clusters

[Sandeep Awasthi]

While configuring jboss clusters, many properties are accessed in MBean configuration using standard ${propertyName} notations. For example
jboss.partition.name:DefaultPartition

<cluster-config>
<partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
</cluster-config>

Where exactly these properties are defined. I have deployed one MBean which depends on ${jboss.partition.name:DefaultPartition} in MBean configuration xml. I get error and does not work. So I removed ${} and used hardcoded like following

<depends>jboss:service=DefaultPartition</depends> instead of <depends>${jboss:service=DefaultPartition}</depends>
it says
DEPLOYMENTS IN ERROR:
Deployment "jboss:service=DefaultPartition" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss:service=DefaultPartition' **

But MBean works ok.

Thanks.

[Jaikiran Pai]

Sandeep Awasthi wrote:While configuring jboss clusters, many properties are accessed in MBean configuration using standard ${propertyName} notations. For example
jboss.partition.name:DefaultPartition

<cluster-config>
<partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
</cluster-config>

Where exactly these properties are defined.

A property of the form ${property.name:DefaulValue} in JBoss, is set to "DefaultValue" if the property.name is not already set. The value after the ":" acts as the default value. So in your example:

${jboss.partition.name:DefaultPartition}

The jboss.partition.name will be set to DefaultPartition if you don't pass the jboss.partition.name as a system property:

-Djboss.partition.name=MyPartition

Sandeep Awasthi wrote:
I have deployed one MBean which depends on ${jboss.partition.name:DefaultPartition} in MBean configuration xml.

An MBean cannot depend on a property value. It can only depend on other MBeans. The < depends> element expects the ObjectName of the other MBean.

[Sandeep Awasthi]

Thanks Jaikiran.

I referred this and one more link which I forgot after searching google.

On the link above I posted, the configuration is mentioned as

 <server> 
	 <!-- This MBean is an example of a clustered singleton --> 
	 <mbean code="org.jboss.ha.examples.HASingletonExample" 
		name=“jboss:service=HASingletonExample"/> 
	 
	 <!-- This HASingletonController manages the cluster Singleton --> 
	 <mbean code="org.jboss.ha.singleton.HASingletonController" 
		name="jboss:service=ExampleHASingletonController"> 
		 
		 <!-- Inject a ref to the HAPartition -->
		 <depends optional-attribute-name="ClusterPartition" proxy-type="attribute">
			 jboss:service=${jboss.partition.name:DefaultPartition}
		 </depends>  
		 <!-- Inject a ref to the service being controlled -->
		 <depends optional-attribute-name="TargetName">
			 jboss:service=HASingletonExample
		 </depends>
		 <!-- Methods to invoke when become master / stop being master -->
		 <attribute name="TargetStartMethod">startSingleton</attribute> 
		 <attribute name="TargetStopMethod">stopSingleton</attribute> 
	 </mbean> 
</server> 

I think it is for older version of JBOSS.

[Bando Perez]

This bastardo problem had me going around in circles for a while so I'll post the solution here:

Add the following

<attribute name="HAPartition"><inject bean="HAPartition"/></attribute>

to your org.jboss.ha.singleton.HASingletonController MBean in your jboss-service.xml or xxx-service.xml

Many online guides for JBoss 5 are wrong in this aspect and give obsolete information, e.g: http://docs.jboss.org/jbossas/docs/Clustering_Guide/5/pdf/Clustering_Guide.pdf [Ch.5, p.64]

A more up to date solution would be to deploy it as a bean instead of a service MBean using a separate jboss-beans.xml, see http://community.jboss.org/thread/64808

Adios