cancel
Showing results for 
Search instead for 
Did you mean: 

Not working proxy with attachment http 500 BubbleException

Former Member
0 Kudos

Hello Experts,

We are  migrating from 7.3 dual stack to 7.4 single stack.There we have one interface which is from SFTP to ECC (via proxy).

We are sending one attachment with proxy.When testing we are getting the error in cc.

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


In log the error is


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>XIServer</SAP:Category><SAP:Code area="INTERNAL">ATTRIBUTE_INITIAL</SAP:Code><SAP:P1>Manifest cid:cid:payload-ca3f407c135e11e6b0a0000002c105be-att1@sap.com</SAP:P1><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:Stack>Attribute Manifest cid:cid:payload-ca3f407c135e11e6b0a0000002c105be-att1@sap.com is initial
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hide Full Message

In PO we have receiver cc where we are using desiantion as mentioned in NWA,it working for other interfaces ,but not for this one.

any help will be greatly appreciated.

Regards

Naveen

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Thanks all for ur suggestion and help,Actual problem was with the java code that is generating the attachment.

Regards

Naveen

Answers (3)

Answers (3)

Former Member
0 Kudos

hi both,

the code is already implemented and also value of xiadapter.version.minor also set to 0.

@praveen please find the mainfest attached.

former_member186851
Active Contributor
0 Kudos

Hello Naveen,

One more check,Your attachement is not empty right?

Former Member
0 Kudos

Hello Raghu,

Yes my attachment is not empty.It has values.

Thanks,

nitindeshpande
Active Contributor
0 Kudos

Hi Naveen,

Can you please check if your HTTP destination to ECC system is working fine? Please note the HTTP response must be 500 once you ping the HTTP destination.

Regards,

Nitin

former_member186851
Active Contributor
0 Kudos

Ok Naveen,

Everything seems to be Fine.

Check for the cache and  try re-configuring then.

@ Nitin.Guess destination should not a problem as is other scenarios are working fine for proxy.

Former Member
0 Kudos

Hi Nitin,

Yes the HTTP destination has been giving the response as 500 on pinging.

former_member186851
Active Contributor
0 Kudos

Hello Nithin,

This is error response,

Check the host and details maintained in the destination.

nitindeshpande
Active Contributor
0 Kudos

Raghu,

Once you connect from Java system to ABAP system, the response you receive is 500. The response is correct.

Regards,

Nitin

nitindeshpande
Active Contributor
0 Kudos

Hello Naveen,


Are you using standard proxy? Can you please check the namespace of your proxy interface and the namespace in your payload?

I guess they are not matching, hence it is not able to find the right structure.

Regards,

Nitin

Former Member
0 Kudos

hi Raghu,

i did cache referesh full and then tried,but again same issue.

Regards

Naveen

former_member182412
Active Contributor
0 Kudos

Hi Naveen,

How are creating the attachment in PI? Are you picking up the file using additional file option in SFTP adapter or are you converting main payload into attachment via java mapping??

Regards,

Praveen.

Former Member
0 Kudos

hi praveen,

we are picking the file from sftp and then coverting main payload into attachment via java mapping.

regards

naveen

Muniyappan
Active Contributor
0 Kudos

is the receiver proxy code implementation is done? recently i was facing the same issue. after proxy is implemented  it started to work.

former_member186851
Active Contributor
0 Kudos

Muni if the proxy code is not implemented it will fail in ECC (SXMB_MONI) right?

Muniyappan
Active Contributor
0 Kudos

it holds true for classical. but with ICO, receiver soap channel(xi protocol) it is behaving different.

.

former_member186851
Active Contributor
0 Kudos

Ok Muni..Thanks.

@ Naveen.

Check that link and for the code implementation as Muni suggested.

former_member186851
Active Contributor
0 Kudos

Hello Naveen,

Try creating virtual receiver as mentioned in the below link

BUBBLE EXCEPTION during Processing | SCN

Former Member
0 Kudos

HI Raghuram,

Its already created with virtual receiver .

Thnx

former_member186851
Active Contributor
0 Kudos

Ok Naveen,

Check the below discussion and see if it helps

former_member182412
Active Contributor
0 Kudos

Hi Naveen,

Check the manifest of the message it is complaining about this, it should be like below for not attachment. can you paste your manifest here?

Also check this sap note 1501345 - XI runtime: Manifest <attachment-name> is initial

Regards,

Praveen.