1 Reply Latest reply on Nov 27, 2017 8:48 AM by Paul Ferraro

    Adding distributable to war make it undeployable on wildly 10

    Faisal Masood Newbie
      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>