Operation After Transaction Commit Triggers Cache Get Even With Cache Disabled (Doc ID 1520404.1)

Last updated on SEPTEMBER 10, 2014

Applies to:

Oracle TopLink - Version 11.1.1.4.0 to 11.1.1.5.0 [Release Oracle11g]
Information in this document applies to any platform.

Symptoms

Previously TopLink Grid was enabled. Now it is shut it back down by setting eclipselink.cache.shared.default to false.

However, it was found that cache get is still issued if an entityManager.find() or relationship navigation is done after committing transaction.

This blocks the shutdown of Coherence cache to free system resources.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms