Confirm cache is setup correctly in the log files

In order to confirm that cache is setup correctly in the log files, ensure you have the following values set.

Change the priority value parameter to debug in the log4j2.xml file. For example:
Change the priority value parameter to debug in the log4j2.xml file. For example:
<Logger name=" net.sf.ehcache " level="debug" additivity="false">
<AppenderRef ref="NATIVE_CACHE" />
</Logger>
When the cache peers are advertised, a message similar to the following displays:
2013-05-14 22:25:15,287 [Multicast Heartbeat Sender Thread]
DEBUG net.sf.ehcache.distribution.PayloadUtil - Cache peers for this
CacheManager to be advertised: //192.168.1.69:59569/workflowCache|/
/192.168.1.69:59569/specCache__KEY_VERSION_TO_START_VERSION|//192.168.1.69:59569/
ctgViewCache|//192.168.1.69:59569/lookupCache|//192.168.1.69:59569/catalogCache|/
/192.168.1.69:59569/specNameToSpecIdCache|//192.168.1.69:59569/roleCache|/
/192.168.1.69:59569/nodeIdToSpecIdCache|//192.168.1.69:59569/attrGroupCache|/
/192.168.1.69:59569/catalogDefinitionCache|//192.168.1.69:59569/scriptCache|/
/192.168.1.69:59569/specCache__KEY_START_VERSION_TO_VALUE|//192.168.1.69:59569/
specCache__KEY_TO_CURRENT_START_VERSION|//192.168.1.69:59569/wsdlCache|/
/192.168.1.69:59569/accessCache
Note: The IP address must not be 127.0.1.1.
You will see a message similar to the following when a machine is receiving notification from peers in its cluster, in the native_cache.log file:
2013-05-14 22:25:15,287 [Multicast Heartbeat Receiver Thread]
DEBUG net.sf.ehcache.distribution.MulticastKeepaliveHeartbeatReceiver - rmiUrls
received //<IP-address>:<port>/workflowCache|//<IP-address>:<port>/attrGroupCache|/
/<IP-address>:<port>/specCache__KEY_VERSION_TO_START_VERSION|//<IP-address>:<port>/
scriptCache|//<IP-address>:<port>/ctgViewCache|//<IP-address>:<port>/
specCache__KEY_TO_CURRENT_START_VERSION|//<IP-address>:<port>/
specCache__KEY_START_VERSION_TO_VALUE|//<IP-address>:<port>/lookupCache|/
/<IP-address>:<port>/catalogCache|//<IP-address>:<port>/roleCache|/
/<IP-address>:<port>/wsdlCache|//<IP-address>:<port>/accessCache
You will see a message similar to the following if the ehcache is still not working:
2013-05-14 22:25:15,287 [net.sf.ehcache.CacheManager@6d0b6d0b]
DEBUG net.sf.ehcache.util.UpdateChecker - Update check failed:
java.net.SocketTimeoutException: connect timed out