SAP Knowledge Base Article - Preview

2829932 - Clustered SAP Mobile Platform (SMP) 5 out of 13 services would not start up

Symptom

  • Network issue then 5 of 13 SMP 3.0 clustered servers will not start afterwards
  • Errors seen in logs:

    ~~~~~~~~~~Start here~~~~~~~~~~~~~

    2019 07 26 06:30:23#0-400#WARN#org.jgroups.protocols.TCP###TransferQueueBundler,se0917280-c5d4-4862-a48c-5055e4e478f7:com.sap.mobile.platform.server.configuration.persistence.service.impl.ClusterHandler,X: no physical address for 97a68d17-429c-3c1f-5d94-cdef9c01fac8, dropping message |   error from oci.log(attached) !ENTRY org.eclipse.osgi 4 0 2019-07-26 06:31:15.627 !MESSAGE SMPServerStatusManager: 2019 07 26 06:31:15.627 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.agentry.core <-- Issue SMPServerStatusManager: 2019 07 26 06:31:15.627 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.cluster.management.server <-- Issue SMPServerStatusManager: 2019 07 26 06:31:15.627 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.admin.jaxrs.backendconnections.impl <-- Issue SMPServerStatusManager: 2019 07 26 06:31:15.627 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.admin.jaxrs.sldds <-- Issue SMPServerStatusManager: 2019 07 26 06:31:15.627 Bundles (and their services) not yet initialized: com.sap.gw.rt.service.cache <-- Issue  
    ~~~~~~~~~~~End here~~~~~~~~~~~~~~
      
  • Below are steps taken:
    1. Ensured the service was stopped, java.exe was NOt running, work/tmp cleared, no lock files; reboot  
    2. Ensured query returned DAYS not Days select prop_id, STRING_VALUE, LONG_STRING_VALUE, LONG_BINARY_VALUE from X_smp.SMP_CLUSTER_PROP_VALUE where prop_id in (SELECT prop_id FROM X_smp.SMP_CLUSTER_CONFIG_PROP where component = 'com.sap.mobile.platform.server.configuration.ServerConfigManager' and context = 'configuration/com.sap.mobile.platform.server.launcher/config-sys.properties' and prop_name = 'com.sap.mobile.platform.server.sld.periodical.upload.timeunit');  
    3. Ran the following update in smp database that updated 1 row / commited ; go.bat -clean       


Read more...

Environment

  • SAP Mobile Platform 3.0 (SP11)
  • Windows Server 2008 r2 64b 8 cpus/ 24g ram  
  • Current cpu usage 0 
  • JVM usage under 7g

Product

SAP Mobile Platform 3.0

Keywords

"Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.agentry.core","SMP 3.0 cluster","Cannot start SMP 3.0","SMP Cluster issue" , KBA , MOB-ONP-AGS , SAP Mobile On Premise Agentry Server , 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.