Actually the instance cap can't be set to be empty or null through the UI, so there is not really a way to define an unlimited cap, except by some high number. Nevertheless, this does not make the argument for the unlimited timer value being other than zero. As Kevin points out the convention seems to be a zero value for a timer would be unlimited and this is the way I prefer it be handled. The problem with Integer.MAX_VALUE is that it's not obvious that it's a default value, with a zero you know it's a default.