Large SiteStats reports can cause out of memory conditions

Bring up a Sakai app server with a heap size of 8G (or smaller) Create a site Outside Sakai, populate the SST_RESOURCES table with 2 million rows with the site id of the site created above (in our case, almost all the events were from anonymous users, as the resources were flagged public) In Sakai in the site, go to Site Stats / Reports / Add / What Activity = Resources / When Period = All / Generate Report The report definition has a "Number of results" selector which is unchecked by default, and the solution is probably to impose an absolute maximum value, but not sure where exactly (maybe lower-level, in the service).