The approach to revision garbage collection taken in
OAK-2192 assumes that long running background sessions call refresh once they become active again. Incidentally this is true as such background sessions usually are admin sessions and those are always auto-refreshed on access (see OAK-88, OAK-803, and OAK-960). However as soon as we move away from admin sessions this might not be true any more and we might start seeing SegmentNotFoundException s unless the user explicitly refreshes the session.
To prevent this we should make all sessions auto refresh once revision gc runs.