See case 269460 for details. The original SQL which was identified in the case as a bottleneck is no longer used in the main code base so the immediate problem should have been addressed. However I think there is the potential for similar problems with the query ResourceError.QUERY_FIND_BY_RESOURCE_ID_AND_ERROR_TYPE RHQ-1671 was raised to reduce the number of unnecessary calls to this query, but it turns out that code path is no longer being executed either, more good news. However we should investigate and see if there are any other usages of this query that could result in it getting executed a large number of times.
rev3322 - add index to resourceId column of ResourceError object, which all queries are currently keyed off of;
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1713