Look at the thread safety code in org.rhq.core.pluginapi.content.version.PackageVersions and make sure it is correct. I just fixed a couple of glaring issues surrounding the unlocking of the RW lock. But there seems to be other issues that I didn't have time to look at. Look at the access to "data" - sometimes its synchronized, other times not. There is the use of "synchronized" keyword and there is the usage of this RW lock (why both?). The thread safety code here looks haphazard and needs to be peer reviewed (I am not convinced it is 100%correct).
svn rev 2608 was my fix that I allueded to in the summary. but again, there is more to be fixed here I think
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1353
mass move off the qa triage list. These are tasks for dev.
mazz, is this still an issue - what were your findings/results?
master commit fdb272c9ea2544b53a66bb37e99b7f6f9be38487 I fixed what looked to be wrong. This class does not even seem to be used (Eclipse can't find any references to it, other than from its unit test) so this probably isn't important. Nothing to QA. Just close this out as FIXED-CODE CHANGE.
Closing this as per previous comment.