Allow cache configuration changes on-the-fly if possible for an attribute

Caches which are created by using the server administration interface are stored internally and the configuration can not be changed by edit the infinispan.xml.

For such caches it should be possible to change attributes which directly have an effect to a running cluster.

Such attributes are

• clustering.remote-timeout
• expiration.interval
• expiration.lifespan
• expiration.max-idle
• memory.max-count
• memory.max-size
• jmx-statistics.statistics
• locking.acquire-timeout
• transaction.single-phase-auto-commit
• transaction.stop-timeout

These changes will be applied cluster-wide and persisted.
 

Changes to attributes which require a restart/migration will be rejected (e.g. number of owners, number of segments)