I probably shouldn't respond any further on this thread. But I feel like most people are focusing on each line of my post independently of the others and thus taking my point out of context. So I will state and then be done.
The model of the disruptor is a very good example of how to implement a non-locking threading algorithm in Java. Personally I made a completely different version of it that also combines in with a work stealing queue. Well, by "made" I mean "is mostly done and currently testing and tweaking".
The reason I have faith in this pattern is because it is used in successful game engines already(Thanks id Software for sharing). id uses a similar pattern to the disruptor--
--however, this is in C++ so that's where the source to the disruptor comes in. Personally, I think if taken in context, these two pieces of information are gold as far as Java gaming is concerned.