We're updating the issue view to help you get more done. 

XAP_GSM_OPTIONS not taken into account when starting GSM via Admin API

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.

Workaround

None

Acceptance Test

None

Status

Assignee

Unassigned

Reporter

Ester Atzmon

Labels

None

Priority

Medium

SalesForce Case ID

11874

Fix versions

None

Commitment Version/s

None

Due date

None

Product

XAP

Edition

Premium

Platform

All