ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

API Gateway v10.1 upgrade error -- the gateway process cannot start up

book

Article ID: 224263

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

We have our gateways currently running on v10 CR03 and had attempted to upgrade our dev clusters to v10.1 using the upgrade patches.
However after installing both the patches and upgrading the DB, the gateway didn't come up, it went to won't start status.

This is the sequence in which we installed the patches while performing the upgrade :

Layer7_API_PlatformUpdate_64bit_v10.1.00-CentOS.L7P

Layer7_API_Gateway_v10.1.00.11620.L7P

[[email protected] bin]$ ./gateway.sh run
Unrecognized VM option 'PrintGCDateStamps'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

 

Environment

Release : 10.1

Component :

Resolution

In Java 11, some JVM flags including those used in Java 8 for Garbage Collection Logging have been removed.

If these are still contained in the JVM flags specified in the appliancedefs.sh, then the JVM will not be able to start.

It's known that the following options are unrecognized in Java 11:

  • -d64
  • PrintGCTimeStamps
  • PrintGCDateStamps
  • PrintTenuringDistribution
  • PrintGCCause
  • UseGCLogFileRotation
  • NumberOfGCLogFiles
  • GCLogFileSize

 

An example to translate the old gc options to the new format,

old options:

node.java.opts= -XX:+UseParallelOldGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=20M -Xloggc:var/logs/ssg_gc.log -XX:+UseCompressedOops

 

new options:

node.java.opts= -XX:+UseParallelOldGC -Xlog:gc*:var/logs/ssg_gc.log:time,level,tags:filecount=10,filesize=20M -XX:+UseCompressedOops