Home/ Questions/Q 6150041
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T19:33:18+00:00

We’d like to use another L2 cache for our big JPA application. We are

  • 0

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).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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.

    • 0