To resolve the problems described in
and DS-3656 the handling of the hibernate cache was changed (see DSPR#1824). As the changes were introduced into a minor version of DSpace (6.2) we decided to uncache rather sensitively as we did not wanted to introduce new bugs as result from too aggressive uncaching. DS-3648
Whenever an item gets loaded, its submitter gets cached. Whenever an item is removed from the cache its submitter isn't as it could be the EPerson that is running the current session (and loaded as context.currentUser). For huge batch processes this may result in a lot of EPersons not being uncached, which we should change. This change should be introduced into a major version of DSpace as new major versions have to succeed in a real testathron.