When using a cache configured with expiration in remote JCache implementation, expiration events were not handled in clustered environment on cache <literal>c1</literal>, if the insertion of an entry was performed by cache <literal>c2</literal>. As a consequence, cache entry listener registered on cache <literal>c1</literal> was not notified of the expiration event. The issue is resolved as of Red Hat JBoss Data Grid 6.6.0, and cache entry listeners receive expiration events correctly in clustered environment.