org.jboss.as.clustering.infinispan in standalone.xml

[Haitham Alkhatib]

Hi,

we are running wildfly in standalone mode and I've seen 

<extension module="org.jboss.as.clustering.infinispan"/> and below configurations in standalone.xml. My question is do we need this module inside standalone.xml or we can operate without it. our code doesn't use infinspan but I don't know if internal components of wildfly requires it ? 

Thanks,

Tim 

<subsystem xmlns="urn:jboss:domain:infinispan:13.0">
<cache-container name="ejb" default-cache="passivation" marshaller="PROTOSTREAM" aliases="sfsb" modules="org.wildfly.clustering.ejb.infinispan">
<local-cache name="passivation">
<expiration interval="0"/>
<file-store passivation="true" purge="false"/>
</local-cache>
</cache-container>
<cache-container name="web" default-cache="passivation" marshaller="PROTOSTREAM" modules="org.wildfly.clustering.web.infinispan">
<local-cache name="passivation">
<expiration interval="0"/>
<file-store passivation="true" purge="false"/>
</local-cache>
<local-cache name="sso">
<expiration interval="0"/>
</local-cache>
</cache-container>
<cache-container name="server" default-cache="default" marshaller="PROTOSTREAM" modules="org.wildfly.clustering.server">
<local-cache name="default">
<expiration interval="0"/>
</local-cache>
</cache-container>
<cache-container name="hibernate" marshaller="JBOSS" modules="org.infinispan.hibernate-cache">
<local-cache name="entity">
<heap-memory size="10000"/>
<expiration max-idle="100000"/>
</local-cache>
<local-cache name="local-query">
<heap-memory size="10000"/>
<expiration max-idle="100000"/>
</local-cache>
<local-cache name="timestamps">
<expiration interval="0"/>
</local-cache>
<local-cache name="pending-puts">
<expiration max-idle="60000"/>
</local-cache>
</cache-container>
</subsystem>

[Paul Ferraro]

With standalone.xml, this subsystem provides services for supporting:

* HttpSession passivation for <distributable/> web applications

* @Stateful EJB passivation

* JPA 2nd-level cache support
* EJB remoting endpoint registration

So long as both your server configuration and applications use none of the above, you can remove this subsystem.