RemovalListener problem

[andre.rigon]

Hi folks,

I'm using a RemovalListener, but it does not get called. The entries
from the cache are removed, but
my removel logic never gets invoked. Any help?

I'm using a cache configured as follows:

CacheBuilder.newBuilder().expireAfterAccess(duration,
unit).removalListener(fileDeleteRemovalListener())
.build();

and this is my RemovalListener:

private RemovalListener<String, String> fileDeleteRemovalListener() {
return new RemovalListener<String, String>() {

@Override
public void onRemoval(RemovalNotification<String, String> not) {

try {
FileUtils.forceDelete(new File(not.getValue()));
} catch (IOException e) {
Log.error("could not delete file " + not.getValue(), e);
}
}
};
}

Thanks!

[Charles Fry]

Did you add logging to onRemoval to see if it was getting called?

--
guava-...@googlegroups.com
Project site: http://guava-libraries.googlecode.com
This group: http://groups.google.com/group/guava-discuss

This list is for general discussion.
To report an issue: http://code.google.com/p/guava-libraries/issues/entry
To get help: http://stackoverflow.com/questions/ask (use the tag "guava")

[André Gonçalves]

Hello Charles, thanks for the answer.

I tried to log, bot nothing happens. It doesnt get called at all.

[Kevin Bourrillion]

It would help to attach a complete compilable and runnable program (simple and self-contained) -- thanks!

--
Kevin Bourrillion @ Google

Java Core Libraries Team
http://guava-libraries.googlecode.com

[Charles Fry]

If this is in a test case you might need to call Cache.cleanUp(). 

[André Gonçalves]

Charles,

I put an cache.cleanUp(); after a .put() call, and stoped the debug and waited until the timeout ends.
That way, the listener fired up.
Why this behavior?

thanks in advance,

Andre

2012/3/9 Charles Fry <f...@google.com>

[Charles Fry]

As explained in the CacheBuilder javadoc:

"If expireAfterWrite or expireAfterAccess is requested entries may be evicted on each cache modification, on occasional cache accesses, or on calls to Cache.cleanUp(). Expired entries may be counted inCache.size(), but will never be visible to read or write operations."

The point is that we don't run any background cleanup threads, so need to hook onto user requests. And for scalability reasons we do that on a per-segment basis.

In a production environment it will all just work out. You just need to do extra stuff (like calling cleanUp explicitly) when you're writing tests.

Charles

[André Gonçalves]

Thanks for the help!

2012/3/9 Charles Fry <f...@google.com>