how to use another implementation for JPA 2 level 2 cache?

Question

We'd like to use another L2 cache for our big JPA application. We are trying to achieve a shared cache between multiple servers.

We use Eclipselink as JPA implementation, and some legacy codes uses internal Eclipselink API's, so switching is not an option.

Coherence/Toplink Grid seems too expensive (4000$/cpu?).

Is there a way we could plug another cache implementation? Is something specified in JPA 2 (I can't find anything in the specs, but maybe I just misread it)? Proprietary (=Eclipselink specific) solutions are ok, as long as they are somewhat documented or simple enough (we don't want that to break).

score 1 · Accepted Answer · answered Jul 18 '11 at 11:13

1

Is there a way we could plug another cache implementation?

Did you investigate the use of the EclipseLink shared object cache that comes with EclipseLink? Going by the description, the shared object cache is not confined to a single EntityManager alone, and is available across the lifecycles of several Entity managers, i.e. across several transactions. It is of course, constrained to the lifecycle of an EntityManagerFactory, which may be as live as long as the application is running in the container.

The EclipseLink shared object cache is different from Oracle Coherence, and I believe it is not licensed and packaged separately, thereby making it available on all containers.

answered Jul 18 '11 at 11:13

Vineet Reynolds

76,006
17
150
174

That's the default cache implementation. It's not shared between servers. I'd like to plug another cache implementation, and I currently can't find a way to do it. – ymajoros Jul 18 '11 at 11:24
1

Well, it supports cache coordination so you can coordinate server caches. – Vineet Reynolds Jul 18 '11 at 11:32
Vineet, do you know if I can use it across weblogic clusters, multiple servers? – Kalpesh Soni Jan 07 '15 at 19:31

Tom Anderson · Answer 2 · 2011-07-18T13:17:57.050

JPA does not specify a pluggable cache interface. I don't know if it ever will, but if it does, my bet is that it won't be until after the resurrected JSR-107 finishes defining a standard API to object caches, which JPA would then be able to use. It might also have to wait for JSR 347, which is defining another cache interface, whose relationship to JCache is somewhat unclear (there is open factional warfare between and within the groups, with some members of the 107 expert group trying to declare 347 an independent republic, and invade Mexico).

So, until then, you're at the mercy of your provider's cache interface. I am not an EclipseLink expert, but last time i looked, i couldn't see a pluggable second-level cache interface. In fact, i think only Hibernate and, of course, DataNucleus, have them.

Still, there is no way for us to change to Hibernate or DataNucleus. — ymajoros, Jul 18 '11 at 13:14

score 1 · Answer 3 · answered Jul 18 '11 at 19:27

1

Most cache implementations are not distributed (other than Coherence), just local. EclipseLink already supports a share cache and cache coordination for caching in a cluster.

What cache do you intent to use, and what benefit do you intend to get from it?

EclipseLink does support integration with 3rd party caches, this API was created for the Coherence integration, although Coherence is the only cache that currently provides an integration.

answered Jul 18 '11 at 19:27

James

17,965
11
91
146

Looks like ehcache, for one, is distributed. I'm still trying to decide if I should use something like that or just Eclipselink cache coordination. – ymajoros Jul 19 '11 at 07:53
I guess you're talking about CacheInterceptor Tom Ware was referring to on EL mailing list? – ymajoros Jul 19 '11 at 08:52
can eclipselink do cache coordination across weblogic clusters? – Kalpesh Soni Jan 07 '15 at 19:32

how to use another implementation for JPA 2 level 2 cache?

3 Answers3