After trying to add the constructors, I've seen that could be almost impossible since it is another "long" attribute, as many others, and therefore very difficult to add "all" type of constructors. So, even if I add some constructors that contains this (that's fine to do it already), I will have to let the setter method.
However when I read the rest of the code, many other variables are setup using the very same approach: setters that could be called once, but not supposely by a lot of threads (so no real concurrency issue), and there is no volatile keywords set. For instance: checkInterval, writeLimit and readLimit.

2 options then:
a) add volatile too all of them (even if I feel like it is not really needed, but I understand the "possible" concern)
b) let them as they are, and so the maxTime

WDYT?