L2 cache overflow behaviour configuration

Description

Cache Overflow makes single select query call to DB.
EhCache.xml:
<cache name="Country1"
maxEntriesLocalHeap="200"
eternal="false"
overflowToDisk="false"
diskPersistent="false"
timeToLiveSeconds="800"
/>

Total Row count of table Country=229

.java file fires same simple SELECT query for 10times

1st query goes to DB and get cached.
2nd query checks cache and here in this case cache-limit reached(200),i.e. cache overflow happened ,
single select query fired per row(output attached).

Expected behaviour:
There should be some configuration to control the no. of queries / or it should fire the single query for non-cached elements.
Tried batch-size option but has limitation of only 1000 keys in 'IN' Clause

Environment

hibernate 3.3.1ga, ehcache 2.5,oracle 10g

Activity

Show:
Brett Meyer
April 7, 2014, 5:45 PM

In an effort to clean up, in bulk, tickets that are most likely out of date, we're transitioning all ORM 3 tickets to an "Awaiting Test Case" state. Please see http://in.relation.to/Bloggers/HibernateORMJIRAPoliciesAndCleanUpTactics for more information.

If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.

Thank you!

Brett Meyer
July 8, 2014, 3:11 PM

Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!

Rejected

Assignee

Unassigned

Reporter

girish

Fix versions

None

Labels

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Affects versions

Priority

Major