N.B.: This bug apparently appears only fqn dedicated to Hiberante(3.3) collections.
13:55:11,712 DEBUG BaseEvictionAlgorithm:384 - Removing node /com/wuerth/phoenix/Cis/bc/persistent/jpa/ConcreteAccountPeer/assAccount/COLL/com.wuerth.phoenix.Cis.bc.persistent.jpa.ConcreteAccountPeer.assAccount#32770 from eviction queue and attempting eviction
13:55:11,712 DEBUG BaseEvictionAlgorithm:406 - processRemoveNodes(): Can't find node associated with fqn: /com/wuerth/phoenix/Cis/bc/persistent/jpa/ConcreteAccountPeer/assAccount/COLL/com.wuerth.phoenix.Cis.bc.persistent.jpa.ConcreteAccountPeer.assAccount#32770Could have been evicted earlier. Will just continue.
On Hibernate "ENTITY"- nodes i did never experience this bug.
Please report a bug at jira.jboss.org. Thanks!
As Hibernate does not suggest LRU as algorhythm for 2L-cache, I use the LRU.
Where'd you get the impression LRU is not recommended? LRU should be fine for Hibernate 2LC, see http://www.jboss.org/file-access/default/members/jbossclustering/freezone/docs/hibernate-caching/3.3/en-US/html/eviction.html#eviction-overview-policies