SAP Knowledge Base Article - Preview

2051990 - SAP Mobile Platform 3.0SP03 with enterprise database hangs on startup loading resources bundles - SUP/SMP

Symptom

User installed SAP Adaptive Server Enterprise 15.7 on Windows 2008r2 and then installed SAP Mobile Platform 3.0SP3 successfully with ASE as the persistence database.  When attempting to start the SAP Mobile Platform server, server hung on startup loading resource bundles.  Log shows:

2014 07 29 23:42:24#0-500#ERROR#org.osgi.service.log.LogService##anonymous#org.eclipse.virgo.medic.log.osgi.OSGiLogServiceListener@72c10304###Bundle org.eclipse.osgi_3.8.1.v20120830-144521,

SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.agentry.core <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.configuration.persistence <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.general.igwfilewatcher <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.lcmservices.webapps.http <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.online.supportability.changeanalysis <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.admin.jaxrs.agentry <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.admin.jaxrs.kapsel <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.admin.jaxrs.security <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.admin.jaxrs.server <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.applicationimportexport.nativehandler <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.foundation.admin <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.notifications.http <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.applicationimportexport.wrapper <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.notifications.blackberry <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.online.admin.common <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.proxy.connection.pooling <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.coreservices.appsettings.odata <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.notifications.handler <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.online.statistics.util <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.proxy.connectivity.onpremise <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.proxy.core <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.security.config <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.connectivity.configuration.file <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.connectivity.configuration.impl <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.connectivity.destination.http.api <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.connectivity.destination.http.impl <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.connectivity.impl <-- Issue
SMPServerStatusManager: YYYY MM DD HH:MM:SS Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.security.admin.impl <-- Issue

 


Read more...

Environment

  • SAP Adaptive Server Enterprise 15.7 (persistence database)
  • SAP Mobile Platform 3.0SP3

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Mobile Platform 3.0

Keywords

  • ASE
  • SMP
  • hang
  • startup
  • resources
, KBA , MOB-ONP , SAP Mobile Platform on Premise , 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.