JDK errors in Multiprocessor with weak memory model

Question

When reading this article to understand some of the Double-check locking problems :
I got surprised by point 4. Appart the String example, it means that any build immutable object like build during a single-thread phase have no garanty later in multi-thread phase to be read a in fully initialized state.
So I checked implentation of some JDK classes to how is managed some static field. The first I checked (in JDK 1.4.1) is Locale.getDefaultLocale().
LOL in fact it's a case of double-check locking.
The internal comment is:
// do not synchronize this method - see 4071298
// it's OK if more than one default locale happens to be created
What is 4071298?
Secondly, setting two times the default locale isn't the problem with Double-check locking.
So any explanation this is ok? Or it's just a JDK example of wrong Double-check locking?

Answer 1

When talking about languages that run in a virtual machine, concern yourself only with the virtual machine, because that is where your code will be executed.
When talking about code that runs in a physical machine, concern yourself with the physical machine (CPU/RAM/etc.) because that is where your code will be executed.
In summary, concern yourself with the memory model of the machine that will run your code. Which is the Java VM in this case.