Software Gateway Fails To Start After Upgrade To 11.2

Products

• CA API Gateway

Issue/Introduction

After upgrading our software gateway install from 11.0 to 11.2 the gateway does not start and the following kinds of errors are seen in the ssg_0_0.log

 

com.l7tech.security.prov.defaultprov.DefaultJceProviderEngine: Initializing Bouncy Castle library in Non-FIPS mode
com.l7tech.security.prov.JceProvider: Requested JceProvider could not be instantiated: Missing BouncyCastle dependency.

org.springframework.context.support.ClassPathXmlApplicationContext: Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cryptoInit' defined in class path resource [com/l7tech/server/resources/ssgApplicationContext.xml]: Failed to instantiate [com.l7tech.server.security.CryptoInitializer]: Constructor threw exception
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'secureRandom' defined in class path resource [com/l7tech/server/resources/ssgApplicationContext.xml]: Cannot resolve reference to bean 'jceProvider' while setting bean property 'targetObject'

Environment

CA API Gateway 11.x

Cause

It was determined that the existing gateway.sh script currently in place within the environment was modified in order to hook a newrelic agent into the gateway.  This would cause the gateway.sh script from the upgrade to not be copied over and put in place.  The 11.2 gateway.sh script contains changes to how we load the BouncyCastle jar files which were now not in place in the environment which was resulting in the situation being seen.

Resolution

Contact support for an appropriate gateway.sh script which matches your gateway version.

 

Any changes made to the current gateway.sh script such as to hook a monitoring agent into the gateway would need to be implemented once again within the new gateway.sh script if desired.