Typo in JVM_MEM_OPTS proxyserver.sh - CA Access Gateway SPS

Products

• SITEMINDER
• CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction

 

After having upgraded CA Access Gateway (SPS) to 12.8SP7, the proxyserver.sh file shows:

  JVM_MEM_OPTS="-ms256m -mx1024m"

instead of

  JVM_MEM_OPTS="-Xms256m -Xmx1024m"

 

Resolution

 

At first glance, the parameter passed to the process is indeed without the -X:

  # ps auxww | grep java
  nobody      2720 97.8 11.4 2982492 212656 ?      Sl   10:56   0:14 /opt/jdk8u275-b01/bin/java -ms256m -mx1024m -server

And when looking to the process itself, it reports it correctly passed with the -X prefix:

  # /opt/jdk8u275-b01/bin/jps -lvm
  2720 com.netegrity.proxy.ProxyBootstrap -config /opt/CA/secure-proxy/proxy-engine/conf/server.conf -Xms256m -Xmx1024m -XX:MaxMetaspaceSize=256M -Dcatalina.base=/opt/CA/secure-proxy/Tomcat -Dcatalina.home=/opt/CA/secure-proxy/Tomcat -Djava.io.tmpdir=/opt/CA/secure-proxy/Tomcat/temp -DHTTPClient.log.mask=0 -DHTTPClient.Modules=HTTPClient.RetryModule|org.tigris.noodle.NoodleCookieModule|HTTPClient.DefaultModule -Dlogger.properties=/opt/CA/secure-proxy/Tomcat/properties/logger.properties -Djava.endorsed.dirs=/opt/CA/secure-proxy/Tomcat/endorsed -Dfile.encoding=UTF8 -DIWACONFIGHOME=/opt/CA/secure-proxy/proxy-engine/conf/sts-config/globalconfig -DNETE_WA_ROOT= -DPWD=/opt/CA/secure-proxy
  2847 sun.tools.jps.Jps -lvm -Dapplication.home=/opt/jdk8u275-b01 -Xms8m

Further, when modifying to some specific values:

  JVM_MEM_OPTS="-ms1000m -mx2000m"

Then the parameters are correctly passed to the Java process at the bootstrap with the -X prefix:

  # /opt/jdk8u275-b01/bin/jps -lvm
  8163 com.netegrity.proxy.ProxyBootstrap -config /opt/CA/secure-proxy/proxy-engine/conf/server.conf -Xms1000m -Xmx2000m -XX:MaxMetaspaceSize=256M -Dcatalina.base=/opt/CA/secure-proxy/Tomcat -Dcatalina.home=/opt/CA/secure-proxy/Tomcat -Djava.io.tmpdir=/opt/CA/secure-proxy/Tomcat/temp -DHTTPClient.log.mask=0 -DHTTPClient.Modules=HTTPClient.RetryModule|org.tigris.noodle.NoodleCookieModule|HTTPClient.DefaultModule -Dlogger.properties=/opt/CA/secure-proxy/Tomcat/properties/logger.properties -Djava.endorsed.dirs=/opt/CA/secure-proxy/Tomcat/endorsed -Dfile.encoding=UTF8 -DIWACONFIGHOME=/opt/CA/secure-proxy/proxy-engine/conf/sts-config/globalconfig -DNETE_WA_ROOT= -DPWD=/opt/CA/secure-proxy

As such, this specific syntax in the proxyserver.sh has no influence on the java process as the parameters are correctly passed at the bootstrap.