SAP Knowledge Base Article - Preview

2543279 - SMP 3.0.7 OData server hangs on a bundle at startup

Symptom

  • SMP OData runtime server fails to start after a new package deployment
  • The server log shows:

SMPServerStatusManager: 2017 09 22 11:19:34.601 Bundles (and their services) not yet initialized: com.sap.banking.banking-alertsbackend <-- Issue
SMPServerStatusManager: 2017 09 22 11:19:34.601 Bundles (and their services) not yet initialized: com.sap.banking.banking-custom-cb <-- Issue
 |
2017 09 22 11:19:36#0-600#INFO#System.out##anonymous#SMPServerStatusManager###SMPServerStatusManager: 256 of 281 tracked bundles have initialized. |
2017 09 22 11:19:46#0-600#INFO#System.out##anonymous#SMPServerStatusManager###SMPServerStatusManager: 256 of 281 tracked bundles have initialized. |
2017 09 22 11:19:56#0-600#INFO#System.out##anonymous#SMPServerStatusManager###SMPServerStatusManager: 256 of 281 tracked bundles have initialized. |
2017 09 22 11:20:06#0-600#INFO#System.out##anonymous#SMPServerStatusManager###SMPServerStatusManager: 256 of 281 tracked bundles have initialized. |
2017 09 22 11:20:16#0-600#INFO#System.out##anonymous#SMPServerStatusManager###SMPServerStatusManager: 256 of 281 tracked bundles have initialized. |

 The log does not progress beyond the above lines.


Read more...

Environment

  • SMP OData server version 3.0.7.5 on Windows OS

Product

SAP Mobile Platform 3.0

Keywords

bundle fail reboot. , KBA , MOB-ONP-COR , SAP Mobile On Premise Core Services , Problem

About this page

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

Search for additional results

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