SOAP Sender Parsing Error

[Former Member]

Hi Experts,

I am getting below SOAP Sender communication channel error. Intermittently :

PI SOAP adapter error:

Parsing Error: org.xml.sax.SAXParseException: Premature end of file.

at sender system they are getting below log in such cases:

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0"> <context>XIAdapter</context> <code>ADAPTER.JAVA_EXCEPTION</code> <text> java.io.IOException: Parsing Error: org.xml.sax.SAXParseException: Premature end of file. at com.sap.aii.af.sdk.xi.mo.DefaultItem.marshal(DefaultItem.java:489) at

Its working after couple of attempts from sender..

from past few months its working fine.

But this behavior is from past few days only..

Could you please guide me on possibilities for this behavior.. what to check from PI (Its ICO setup. its SOAP to SOAP interface -synchronous)

Thanks in advance..

Regards

Siri

[iaki_vila · Accepted solution]

Hi Siri,

What is your PI version and SP level?, may be it could be a bug like this 1849403 - Message Logging can cause empty response for sync messages

Regards.

[Former Member · Accepted solution]

Hi Inaka,

its PI 7.31 SP05

Regards

Siri

[Former Member · Accepted solution]

Hi Inaka\Experts,

Thanks for pointing to SAP note ,it could be because of this. I will check on this for sure..

- Meanwhile is SAP note Is the note 952402 and 1849402 or 952402 is new one..? I have not checked 952402 yet, so..

- Will it show any impact for existing interfaces by adding new patch.

Regards

Siri

[Former Member · Accepted solution]

Hi all,

any inputs on this pls..

Do we need to pay if we add new patches mentioned in SAP note..??

Regards

siri

[Former Member · Accepted solution]

Hi Inaki Vila,

Thanks a lot for pointing to right SAP note..

this behavior is happening due to logging for synch.

Do we need to pay if we update patches?

Regards

Siri

[Former Member]

Hi Experts,

Any inputs on this type of errors..

Regards

Siri

[former_member186851]

Hello Siri sha,

Its data issue.

Did the target webservice update to any new structure or certificates?

[Former Member]

Hi Raghu,

Thanks for reply..

yes,there are few changes at RCV and SND side and we reactivated all changes and doing re test.

How to figure it out ,if its not stable..same payload is passing in few attempts and failing as Parser error..this is confusing .. can it be cache issue also??

Regards

Siri

[iaki_vila]

Hi Siri,

It could be a cache issue but it is more usual a data issue as Raghuraman said. You can try with the check Do Not Use SOAP Envelope, dealing later with the SOAP tags, but you can check what is the exact data that you are receiving, probably none.

Regards.

[Former Member]

Hi Inka,

Thanks a lot for reply..

How to trace if its data issue(I am still not clear as its not constant behavior for same payload),I am not seeing any empty payloads in systems or will it not enter the log if its empty??(I will double check on this again).

- how its going to help us ,if we keep  Do Not Use SOAP Envelope..( I am jut curios on its impact in this situation..)

please guide me to clear this issue

Regards

Siri

[iaki_vila]

Hi Siri,

- how its going to help us ,if we keep  Do Not Use SOAP Envelope..( I am jut curios on its impact in this situation..)

The impact will be that you have to deal with SOAP tags, extract the payload on the request and to wrap the response with the tags.

When you have the exception of premature end of file, i assume that you can't see payload. am i wrong?, if i am not wrong with this option the sender SOAP adapter doesn't do SOAP verifications, and sometimes, not always, you can get the exact payload and to check it. There are other alternatives like the XPI inspector to check.

Regards.

[former_member186851]

Hello Sirisha,

For failing records also your using the same data as the one in the successful one?

[Former Member]

Hi Raghu,

yes ,same request payload is getting OK after some attempts..

Regards

Siri

[former_member429661]

Hi there,

i know this is more than a half year old... but maybe someone has the same problem an could use my solution!

I got the same error on my SAP-System. My Problem was, that the SOAP string has a "blank" on this position...between "soapenv:" and "Envelope".

sEnv = "<soapenv: Envelope..."

After correction it works like a charme...

--Bernward