Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-16144

[GSS](7.2.z) Not possible to configure more than 1 passivation-store per subdeployment

    XMLWordPrintable

    Details

      Description

      In EAP 7.1 and 7.2 per subdeployment, in the EAR, only one passivation store can be used.
      If within one EAR-subdeployment caches "infinispanCache" and "infinispanCache2" per config below are used (referenced via @Cache annotation or <ec:cache-ref> deplyoment desriptor), it results in the error listed below:

      <caches>
      <cache name="simple"/>
      <cache name="infinispanCache" passivation-store-ref="infinispanStore" aliases="passivating"/>
      <cache name="infinispanCache2" passivation-store-ref="infinispanStore2" aliases="longLife"/>
      </caches>
      <passivation-stores>
      <passivation-store name="infinispanStore" cache-container="ejb" bean-cache="passivation" max-size="5"/>
      <passivation-store name="infinispanStore2" cache-container="ejb" bean-cache="passivation" max-size="10"/>
      </passivation-stores>

      using both caches from 1 EAR-subdeployment leads to:

      2019-01-10 12:14:10,757 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."frameworktest.ear"."framework_ejb.jar".cache-dependencies-installer: org.jboss.msc.service.StartException in service jboss.deployment.subunit."frameworktest.ear"."framework_ejb.jar".cache-dependencies-installer: Failed to start service
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
      [...]
      Caused by: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache-configuration.ejb.frameworktest.ear/framework_ejb.jar is already registered
      at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:111)

      It should be possible to configure more than 1 passivation-store per subdeployment, in particular when different time-outs are configured this way.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              pferraro Paul Ferraro
              Reporter:
              lakagwu Lami Akagwu
              Tester:
              Daniel Cihak Daniel Cihak
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: