UP-3717 - session timeout

I don't recall if I've commented on this before, but FWIW I'm not a big fan of using base-class loggers in subclasses as a general rule.  It does present logical flow in the logs better in some ways (you see all of what a class hierarchy is doing as one logical class), but it makes it harder to find the log statement when you see something and you want to track down the source of that line (recursive searches through base classes) or get some detailed logging without involving the base classes.  It also makes it a bit harder to find out if you have access to a logger (though the IDE makes it a bit easier since we usually use log or logger as the name).  Since almost all of our classes are non-final public classes almost all of the loggers would be protected using this approach.  I don't want to get into one of those crazy religious wars, but IMHO each class should specify it's own logger (true, tiny bit more memory consumption) or we just leave it up to developer discretion.  Enough said.