Greater Quebec Software Symposium - Apr. 20 - 22, 2007

The Java Memory Model

Fri, 09 Mar 2007 18:00:07 CST

Greater Quebec Software Symposium - Session Information

The Java Memory Model
by Brian Goetz

Java was the first mainstream programming language to incorporate a formal, cross-platform memory model, which is what enabled the development of write-once, run-anywhere concurrent classes. It is the Java Memory model that defines the semantics of synchronized, volatile, and final.

However, because the most commonly used processors (Intel and Sparc) offer stronger memory models than is required by the JMM, many developers frequently use synchronization and volatile incorrectly, but have been insulated from failure by the stronger memory guarantees offered by the processor architecture they happen to be deploying on. (The infamous double checked locking idiom is an example of this sort of error.)

JDK 5.0 incorporates JSR-133, a revision of the Java Memory Model, which refines the semantics of synchronization, volatile variables, and final fields. Additionally, the new JMM provides a new safety guarantee initialization safety that allows immutable objects to be shared among threads without synchronization, if certain requirements are met. This talk describes the updated Java Memory Model for programmers who are familiar with the multithreading primitives in Java (synchronized and volatile.)

Understanding the Java Memory model is key to using the core concurrency primitives (synchronized and volatile) to develop thread-safe, efficient concurrent classes. Well cover what a memory model is, what synchronization really means, what was broken about the original Java Memory Model, and how the memory model changed in JDK 5.0.

Greater Quebec Software Symposium - Apr. 20 - 22, 2007

Thu, 01 Mar 2007 09:00:00 CST

No Fluff Just Stuff is pleased to announce the Greater Quebec Software Symposium, Apr. 20 - 22, 2007.

Catch these Featured Sessions

Effective Concurrent Java
by Brian Goetz

The Java programming language has turned a generation of applications programmers into concurrent programmers through its direct support of multithreading. However, the Java concurrency primitives are just that: primitive. From them you can build many concurrency utilities, but doing so takes great care as concurrent programming poses many traps for the unwary.

Complex Builds with Ant
by Brian Sam-Bodden

Ant has revolutionized the way we build applications in Java and it has become a de facto standard in the Java world. As applications grow in complexity some developers are finding themselves dealing with ever growing and complex builds. Complex builds have to deal with Multiple Operating System, multiple Application Servers, multiple APIs and multiple stages of development.

Abusing Maven For Fun and Profit : (Near) Zero-Admin Deployments
by Brian Sletten

Ok, I can't promise you profit, but hopefully you'll have fun. Maven 2 introduces a number of new features (including that performance feature) that make it a swell project management tool for development. Come hear about how we can abuse Maven to manage distributed deployment scenarios before the Modules JSR is done.

Greater Quebec Software Symposium - Apr. 20 - 22, 2007

Wed, 14 Feb 2007 15:00:00 CST

No Fluff Just Stuff is pleased to announce the Greater Quebec Software Symposium, Apr. 20 - 22, 2007.

Catch these Featured Sessions

Effective Concurrent Java
by Brian Goetz

Business Rules Engines in Java and J2EE- An Introduction to the Drools Rules Engine
by Brian Sam-Bodden

Software development is expensive, when business rules are hard-coded in your applications source code, changes and additions to those rules translate to wasted time and money. Good object-oriented, component-based approaches can alleviate the burden of keeping up with changes in the business world but they still require that expert knowledge of the changes be passed from the decision makers to the business analysts and finally to programmers that need to implement these changes. Business Rule Engines and Business Rule Languages are based on the basic premise of separation of concerns by empowering business domain experts to express the rules of business in a way that it is directly usable by applications.

Abusing Maven For Fun and Profit : (Near) Zero-Admin Deployments
by Brian Sletten