printCacheDetails does not acquire locks on nodes, so can encounter a ConcurrentModificationException if another thread modifies the node while it's being read.

java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
at java.util.HashMap$EntryIterator.next(HashMap.java:834)
at java.util.HashMap$EntryIterator.next(HashMap.java:832)
at java.util.AbstractMap.toString(AbstractMap.java:485)
at java.lang.String.valueOf(String.java:2826)
at java.lang.StringBuilder.append(StringBuilder.java:115)
at java.util.AbstractMap.toString(AbstractMap.java:490)
at java.lang.String.valueOf(String.java:2826)
at java.lang.StringBuilder.append(StringBuilder.java:115)
at org.jboss.cache.UnversionedNode.printDetailsInMap(UnversionedNode.java:562)
at org.jboss.cache.UnversionedNode.printDetails(UnversionedNode.java:313)
at org.jboss.cache.UnversionedNode.printDetailsInMap(UnversionedNode.java:566)
at org.jboss.cache.UnversionedNode.printDetails(UnversionedNode.java:313)
at org.jboss.cache.UnversionedNode.printDetailsInMap(UnversionedNode.java:566)
at org.jboss.cache.UnversionedNode.printDetails(UnversionedNode.java:313)
at org.jboss.cache.DataContainerImpl.printDetails(DataContainerImpl.java:502)
at org.jboss.cache.util.CachePrinter.printCacheDetails(CachePrinter.java:56)
at org.jboss.cache.jmx.CacheJmxWrapper.printCacheDetails(CacheJmxWrapper.java:141)

There do not currently appear to be any other side effects other than the printCacheDetails call throwing the ConcurrentModificationException.