XI SOAP adapter : Error during parsing the SOAP part

[former_member246370]

Hello experts,

We have several scenarios SOAP to IDocs.

We are on XI 3.0 SP19, and since 9/6/09 around 4:00 PM GMT, our SOAP channels used to communicate with a specific 3rd party all stoped accepting incoming SOAP requests. All the messages are stucked on third party side, and we get the following error in the defaulttrace and application logs :

#1.5#001125A5BCD00066000076850013109E00046BF6A963E479#1244607054865#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.mo.Message.reparseRootDocument()#PIMSOAP#21217##pxaci_PXA_6443451#PIMSOAP#a71ebfa0556d11decc24001125a5bcd0#SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#com.sap.aii.messaging.mo.Message#Plain###Error during parsing the SOAP part --- java.lang.NullPointerException#

It happened at the same time on all the environments for every interfaces using SOAP message from this sender to XI. That's the reason why we think it is a global issue, but we can not find anything concerning this error. Has anybody encountered this error or would have any clue of where it comes from ?

Many thanks,

Best regards,

Guislain

[MichalKrawczyk · Accepted solution]

hi,

check the scenario with any other SOAP test tool like SOAPUI (free tool)

then you will know if this is an XI error in the calling application error

Regards,

Michal Krawczyk

[former_member246370]

Hello Michal,

Thanks a lot for your help. Actualy we have tested with SOAP UI yesterday and this is what came out of the tests :

test 1 : we tried to call the XI service with the wsdl and put dummy data inside --> test OK

test 2 : we loaded in SOAP UI one of the file from our partner and tried to call the service --> test NOT OK

test 3 : we realized that there were some blank lines at the beginning of the file provided by the partner. we removed these blank lines --> test OK.

So we first thought that the format of the file sent by the partner was wrong and this is why we were getting the parsing error, because of these blank line. The thing is that these blank lines have always been here ! We have checked with old successful messages and they contain also these lines and if we test them in SOAP UI we get an error also. so it does not seems to come from this.

Moreover, as I said in my previous message, it happened on all the environments approximatly at the same time, so we are suspecting a global problem, but which one ? That's the million dollar question

Would you have any other ideas ?

Thanks a lot,

Best regards,

Guislain