steps to reproduce: * start up 10 secured jboss-as instances (pincipal/credentials should be the same for all of them) * force an agent discovery if necessary * import all 10 instances (you'll notice they are red) * add all 10 to a compatible group * go to the inventory tab of this group, click edit under "connection properties" ** add the necessary principal/credentials for your servers, click OK you'll notice that the first or second updates complete in 30-45 seconds, but after that the rest of them seem to take about 10 minutes each. even though they will look successful, this is somewhat of a false positive. the update itself completely successfully, but the post-processing hook to execute a runtime discovery timed out. so, you'll see most (if not all) of the remaining updates take 10 minutes. these updates are very fast, and should be able to complete within a few minutes.
rev848: 1.0.0-ga-cp branch rev849: trunk remove agent-side deadlock by executing a deferred runtime discovery request after a plugin configuration update; fix the method that schedules group plugin configuration updates to prevent hibernate exceptions from happening due to clear/flush methods; add a delay in the aggregate plugin configuration update job so that it doesn't try to execute the job before the aggregate update is committed; -- following the testing procedures listed in the case, you'll now see that the plugin configurations can be updated against the jbas group of size 10 in approx 3-4 seconds, instead of minutes/hours.
this was very well tested already since this went out as a patch for a customer several weeks ago. tested agent on win with 10 jboss, and tested agent on linux with 10 jboss. server always ran on windows. confirmed that timings are dramatically reduced over what they used to be.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-503