PI 7.31 Single Stack SOAP: call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]

[nageswararao_v2]

Hi SAP Gurus...

Since I am new bee to SAP PI 7.31 Single Stack, I was stucked in my scenario here my requirment:

We have two PI systems and pushing the data from One PI to another PI system using SOAP adapter XI 3.0 protocol. Since both PI systems are Single stack(Java) and while the message processing in Receiver Communication channel we are getting below error:

• SOAP: call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]

Please find the below error screenshot which i am getting in receiver communication channel:

Thanks in advance...

Thanks & Regards,

Nagesh

[nageswararao_v2 · Accepted solution]

Hello gurus...

I am still stucked at above mentioned error, Please help me on this...

Awaiting for your response.

Thanks & Regards,

Nagesh

[nageswararao_v2 · Accepted solution]

Hi Gurus...

Now I changed my communication channel as SOAP adapter with SOAP 1.1 message protocol for both PI's instead of XI 3.0 protocol.

Now the message is processing successfully to the second PI, But in second PI's sender communication channel getting stucked with the following error, please help me on this issue....

• SOAP: call failed com.sap.aii.adapter.xi.routing.RoutingException: CPA Cache lookup for receiver binding failed for message com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Channel object with Id Channel:6437fa535fe83fb186f65be491467cfa not available in CPA Cache.

     Please find below capture of error which i am getting in sender cc on second PI

   And also please help me how to restrict/block/avoid the response for my soap channel, since we are working with asynchronous interface we don't need any response...

Thanks & Regards,

Nagesh

[fatih_eren · Accepted solution]

Hello NageswaraRao,

I have with the SOAP Adapter XI 3.0 protocol the same problem with "BubbleException: HTTP Response Received. Status Code = 500 [null "null"]".

Have you found a solution with the XI 3.0 protocol?

[claudia_liszy · Accepted solution]

Hi Fatih,

on our side this error was caused by an authorization problem.

Have you checked whether the user, which is mentioned in the receiver communication channel, has the proper roles or does even exist in the receiver system?

Regards

Claudia

[fatih_eren · Accepted solution]

Hello Claudia,

It's not an user or authorization Problem.

If I Change the protocol from SOAP XI 3.0 to SOAP 1.1, then the message is received in the target PI-System successful. Here I've used following URL:

http://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c

In SOAP XI 3.0 Protocol I get a "BubbleException" with the following error in the log viewer
"com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.ConfigException: No sender agreement configured that matches the message's header fields"

So I think the target-URL in the Receiver SOAP Adapter isn't correct and in SAP note 856597 the following URL should be used:

http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverP...

But I get the same error message here.

[nageswararao_v2 · Accepted solution]

Hello Fatih and Claudia,

As Fatih said above we were also used SOAP1.1 with channel URL: http://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c to over come this problem.

Sorry for late reply...

Thanks & Regards,

Nagesh

[sewoon_oh]

In our project case, WEB (SOAP) system to ERP (Proxy) scenario, user profile in ERP something wrong.

So we added some authority to user in ERP, then problem solved.

---------------------------------------------

SOAP: Error occurred:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code =
500 [null "null"]

---------------------------------------------

[Former Member]

I faced an issue almost the same as the current one discussed here:

channel log:

Message log:

Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method java.lang.String.trim() of a null object returned from com.sap.aii.af.service.cpa.Channel.getValueAsString(java.lang.String)

Solution:

I did change Message protocol from XI 3.0 to SOAP 1.1 save & activate, but i got Authorization error cause SOAP 1.1 dos not use any authorization . I changed the protocol back to XI 3.0 retyped Authentication Data , saved and Activate , it worked  and the issue solved ..

Enjoy..

Patrick

[baskar_gopalakrishnan2]

simple approach is to test the second PI webservice using soapUI instead sending via first PI.  This way you will know the problem related to the data or endpoint connectivity failure error. Copy the data you sent from first PI and pass it via soapui or xmlspy.

[nageswararao_v2]

Hi Baskar,

     Thanks for reply, We are sure data is not the issue since we are using standard IDoc XML and implemented this package more customer in dual stack systems using XI adapter.

     For this customer system having single stack PI, Here No XI adapter so we are using SOAP adpter with XI 3.0 protocol. and In HTTP destination the below URL we are using to connect the second PI:

• http://xxxxhost:yyyyport/XISOAPAdapter/MessageServlet?ximessage=true.

Thanks & Regards,

Nagesh

[former_member184789]

Hi,

In the SOAP Adapter with XI 3.0 protocol i.e Proxy channel, you would have provided a User ID & pwd of a User in target system. Check the authorization for this User. Did you ping the Communication Channel in NWA?

[nageswararao_v2]

Hi Adarsh,

     Thanks for reply, Yes we are using HTTP RFC Destination to connect the target system with user credentials. And we are able to ping the channel successfully in NWA...

Thanks & regards,

Nagesh

[former_member184789]

Hi

could you check if the below thread helps you:

http://scn.sap.com/thread/3253448

[nageswararao_v2]

Hi Adarsh,

• Thanks for quick reply, I was gone through that link also but still same error we are getting...

Could anybody please help me out from this issue...

Thanks & Regards,

Nagesh