Hello all :)

[Engineeringserver.com]

I'm a Java developer and i stumbled on this site, hope to have a great time here :)

[Nicholas Jordan]

I'm a Java developer and i stumbled on this site, hope to have a great time here :)

Wait till you meet Pat.

[Niveditha]

Hi,
Welcome to our forum... :)
Hope to see you around....

[Engineeringserver.com]

Thanks, all. Hope to contribute here as well :)

[Nicholas Jordan]

Show how the usual double-check lock trick of a private constructor and the only private variable is a static instance of the helper class, which in turn calls the private constructor can be defeated as a design paradigm by legacy code buried in the compiler. In the problem, dameon thread doing caching raises an IllegalAccessException.

Error message:

// This is a standard stack trace in Java, with some 
// editing due to the fact that it is someone else's code

java.lang.IllegalAccessException:
 Object can not access a member of class ( someone else's code ) 
with  modifiers "private"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) 
at java.lang.Class.newInstance0(Class.java:349)

There are no calls to the constructor and no explicit calls to newInstance() on the class at the point where the exception is raised. Appears to be a section of code written by one who is well trained, thus is likely to be traceable to an intersection of interview question level of work contradistincted to bench practices in a real shop.

My answer: The "Double-Checked Locking is Broken" Declaration

See: An Introduction to Real-Time Java Technology: Part 1, The Real-Time Specification for Java (JSR 1) to get an overview of the engineering needed.

The problem likely involves some techniques in Reflection that should be retired to legacy code as insufficient for today's parallel computing paradigm or over-eager optimization by the compiler.

[Eranga]

I'm a Java developer and i stumbled on this site, hope to have a great time here :)

Hi,

Welcome to our community. :)

[CaptainMorgan]

Nick, please refrain from this type of behavior in the introductions. I know it was probably meant in good faith, but such posts are meant for elsewhere. :)

Thanks pal.

Engineeringserver:
Welcome!

See you around!

[Nicholas Jordan]

I understand your admonition. Poster is an engineer, special case. I accept your directions.