EclipseLink/Examples/JPA/Ehcache

Integrating EclipseLink with Terracotta Network Attached Memory

DISCLAIMER: This page reflects investigation into how EclipseLink users can integrate with Terracotta ehcache. It does NOT imply any formal certification that EclipseLink supports the Terracotta API at this time.

Summary

• This document in progress as of 20100326 details how to integrate EclipseLink (via a TIM - Terracotta Integration Module) into the Terracotta Inc. Network Attached Memory (Distributed JVM-aware transparent Cache).
• The goal of this investigation is to define and publish a procedure on using EclipseLink as the JPA provider in a distributed memory application based on Terracotta Inc. Caching API.
• The motivation of this work is in learning and leveraging 'ehcache from Terracotta Inc. and details/issues of the technical space surrounding distributing caching in general as described in the paper on the new Java5 memory model by William Pugh - The Java Memory Model.

Setup

Development Environment

• We will be using a cluster of 3 identical machines (Low power P4-630 CPU's) running 32 bit versions of the SUN JDK 1.6.0_18

References

• Terracotta Inc. Discussion Forum
• Terracotta forum post - integration request 20080812 3rd level Cache
• Terracotta forum post - integration request 20090518 TIM
• Terracotta forum post - integration request 20090614 Spring EclipseLink
• Terracotta forum post - integration request 20090616 Custom ClassLoader
• Eclipselink coordinated cache integration - 20081221 New TIM (Terracotta Integration Module)
• See Chapter 6 p.131 of "Terracotta - Cluster the JVM for Spring, Hibernate and POJO Scalability" - available from Apress.