on 10-22-2014 3:04 PM
Hello GUYS!
being a new one in SAP PI 7.3,I have developed a few synchronous Interfaces.
but got an error log like:
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"]
PLS suggest how to solve it.
Hi Suparna
I am facing same issue.May I know how you solved he issue.
Regards,
Tibin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guys,
I've noticed that this problems comes out because of an authorization problem.
If I use a user with sap_all for communication between PI to ECC there is no problem.
But if I use a different user with only SAP_XI_APPL_SERV_USER then I get the bubble exception.
Please test it the same way I did to check if it is authorization. I will reply with the correct role when I find out.
Best regards,
Luis.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suparna,
As per your configuration i suppose that you want to send a message to an ABAP proxy, am i worng?
If i am right you can try the next things:
1. Check your configuration in PI and endpoint ECC following this document: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef4...
2. Check in the endpoint any exception in the st22 transation. Enable the monitoring in the ECC endpoint, you can do it in the similar way that you do in PI, and try to check if any message is comming, also you can set an external breakpoint.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes u r ryt!
In the synchronous scenario:
Sender :Third Party
reciver is:Abap proxy
1>with the same config I have run several interfaces which are worKing fine
Let me give u the message log details:
Delivering to channel: CCO_PROXY_XYZ
MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
SOAP: Request message entering the adapter processing with user abc
SOAP: Target url:
XI packaging (bulk mode) is not enabled. Switching to normal processing....
XISOAP: XI message received for processing
Error during parsing the received XMB message.
Error SOAP: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]
Error 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"]
Error 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"]
Error Exception caught by adapter framework: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]
Error Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]
Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]
Error 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"]
Error Message status set to FAIL
Error SOAP: Call failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]
Error SOAP: Call failed: com.sap.aii.af.lib.mp.module.ModuleException: senderChannel 9cdd1b6a5136395ea3076c65b54b880a: Catching exception calling messaging system
IN LOG VIEWER I got the msg like that:
The HTTP Response data is = <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:Category>XIProxy</SAP:Category><SAP:Code
area="ABAP">INTERFACE_SIGNATURE_ERROR</SAP:Code><SAP:P1>ZII_SI_SAP_____RESP</SAP:P1><SAP:P2>MT_SAP______Req</SAP:P2><SAP:P3>urn://3rd Party_SAP/3rd Party/XYZ</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:Stack>Information about the method parameters is missing for the interface ZII_SI_SAP_XYZ_RESP (ABAP interface, request message MT_XYZ_Req, request message namespace urn://3rdParty_SAP/3rd party/XYZ)
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Ibeing 5 months experinced in PI, I am wid no clue !
Pls hlp me
Hi Suparna,
INTERFACE_SIGNATURE_ERROR indicated this issue is related to the XML signature validation in Proxy Runtime environment. You can check the Message Payload in PI Message Monitoring after mapping. (AM in staging). Make sure the Message name and namespace are exactly the same as what you want in Proxy Receiver.
For the moment they are "request message MT_XYZ_Req, request message namespace urn://3rdParty_SAP/3rd party/XYZ".
Best Regards
Lionel
Hi Suparna,
A few cents to Lionel suggestion. Go to ECC and regenerate the proxy.
If you are using a XSD in your outbound interface, take the payload from monitoring and validate it against the XSD. You have on-line free tools for this purpose: Free Online XML Validator Against XSD Schema - FreeFormatter.com
Regards.
Thanx Guys!
but pls help me in below:
I am getting from RWB the message payload after mapping which is entering into reciever sytem
but as u said I have to check the message name and namespace are exactly same as the proxy reciever.
i just want to know how can i check with the proxy reciever 's one?
pls tell me in details
and if it is different then how do i solve the issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check in http://host:port/mdt/channelmonitorservlet the CCs. Maybe exists a problem in parsing some data. (Error 500 is an error on server side).
Also maybe is a problem between abap <> stack java check connections at TX SM59
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suparna,
my suggestion: please check the used communication user whether it has all necessary authentification roles in the receiving system.
Regards
Claudia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.