Same problem if I use
treeCache.put( Fqn.fromString( "/a/b1/c11" ), "n_c", "v_c" );
One more step.
if I remove from my cache configuration the expiration
<expiration lifespan="60000" maxIdle="20000"/>
The problem doesn't occur.
Thanks for the post. I was having the same issue and removing the the expiration tag solved the issue.
Just wondering how you resolved the issue with eviction after removing this tag. Because the contents I leave in the cache remain until a user remembers to log out. But a lot of times users do not and in that case the contents in the cache do not get timed out.
If you have any ideas do let me know.
In my case I have a curtom eviction policy that have to remove entries basing on application events. Then I created a custom cachelistener that removes entries from cache.