Show TOC

OSGi and Log4j Errors in Server LogLocate this document in the navigation structure

Problem
While reviewing the server log, you may see multiple errors related to OSGi and Log4j , for example:
...
2015 03 27 16:09:39#+0800#ERROR#org.osgi.service.log.LogService##anonymous#org.eclipse.virgo.medic.log.osgi.OSGiLogServiceListener@4d10ed49###Bundle com.sap.it.ictools.mapping.core.valuemapping_1.16.3, [SCR] Component definition XMLs not found in bundle com.sap.it.ictools.mapping.core.valuemapping. The component header value is OSGI-INF/*.xml |
2015 03 27 16:09:39#+0800#ERROR#org.osgi.service.log.LogService##anonymous#org.eclipse.virgo.medic.log.osgi.OSGiLogServiceListener@4d10ed49###Bundle org.eclipse.equinox.ds_1.4.0.v20120112-1400, [SCR] Component definition XMLs not found in bundle com.sap.it.ictools.mapping.core.valuemapping. The component header value is OSGI-INF/*.xml |
...
2015 03 27 16:10:31#+0800#ERROR#System.err##anonymous#Start Level Event Dispatcher###log4j:WARN No appenders could be found for logger (com.sap.mobile.platform.server.general.dbstatus.Activator). |
2015 03 27 16:10:31#+0800#ERROR#System.err##anonymous#Start Level Event Dispatcher###log4j:WARN Please initialize the log4j system properly. |
2015 03 27 16:10:31#+0800#ERROR#System.err##anonymous#Start Level Event Dispatcher###log4j:WARN 
...

These messages are expected, and do not indicate a problem with SAP Mobile Platform.