Description of problem:
It appears that the "partitionName" attribute for EAP 5.x is not always reported correctly. This blocks customers from using group definitions to automatically create compatible groups to manage their jboss clusters. If you do:
It will not find anything
Steps to Reproduce:
1. Start some EAP 5.0.1 version with the "production" configuration
2. Inventory that instance
3. Navigate to Monitor > Traits
The "Partition Name" attribute is empty / not reported
The "Partition Name" attribute should be filled in
I verified that the property [MCBean|ServerConfig|*|partitionName] did indeed have a null value for an EAP 5.0.1 instance running the "production" config. But I noticed that the property [MCBean|HAPartition|*|partitionName] was set correctly to the cluster partition name. So I updated the as-5 plugin to fallback to using the 2nd property if the 1st property does not exist or has a null value.
Commit abc1adc - pushed to release-3.0.0 branch.
Note, I also changed the display name of the trait from "Partition Name" to "Cluster Partition Name".
Verified on JON 2.4 GA_QA build#47
Started EAP 5.0.1 with the "production" configuration. Navigated to Monitor > Traits tab. It displays the trait "Cluster Partition Name" with value 'DefaultPartition'.
I've created the following JIRA issue for the EAP issue with the 'partitionName' managed property having a null value:
Mass-closure of verified bugs against JON.
This is already fixed in the RHQ branch used for the EAP 5.x admin-console.