The fix for bug 847014 introduced bounded, predictable expansion for resource tree child nodes. This means that if a node in a tree (a parent resource) has perhaps thousands of children, that we protect against pulling an unlimited amount of data into the tree. We have the same issue when a user navigates directly to a resource that may have thousands of siblings (via a link or bookmark). We need to protect the tree from an unbounded fetch.
master commit 414ccdf3fd964dc6d64abe511ec02f4e9170aa40 Apply the new ResourceManager.findResourcesByCriteriaBounded() method to getResourceLineageAndSiblings() in order to similarly bound the initial tree building fetch. Currently getResourceLineageAndSiblings() will use the defaults applied to findResourcesByCriteriaBounded(), although we may find that providing separate overrides will be useful. Test Notes: The initial fetch will no longer be unbounded so it's possible that users that previously did not see any truncation may not see it. But it's unlikely as by default we still pull up to 1000 siblings. Testing could be easier by setting overrides to smaller numbers (see bug 847014 for more on how to do that) testing may be easier. In all cases the resource being navigated to should show up in the tree, even if it is at the bottom of many siblings.
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.