For all the details on the changes to JBAS that broke things, see https://jira.jboss.org/browse/JBAS-8263.
I believe the fix for this is simply adding common/lib/jboss-as-profileservice.jar and lib/jboss-profileservice-spi.jar to the list of client jars in org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent. However, because the PC's plugin connection classloader infrastructure blows up when jars that don't exist are added to the connection classloader, we need to either only add these two jars to the list of client jars if they exist or only add them if the discovered AS instance's version is 6.0 M4.
In my testing, adding these two jars does allow the as5 plugin to successfully connect to an AS6 M4 instance (i.e. the resource component starts successfully).
Note, it's not the PC's plugin connection classloader infrastructure that blows up if one of the client jars doesn't exist - it's the as5 plugin itself. We should probably change it so it just logs a warning rather than blowing up, since, as this issue demonstrates, the exact set of required jars varies from version to version.
Needs to get this into Master, not the 2.4 release branch
This has been fixed in master via commit 727c897. We can now discover and manage AS6 M4.
Once AS6 CR1 is released in November, we should test again and make sure everything still works.
Verified on build#158 (Version: 4.1.0-SNAPSHOT Build Number: c1539ab)
Downloaded jboss-184.108.40.20601110-CR1. Started the server and discovered it successfully. It is shown green. Please refer the attached screenshot.
Verified that monitoring, importing a test script works for the resource.
Marking as verified.
Created attachment 510028 [details]