CacheInvalidator(3.2.7RC1 jdbc2) complains alot, why?

We keep seeing these warning in our log files.

Quote:
jvm 1 | 11:19:31,671 WARN [CacheInvalidator] removal of 466 rejected for null: the entry could not be found

and

Quote:
jvm 1 | 11:17:13,859 WARN [CacheInvalidator] removal of 1 rejected for TransactionImpl:XidImpl [FormatId=257, GlobalId=scale-server2//10163, BranchQual=]: the entry could not be found

So what is this and how do I get rid of it?

Other things I notice:
1) The invalidator with the null transaction is not referenceing this data. IE. This particular machine has not accessed that table/row (yet). This is the "idle" machine.

2) The invalidator with the defined transaction is shown more than once(some times once, sometimes 3-4 times).

What I think may be happening.
1) The cache is being invalidation by the InvalidationManager on the global cache that has not been set.
2) On commit of a modified row, multiple removes aer being called on the same transaction. If only one call is done, it works. But if multiple removes for the same transaction is done, this warning appears.

I can throw into debugger to confirm both scenarios.