ApplicationResponseFault with namespace longer than 60 in sync soap message

[marcmaurí]

Hi,

we are on pi 7.0 and our scenario is a async-sync bpm. In the sync soap message, the webservice raise an application error. In the response soap message we get the following detail tag:

<detail><ApplicationResponseFault xmlns="http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10"><DocumentResponse xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"><Response><ResponseCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">BusinessReject</ResponseCode></Response></DocumentResponse></ApplicationResponseFault></detail>

In sxi_monitor this application error isn't caught and a system error is generated.

In the system error message we get:

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>

<SAP:P1>500</SAP:P1>

<SAP:P2>Internal Server Error</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4271) at com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:572) at com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at

... ....

In defaulttrace.trc we get ","<sap:ApplicationFaultMessageNamespace> is longer than 60 characters: http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10",":

"09/04/2009","10:22:43:421","unable to generate the header map","Error","","com.sap.aii.adapter.xi.ms.XIMessage.getHeaderMap()","sap.com/com.sap.aii.af.app","SAPEngine_Application_Thread[impl:3]_14","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE005E00005F2300000A6C000472BC344957CC","com.sap.aii.adapter.xi.ms.XIMessage","","","n/a","b82f88e0992b11dea4d8001a64317eee","","0","0","","0","","","0","com.sap.aii.adapter.xi.ms.XIMessage","SAPEngine_Application_Thread[impl:3]_14","","J2EE_GUEST",

"09/04/2009","10:22:43:421","<sap:ApplicationFaultMessageNamespace> is longer than 60 characters: http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10","Error","","com.sap.aii.messagi...,

"09/04/2009","10:22:43:421","Could not process message from 192.168.130.21 due to java.lang.NullPointerException.","Error","","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(HttpServletRequest, HttpServletResponse)","sap.com/com.sap.aii.af.ms.app","SAPEngine_Application_Thread[impl:3]_55","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE0083000072F700000A6C000472BC344955F3","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet","192.168.130.21,java.lang.NullPointerException,","192.168.130.21,java.lang.NullPointerException,","SAPDES_TPI_34103150","1d72b100992c11dec67f001a64317eee","PIISUSER","0","0","","1","","","15337","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet","SAPEngine_Application_Thread[impl:3]_55","","PIISUSER",

"09/04/2009","10:22:43:421","The SAP XI Adapter Framework Messaging Service caught an exception during rendering an XML Message. Details can be found in the trace file for Location com.sap.aii.messaging.mo.xmb. Action: Please contact SAP Support and provide the trace file.","Error","/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK","com.sap.aii.messaging.mo.xmb.XMBErrorHeader.marshal(XMLWriter)","sap.com/com.sap.aii.af.app","SAPEngine_Application_Thread[impl:3]_14","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE005E00005F2000000A6C000472BC3449559F","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","","","n/a","b82f88e0992b11dea4d8001a64317eee","","0","0","","0","/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK","","0","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","SAPEngine_Application_Thread[impl:3]_14","","J2EE_GUEST",

So I think the problem is due to the namespace length. I'm right?

We can't change the consumed webservice to reduce namespace length and our customer ask us to solve it in PI. Is there any way to change the namespace before to be treated and get a correct application error?

Thanks in advance,

Marc

Edited by: Marc Mauri on Sep 5, 2009 12:06 PM

[Former Member]

this issue is resolved in 7.1 EHP1

[former_member200962]

This note should be of your interest: https://service.sap.com/sap/support/notes/901988

Regards,

Abhishek.

[marcmaurí]

Thanks Abhishek,

we changed de wsdl definition but the problem wasn't solved.

The webservice application we are consuming, send us the applicationfault tag with a longer than 60 namespace, so we get the same error.

Is there any way to change the namespace before to be treated and get a correct application error?

Thanks in advance,

[Former Member]

Hi Marc,

A customized adapter module will resolve this matter.

Let us know if you have more questions.

Regards.

Neetesh

[marcmaurí]

Hi Neetesh,

we developed our own adapter module. We use it in our receiver soap adapter, module tab, before and after the standard module sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean.

In this audit log secuence you can see that the problem seems not to be solved, because the error is triggered when processing response message inside adapter module sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean, so our module is not called and the problem remains.

2009-09-22 19:06:41 Success Message successfully received by messaging system. Profile: XI URL: http://sapdes:50300/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

(...)

2009-09-22 19:06:41 Success The message status set to DLNG.

2009-09-22 19:06:41 Success Delivering to channel: CC_WS_DOS

2009-09-22 19:06:41 Success MP: Entering module processor

2009-09-22 19:06:41 Success MP: Processing local module *localejbs/AM_OWN_MODULE*

2009-09-22 19:06:41 Success GetHostName: Module called

2009-09-22 19:06:41 Warning Inside my own adapter Module <-- THIS IS A TRACE MESSAGE CODED INSIDE OUR MODULE

2009-09-22 19:06:41 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

2009-09-22 19:06:41 Success SOAP: request message entering the adapter with user J2EE_GUEST

2009-09-22 19:06:41 Success SOAP: Web Services Security processing...

2009-09-22 19:06:41 Success SOAP: apply Web Services Security...

2009-09-22 19:06:41 Success SOAP: Web Services Security applied.

2009-09-22 19:06:42 Success SOAP: completed the processing

2009-09-22 19:06:42 Success SOAP: continuing to response message 4d2c88e0-a79a-11de-9ffa-001a64317eee

2009-09-22 19:06:42 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault <----

---

THIS ERROR IS DUE TO NAMESPACE LENGHT (WE CAN SEE THIS ERROR IN DEFAULT_TRACE.LOG)

2009-09-22 19:06:42 Success MP: Processing local module localejbs/AM_OWN_MODULE

2009-09-22 19:06:42 Success MP: Leaving module processor

2009-09-22 19:06:43 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System. 2009-09-22 19:06:43 Success The message status set to DLVD.

Any suggestion?

Thanks in advance,

[Former Member]

Hello,

I have the same problem. I tried it too and seems the exception occurs just before the adapter module. I also have cut the namespaces at WSDL (Maybe check the definition loaded at PI) with the same namespace that I'll modified at Adapter Module but doesn't work

[former_member200962]

SAP PI7.0 only supports namespace length of upto 6o characters. If your namespace length is more than 60 then manually remove the extra characters from your WSDL file.

This will solve your issue. There is even a SAP note for the same.....if I get the note number i will post it.

A wiki: https://wiki.sdn.sap.com/wiki/display/XI/IntegrationBuilderNamespaceofexternal+definitions

REgards,

Abhishek.

Edited by: abhishek salvi on Sep 5, 2009 3:43 PM