SAP Knowledge Base Article - Preview

2954478 - SMP cannot start up after upgrading to SMP 3.1 SP00 with error message: Caused by: java.lang.ClassNotFoundException: com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve

Symptom

Upgrade to SMP 3.1 SP00 PL00 was successful, but SMP couldn't start afterwards with the below messages in the osgi.log:

Caused by: java.lang.ClassNotFoundException: com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve

!MESSAGE SMPServerStatusManager: 2020 06 17 10:34:23.282 Bundles (and their services) not yet initialized:

Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.foundation.monitoring.webconsole <-- Issue
Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.online.admin.common <-- Issue
Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.online.filters.util <-- Issue
Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.coreservices.appsettings.odata <-- Issue
Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.offline.filter <-- Issue


Read more...

Environment

SAP Mobile Platform (SMP) 3.1 SP00 PL00

Product

SAP Mobile Platform 3.1

Keywords

smp, sup, odata, server upgrade, update, migrate, RequestTracingValve, com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve , KBA , MOB-ONP-INS , SAP Mobile On Premise Installer , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.