error shows up in default trace, but nowhere else; how to get more info ?

[Former Member]

Our default (java) traces get filled up quickly with the following messages :

error 2010-06-29 11:10:13:851 Error during parsing body item ^mt_Order using class com.sap.aii.af.sdk.xi.mo.DefaultItem at ^Klantnaam/ caused by --- java.lang.NullPointerException com.sap.aii.af.sdk.xi.mo.Message.reparseRootDocument()

error 2010-06-29 11:10:13:850 Caught an Exception: java.lang.NullPointerException org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference. com.sap.aii.af.sdk.xi.util.StreamXMLScannerImpl.next()

error 2010-06-29 11:10:13:850 Excetption java.lang.NullPointerException at state 1 with current values Klantnaam com.sap.aii.af.sdk.xi.util.StreamXMLScannerImpl.updateState()

error 2010-06-29 11:10:13:849 Caught an Exception in EP: org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference. com.sap.aii.af.sdk.xi.util.StreamXMLScannerImpl.run()

error 2010-06-29 11:10:13:761 Error during parsing the SOAP part --- java.lang.NullPointerException

based on the phrase "Klantnaam" and "mt_Order" I could find the likely culprit interface. this is a plain and

simple SOAP-to-IDOC scenario.

these messages never show up in RWB, so they must fail before RWB even is involved.

I suspect that someone is sending us malformed soap (or http?) requests, and the soap message cannot be constructed from the message payload.

sometimes (but not nearly as often as the log messages appear) I see a message in RWB with this text as "message : SOAP document" :

authorization:Basic UElJU1VTRVI6cDBzdGIwZGU= accept-encoding:gzip sap-xi-messageid:8499D4D0835F11DFB78D0019994ADA63 content-length:7963 host:<deleted by poster> user-agent:SAP NetWeaver Application Server (1.0;711) content-type:multipart/related;boundary=SAP_0019994ADB6F02EE8FD38DB64E22D23D_END;type="text/xml";start="" soapaction:"http://sap.com/xi/XI/Message/30" ApplicationMessagesynchronous8499d4d0-835f-11df-b78d-0019994ada632010-06-29T09:20:11ZP_ismP21_100CRMXIF_ORDER_SAVEBestEffortSJMaf.p20.dbp20-seXIRA8499d4d0-835f-11df-b78d-0019994ada63is.20.cip20XI8499d4d0-835f-11df-b78d-0019994ada633.0af.p20.dbp20-seXIRA8499d4d0-835f-11df-b78d-0019994ada635fdc3fd7e5f335e3806fc35a13d2c233WarningOffMainDocumentMain XML documentApplication

seems like a HTTP header to me, but not quite sure...

my question : what can I do to get more information, especially about the content of the messages causing this behaviour ?

I tried enabling more logging for the components menstioned in the above entries, but to no avail.

traces in SMICM and SICF also were not helpful.

I hope to avoid to need to trace the actual network for the messages...

any help much appreciated !

Regards,

Ronald

Edited by: Ronald on Jun 29, 2010 11:24 AM Added RWB info

[Former Member]

Hi Ronald,

From the trace, I can see that itu2019s getting null pointer exception.

Normally this can occur due to the improper form of source message.

Please check the source message and see that there is no gap between the elements /tags of xml message.

[Former Member]

Thanks for your reply.

I am glad you support my diagnosis.

however, since it is an unknown party calling the web service,

my main question is how I can get more information on that source message.

is there any trace which dumps that message content before it is being passed to and parsed by the soap adapter ??

I have no clue who is sending this request, so I cannot ask them to investigate.

Edited by: BW teamlid on Jun 29, 2010 4:00 PM rephrase