The following query configuration throws "The result set is closed." exception on the first call of "Iterator.next()" for the returned Collection:
When such a query is not executed in a transaction by default all the returned results are cached upfront and aside consuming lots of memory looks like might get garbage collected if iteration takes a long time. This leads to another "The result set is closed." exception once underlying ScrollableQueryResult,getObjectForIndex() is called.