When the RHQ Server gets clobbered with lots of agent registration requests (such as when you start a large amounts of agents at the same time), the server bogs down. This is because, not only is there lots of registrations coming, but soon, tons of inventory reports will also be coming. I'm not sure if we should try to some how throttle these new agents. Perhaps add a new concurrency limit classification for registration messages? Or something similar that slows down the influx of new agents.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1121
mass add of key word FutureFeature to help track
mazz, is this still an issue?
i would close this. we've not seen any problems with the server unable to handle a flood of registration requests. we do throttle other things like inventory reports.