ISPN-7277: Passivation disabled in embedded but enabled in server mode.

infinispan · Dec 5, 2016 · c1d0903 · c1d0903
1 parent c3e25c5
commit c1d0903
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/...ain/java/org/jboss/as/clustering/infinispan/subsystem/BaseStoreConfigurationResource.java b/...ain/java/org/jboss/as/clustering/infinispan/subsystem/BaseStoreConfigurationResource.java
@@ -52,7 +52,7 @@ public class BaseStoreConfigurationResource extends BaseLoaderConfigurationResou
                     .setXmlName(Attribute.PASSIVATION.getLocalName())
                     .setAllowExpression(true)
                     .setFlags(AttributeAccess.Flag.RESTART_RESOURCE_SERVICES)
-                    .setDefaultValue(new ModelNode().set(true))
+                    .setDefaultValue(new ModelNode().set(false))
                     .build();
     static final SimpleAttributeDefinition PURGE =
             new SimpleAttributeDefinitionBuilder(ModelKeys.PURGE, ModelType.BOOLEAN, true)

diff --git a/server/integration/infinispan/src/main/resources/schema/jboss-infinispan-core_9_0.xsd b/server/integration/infinispan/src/main/resources/schema/jboss-infinispan-core_9_0.xsd
@@ -907,7 +907,7 @@
                 <xs:documentation>If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.</xs:documentation>
             </xs:annotation>
         </xs:attribute>
-        <xs:attribute name="passivation" type="xs:boolean" default="true">
+        <xs:attribute name="passivation" type="xs:boolean" default="false">
             <xs:annotation>
                 <xs:documentation>If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.</xs:documentation>
             </xs:annotation>