Access Gateway does not start after upgrading to 4.4.4

  • 7024416
  • 08-Feb-2020
  • 13-Mar-2020


  • Access Manager Version 4.4.4
  • Access Gateway Appliance cluster


  • All Access Manager devices have been upgraded from version 4.4.1 to 4.4.4
  • After the upgrade only one Access Gateway Appliance out of a cluster fails to start returning: "org.apache.catalina.LifecycleException.error"

  • Catalina.out reports the following log entries:
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/nesp]]
        at org.apache.catalina.util.LifecycleBase.start(
        at org.apache.catalina.core.ContainerBase.addChildInternal(
        at org.apache.catalina.core.ContainerBase.addChild(
        at org.apache.catalina.core.StandardHost.addChild(
        at org.apache.catalina.startup.HostConfig.deployDirectory(
        at org.apache.catalina.startup.HostConfig$
        at java.util.concurrent.Executors$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.lang.IllegalStateException: Unable to complete the scan for annotations for web application [/nesp] due to a StackOverflowError. Possible root causes include a too low setting for -Xss and illegal cyclic inheritance dependencies. The class hierarchy being processed was [org.bouncycastle.asn1.ASN1EncodableVector->org.bouncycastle.asn1.DEREncodableVector->org.bouncycastle.asn1.ASN1EncodableVector]


  • This kind of error often indicates a JAVA version conflict or duplicate application files.
  • No differences have been identified by comparing the Embedded Service Provider (ESP) application folder at: "webapp/WEB-INF/lib/" folder between the working and non working Access Gateway Appliances
  • However, when the folder was compared to a "clean" lab server, there was an extra file found (Bouncy Castle Crypto package).

  • A fresh installation of NAM 4.4.4 Access Gateway Appliance did not include a JDK14 version of the Bouncy Castle Crypto package
  • After removing the bcprov-jdk14-119.jar the appliance started without any further problems
  • The jdk14 file was also removed from the working access gateways as a precaution.


The cause was an older version of the Bouncy Castle Crypto package compiled for JDK14 getting loaded on one node only.
Since the release of NAM 4.0 jdk15 has been used. This lib must therefore be a leftover from NAM 3.2.x

The load order on just one node was different for an unknown reason. All nodes were configured and upgraded identically but there must have been some environmental issue that causes the jar files to load in a different order on this server.