EntryListener.entryAdded() not called after IMap.evict() followed by IMap.get()

[patriziomunzi]

If I call the evict method on a key and then the get method on the same key the listener entryAdded method does not fire.

this.instance.getMap(cacheName).evict(id);
this.instance.getMap(cacheName).get(id);

=====

    private class CacheEntryListener implements EntryListener<Object, Object> {
        @Override
        public void entryUpdated(EntryEvent<Object, Object> event) {
            if(_log.isDebugEnabled()) {
                _log.debug(cacheName + " - key: " + event.getKey() + " updated");
            }
        }
        @Override
        public void entryRemoved(EntryEvent<Object, Object> event) {
            if(_log.isDebugEnabled()) {
                _log.debug(cacheName + " - key: " + event.getKey() + " remove");
            }
        }
        @Override
        public void entryEvicted(EntryEvent<Object, Object> event) {
            if(_log.isDebugEnabled()) {
                _log.debug(cacheName + " - key: " + event.getKey() + " remove");
            }
        }
        @Override
        public void entryAdded(EntryEvent<Object, Object> event) {
            if(_log.isDebugEnabled()) {
                _log.debug(cacheName + " - key: " + event.getKey() + " added");
            }
        }
    }

[enesakar]

Not sure if the entryAdded for the second time is needed.
It is not the same situation with the first time add.
Think you take an action when an entry is added. Then after eviction, you will take this action again and again, although it is not added for first time.

[patriziomunzi]

I see your point, but I what if I want to get notified if a entry IS in the cache.

Maybe the update method could be fired.

Patrizio Munzi
email: patrizio.munzi@gmail.com
mobile: +39 393 7195164
skype: patrizio.munzi

On 10 Jan 2014, at 09:31, Enes Akar notifications@github.com wrote:

Not sure if the entryAdded for the second time is needed.
It is not the same situation with the first time add.
Think you take an action when an entry is added. Then after eviction, you will take this action again and again, although it is not added for first time.

—
Reply to this email directly or view it on GitHub.

[noctarius]

Well in your case it is something like an update since the real value still exists but is just evicted so an add should be an update.

[patriziomunzi]

yes exactly, firing an update could work for me. Is it something you can add?

On 10 Jan 2014, at 09:59, Christoph Engelbert notifications@github.com wrote:

Well in your case it is something like an update since the real value still exists but is just evicted so an add should be an update.

—
Reply to this email directly or view it on GitHub.

[noctarius]

I think not in a few minutes but it should answer someone with deeper knowledge of the eviction process.

[patriziomunzi]

Ok, waiting for your feedback, thnx

On 10 Jan 2014, at 10:06, Christoph Engelbert notifications@github.com wrote:

I think not in a few minutes but it should answer someone with deeper knowledge of the eviction process.

—
Reply to this email directly or view it on GitHub.

[ajermakovics]

Another option is to have another event type - Loaded, when something is loaded from a map store. That way you'd be able to distinguish between all the events

• Evicted <-> Loaded
• Added <-> Removed

[ahmetmircik]

related one #2407