You could use invalidation so only eviction messages are broadcast, but this means that the caches need to be in the same cluster.
Just because they are in different LANs doesn't mean they cannot be clustered - consider using TCP or TCP_NIO, or even the TUNNEL protocol in your cluster configuration instead of UDP. See JGroups docs for more details.
Sorry if i wasn't more clear.
I have these components distributed geografically: management, provider, reseller and each one has its own cache: management-cache, provider-cache, reseller-cache and I have the core of the application separately with its own cache too (core-cache). The core-cache can contain the elements of management- cache, provider-cache or reseller-cache or all together that's why i need some configuration that permit to send a signal to management-cache, provider-cache or reseller-cache when a node has been removed from the core-cache. i was looking information about clustering by region or about cache loader by region and I found this:
Has been implemented this feature in this new version (1.4.1.SP3)?
Exist some configuration that resolve the above issue?
The linked thread pertains to cache loaders. There can be only one cache loader per thread.
What's confusing to me (and probably to others) is why do you need to segregate the data into separate cache instances, and what is the point of copying all the caches' data into one core cache?
If you wanted, though, one approach would be to wrap multiple TcpDelegatingCacheLoader into a single CacheLoader. Then configure your "core cache" to use this cache loader.
You could chain multiple TcpDelegatingCacheLoaders...