Skip to Content

HTTP Destination error from PI single stack to ECC

Hi All,


We are using SOAP channel with Transport Protocal as HTTP and Message Protocol as XI 3.0 with Addressing Type as HTTP Destination and HTTP Destination as ECC100H.


However, suddenly the interface stopped working and giving the below error. The User is not locked in ECC and the RFC Destination ping to the same ECC system is working fine.


Error Log below.


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


MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]


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"]


Exception caught by adapter framework: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]


I did not find any link for single stack PI to ECC connection details.


Thanks,

Shaibayan

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Sep 15, 2016 at 03:57 PM

    Shaibayan,

    • Service interface is activated in PI and check in ECC if proxy is generated.
    • Any changes in the USER roles mentioned in http destinations?

    Br,

    Manoj

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 15, 2016 at 04:43 PM

    This is could be due to some issue in SM59 parameters.

    Also the user should have the role-SAP_XI_APPL_SERV_USER

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 15, 2016 at 06:23 PM

    Hi Shaibayan,

    Not sure if this will help you at all but we faced this same issue when we tried to use principal propagation in conjunction with the basic message server setup for our ECC system. The failure would happen when the message server would issue a temporary redirect to the appropriate ECC node which did not work together with principal propagation. We had to abort the use of principal propagation at that point because SAP recommends using Web Dispatcher for such a scenario which we did not have at the time. No idea if this is anything like your scenario but wanted to share in case it might help you out.

    Regards,

    Ryan Crosby

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.