Removal listener called multiple times for the same object.

[valmaltsev]

I noticed that when cache is configured with both maximumSize() and expireAfterAccess(), sometimes removal listener called twice for the same object, once with SIZE and once with EXPIRED causes. Is this by design?

[ben-manes]

It should not. Can you provide a unit test that demonstrates the problem? There were some minor bugs fixed in 3.0.4 (#593) if you are on an older release.

[valmaltsev]

We're on 3.0.5. I don't have a unit test right now. It was observed in performance tests of our product. I'll try to reproduce it in a unit test.

[valmaltsev]

I can't come up with a unit test that reproduces the issue. I guess it was caused by a bug in our own code.

[ben-manes]

Thanks for trying!

[ben-manes]

I've been mining the code coverage report for ideas on new test cases and I think that I discovered 3 bugs, two of which are for removal notifications. They don't match with your scenario, though. I'm still iterating through the CI to squash mistakes, as it takes ~2hrs per build due to test volume. You can see this commit for an in-progress iteration and the bug descriptions.