When an item descriptor’s caching mode is set to distributedJMS, all cache invalidation events sent for items of that type use JMS, which persists cache invalidation event messages in the SQL database until delivery is complete. By contrast, Distributed TCP Caching cannot guarantee that all servers receive cache invalidation events. For example, a server might fail to connect to another server, and there is no guarantee that all delayed events are delivered after the connection is reestablished.

Note: Use distributed JMS caching only for items that are infrequently updated, as its performance is much slower than using distributed TCP caching.