Uploaded image for project: 'InsightEdge Platform'
  1. GS-13273

WEB-UI embedded remote service is not seen when configured with mirror

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Medium
    • Resolution: Won't Fix
    • Affects versions: None
    • Fix versions: None
    • Labels:
      None
    • Platform:
      All
    • SalesForce Case ID:
      00011187
    • Sprint:

      Description

      Expected:
      when there is a remote service with embedded space and a mirror within the same pu.xml - the space should be seen in the WEB-UI Spaces tab as it is in the GS-UI
      Actual:
      the WEB-UI refers only to the mirror/stateless pu and show nothing in the Spaces tab. Also this behavior isn't not consistently - when all configuration is separated to an external config file, the behaviour is as expected.
       
      Test is attached.

      Customer description:
      We have pu.xml file with defined mirror and remoting service with dedicated space for remoting (please see configuration).
      When configuration is internal to pu.xml mirror pu can be seen in WebUI "processing units" tab, but space created for remoting cannot be found in "spaces" tab.
      But if we export the same configuration to the separate file and import it in pu.xml - WebUI in tab "spaces" shows also spaces that are part of mirrors remoting service.

      Could you please advise why the very same configuration behaves differently in those two scenarios?

      Example configuration:

      <os-remoting:service-exporter id="serviceExporter" >
      <os-remoting:service ref="someRemotingService"/>
      </os-remoting:service-exporter>

      <bean id="someRemotingService" class="some.remoting.service.SomeRemotingService">
      <constructor-arg name="space" ref="gigaSpace"/>
      </bean>

      <os-core:mirror id="ourMirror" url="/./serviceName" space-sync-endpoint="spaceSynchronizationEndpoint">
      <os-core:source-space name="spaceName" partitions="20" backups="1"/>
      <os-core:properties>
      <props>
      <prop key="space-config.mirror-service.operation-grouping">group-by-replication-bulk</prop>
      </props>
      </os-core:properties>
      </os-core:mirror>

      <os-core:space id="remotingSpace" url="/./${tess-space.mirror.service-name}_SpaceForRemoting" />
      <os-core:giga-space id="gigaSpace" space="remotingSpace"/>

      File structure:
      Scenario 1
      <project-dir>/src/main/resources
      -- META-INF/spring/pu.xml (whole configuration content embedded in file)

      Scenario 2
      <project-dir>/src/main/resources
      -- META-INF/spring/pu.xml (imports config.xml)
      -- some/package/config.xml (whole configuration content embedded in file)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Yuvald Yuval Dori (Inactive)
              Participants of an issue:
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: