Java Development through Proposed Revisions to the Java Memory Model

Quick Inquiry


Client Speaks

Client Speaks - Testimonials for Aegis Software
You Are @ >> Home >> Articles >> Java Development through Proposed Revisions to the Java Memory Model

Looking at constrains, problems and accidental consequences, not being addressed by the JDK5, open source Java supporters have shown an interest in modernizing the Java memory model, which is formally un-updated since past nine years. A JDK Enhancement Proposal (JEP), Number 188, issued in January, proposes the guidelines on shared-memory concurrency efforts which influence testing, JVM support, tools and Java SE (Standard Edition).

We are expecting that the multicore processors will get the support from improved concurrency. Memory models fundamentally postulate every Java thread actions and synchronizations. The updated model basically presents the arithmetically articulated instructions on the interaction procedure of threads with memory.

Going on with the JEP documents, creating and upholding topographies and mechanisms which operate in harmony are among the chief yet challenging issues in engineering parallel and concurrent platforms. Furthermore, unintended consequences, errors and specification limitations become ostensible over time. Software tools and components, programming techniques and new hardware platforms appear to escape prevailing boundaries.

The efforts of JPE can lead to numerous bug fixes, adjustments, and enhancements across the platform. Additionally, it can be used to develop advance programming tools, support new concurrency features, improve implementations and revise the specification of JAVA language.

The proposal depicts upgraded reinforcement of the original memory model, wherein this advancement would be more explicable and mechanically checkable. Moreover, implementation guidance and C11/C++ compatibility addresses the JVM coverage. The reframed model will be pliable to use by development tools which checks for errors (security maintenance and race conditions across concurrent execution) analytically.

For further information, mail us at

do not copy