This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Calling Thread.start does not mean that the thread will start executing right at that moment; the JVM must first decide to switch away from the current thread. I'm not sure what all the factors are that go into that decision, but the length of the remaining byte code (very short in this case) may well be a factor.
In general, you should not rely on setting thread priorities for trying to force scheduling decisions; that may not work the way you expect, or not work at all.