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

XAP_GSM_OPTIONS not taken into account when starting GSM via Admin API

    Details

    • Type: Bug
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects versions: None
    • Fix versions: None
    • Labels:
      None
    • Platform:
      All
    • SalesForce Case ID:
      11874
    • Sprint:
    • Product:
      XAP
    • Edition:
      Premium

      Description

      When starting Gigaspaces via command line shell script (e.g. "./gs-agent.bat gsa.gsm 1 gsa.gsc 0 gsa.lus 1") the env var XAP_GSM_OPTIONS is correctly passed to VM arguments of GSM process.

      However when you start GSM via Admin Api
      (e.g. admin.getGridServiceAgents.getHostNames.get(hostToDeploy).startGridServiceAndWait(gridServiceManagerOptions))
      the started GSM process doesn't have arguments specified in XAP_GSM_OPTIONS.

      This is inconsistent behavior as e.g. env var EXT_JAVA_OPTIONS is passed to the GSM process correctly when starting this way.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ester Ester Atzmon
              Participants of an issue:
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: