Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-4064

Clustered SCA binding does not work - wrong ha and full-ha configuration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • jboss-fuse-6.2.1
    • jboss-fuse-6.2.1
    • SwitchYard
    • None
    • % %

    Description

      Clustered SCA binding does not work with current standalone-ha.xml and standalone-full-ha.xml configuration.

      SCA component has set cache-name to cluster, but it does not work properly:

      14:38:39,928 WARN  [org.switchyard.component.sca] (MSC service thread 1-8) SWITCHYARD039204: Cannot enable clustered SCA binding for {urn:switchyard-quickstart-demo-cluster-credit:1.0}CreditCheck.  No distributed cache is avaialble.
      

      When is added new switchyard cache-container and SCAComponent use them, it works:

      <cache-container name="switchyard" default-cache="default" start="EAGER">
          <transport lock-timeout="60000"/>
          <replicated-cache name="default" mode="SYNC" start="EAGER" batching="true">
              <locking isolation="REPEATABLE_READ"/>
          </replicated-cache>
      </cache-container>
      
      <module identifier="org.switchyard.component.sca" implClass="org.switchyard.component.sca.deploy.SCAComponent">
          <properties>
              <cache-name>
                  switchyard
              </cache-name>
          </properties>
      </module>
      

      The following settings is the same as is in FSW 6.0.

      Use quickstarts/demos/cluster as reproducer.

      Attachments

        Issue Links

          Activity

            People

              mageshbk_jira Magesh Bojan (Inactive)
              vchalupa_jira Václav Chalupa (Inactive)
              Martin Basovnik Martin Basovnik (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: