SAP Knowledge Base Article - Public

3217823 - Cloud Agent will not start after upgrade in SAP Analytics Cloud (SAC)


After updating the Cloud Agent to version 1.0.354, it will not start when the Tomcat for the Cloud Agent is started.

In the Catalina.out file you see the error message:

SEVERE [localhost-startStop-2] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
SEVERE [localhost-startStop-2] org.apache.catalina.core.StandardContext.startInternal Context [/C4A_AGENT] startup failed due to previous errors

and in the localhost.<Date Stamp>.log file you see the error

SEVERE [localhost-startStop-2] org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener of class
java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class="com"/sap/fpa/cloud/rest/cs/DriverManager, offset=6 (unable to load class
at org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(
at org.apache.catalina.loader.WebappClassLoaderBase.findClass(
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(
at org.apache.catalina.core.DefaultInstanceManager.loadClass(
at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(
at org.apache.catalina.core.DefaultInstanceManager.newInstance(
at org.apache.catalina.core.StandardContext.listenerStart(
at org.apache.catalina.core.StandardContext.startInternal(
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.deployWAR(
at org.apache.catalina.startup.HostConfig$
at java.util.concurrent.Executors$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

This issue only occurs when using an IBM version of Java for the Tomcat hosting the Cloud Agent.


  • SAP Cloud Agent 1.0.354
  • IBM JVM 1.7
  • Tomcat 8

Reproducing the Issue

  1. Install Tomcat  8 and use an IBM JVM version 1.7 with it
  2. Upgrade to SAP Cloud Agent 1.0.354


This is caused by using the older version of the IBM JVM


To resolve this, use a 1.8 version of the JVM.

Note: While IBM JVM's should work, it is recommended to use SAP JVM with the Cloud Agent.

See Also

Your feedback is important to help us improve our knowledge base.


SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped, sap analyst cloud,,,,,,, predictive analytics (analysis), data analysis (analytics) tools, analytics tools, sap analytics cloud, data literacy, advanced analytics, data democratization, analytics software, real time analytics, self service analytics, advanced data analytics, analytics as a service, analytics cloud / cloud analytics, saas analytics, cloud bi, enterprise planning, cloud data analytics, cloud based analytics, analytics cloud platform, modern analytics, real time analysis, cloud analytics solution(s), what is sap analytics cloud, cloud analytics tools, analytics in the cloud, cloud analytics software , KBA , LOD-ANA-DES , Story Design & Visualizations , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem


SAP Analytics Cloud 1.0