Adding distributable to war make it undeployable on wildly 10

[masood.faisal]

file:///file:///file:///file:///file:///file:///file:///file:///file:///file:///file:///file:///file:///file:///

"{\"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available.\" => {

    \"Services that were unable to start:\" => [

        \"jboss.clustering.web.locator.\\\"test.war\\\"\",

        \"jboss.clustering.web.locator.\\\"tes.war\\\".nodes\",

        \"jboss.clustering.web.locator.\\\"test.war\\\".registry\",

        \"jboss.clustering.web.\\\"test.war\\\"\",

        \"jboss.deployment.unit.\\\"test.war\\\".deploymentCompleteService\",

        \"jboss.infinispan.mycontainer.\\\"test.war\\\"\",

        \"jboss.infinispan.mycontainer.\\\"test.war\\\".config\",

        \"jboss.undertow.deployment.default-server.default-host./myapp\",

        \"jboss.undertow.deployment.default-server.default-host./myapp.UndertowDeploymentInfoService\",

        \"jboss.undertow.deployment.default-server.default-host./myapp.codec\",

        \"jboss.undertow.deployment.default-server.default-host./myapp.session\"

    ],

    \"Services that may be the cause:\" => [\"jboss.clustering.registry.mycontainer.routing.entry\"]

}}"

i have a replication-config in my jbos-web.xml

<jboss-web>

    <context-root>myapp</context-root>

    <disable-cross-context>false</disable-cross-context>

    <replication-config>

        <cache-name>mycontainer.mycache</cache-name>

        <replication-granularity>SESSION</replication-granularity>

    </replication-config>

</jboss-web>

[pferraro]

It looks like you are trying to use a custom cache container to store/passivate web session data.  Can you paste the configuration of this cache-container from your Infinispan subsystem config?  You are likely missing the module attribute required to use this cache container with the distributable session manager.

e.g.

<cache-container name="mycontainer" module="org.wildfly.clustering.web.infinispan">...</cache-container>