Skip to Content
0
Former Member
Jan 30, 2014 at 04:41 PM

" Parsing Empty Source Error " In SolMan SLD Log

50 Views

Hi Everyone,

We have Solution Manager 7.1 SP 05 ( NW 7.02 SP10 ) and while setting up SUP 2.2 monitoring setup we have repeatedly following error at SolMan SLD Logs ;

SLD PayLoad generated at SUP side is accurate as per verification of SAP ;

We have also verified applicable pre-requisites as SUP Monitoring Set Up resources on SMP alongwith SUP Entry in SAP BC application server

and content management section of SolMan SLD;

SLD ping is successful and we do see SUP Host entry in the list of Automatic Data Supplier Entry on Solution Manager - only issue is sw comp. version and sw component details i.e. SCC, SUP Unwired Server, SUP Cache DB, SUP Mon DB and its version do not reflect at LMDB side.

Core Issue :

Eventhough SUP Payload is accurate / not corrupted ..it does not supply the SUP 2.2 SW Ver. Component Details etc. to SolMan ..i.e.

we do not see any SUP data at LMDB ; we have verified SLD Communication User at SUP's SCC ( SLD config ) has enough authorizations

as well.

even after increasing Trace level we don't see any error message in traces to pin point the root cause.We have only one SLD at Solution Manager so, we don't see any scope of authorization or other error related to ' Bridge Forwarding ' as it would be in case of Local / Master SLD scenario.

Error Message in SLD Log :

==========================================================================================================

#39 01/14/2014 15:37:22.526 [SAPEngine_Application_Thread[impl:3]_29] ERROR com.sap.lcr.sagent.DataSupplierServlet: IO Error

Thrown:

java.io.IOException: Parsing an empty source. Root element expected!

at com.sap.engine.lib.xml.parser.XMLParser.onEncodedDataReaderEOF(XMLParser.java:2893)

at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.onEncodedDataReaderEOF(AdvancedXMLStreamReader.java:433)

at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:173)

at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)

at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.addInputFromInputStream(AdvancedXMLStreamReader.java:292)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:226)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)

at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)

at com.sap.lcr.sagent.DataSupplierServlet.doPost(DataSupplierServlet.java:168)

at com.sap.lcr.sagent.DataSupplierServlet.doGet(DataSupplierServlet.java:65)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at com.sap.lcr.sagent.DataSupplierServlet.service(DataSupplierServlet.java:240)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

==================================================================================================

Pl. share your knowledge / inputs to resolve this issue where SLD Payload of SUP fails to transmit SUP SW Comp and ver. data to LMDB.

Thanks in Advance for your time and inputs.

Best Regards,

- Ishan