on 07-07-2017 12:27 PM
Hi All,
We have a asynchronous webservice to ECC Proxy scenario which has been working perfectly fine until we moved it to the new PI 7.3.1 environment.
One of the third party system in the client landscape is given PI end-point URL which is mapped to the ECC Proxy message: 3rd party <SOAP> PI <ABAP PROXY> ECC
The asynchronous scenario which was working without error until we moved it to a new PI upgraded environment where it started giving the below error:
The channel is set to QoS: Exactly Once - even in the old environment and there has been no change to this object.
Please, kindly let us know thoughts and if you happen to encounter similar issue - the best possible way to resolve ?! Your help is greatly appreciated.
Thank you,
Rithvik
ErrorDetails:
<?xml version="1.0" encoding="UTF-8" standalone="true"?> <!-- Inbound Message --> -<SAP:Error xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1"> <SAP:Category>XIServer</SAP:Category> <SAP:Code area="INTERNAL">ATTRIBUTE_WRONG_VALUE</SAP:Code> <SAP:P1>Message->ReliableMessaging->QualityOfService</SAP:P1> <SAP:P2>BE</SAP:P2> <SAP:P3/> <SAP:P4/> <SAP:AdditionalText/> <SAP:Stack>Attribute Message->ReliableMessaging->QualityOfService has invalid value BE </SAP:Stack> <SAP:Retry>M</SAP:Retry> </SAP:Error>
Change the quality of service in Sender channel to EO it should work.
EO is for async communicaitons.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After checking what Manoj mentioned, make sure the URL you have provided to the third party has &&QualityOfService=ExactlyOnce embedded.
Thanks,
Apu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rithvik,
Can you check the end point URL which third party is using does not have QOS=BE in the URL ? If yes then remove it.
And also please check the service interface are still async there was an issue in the past where service interface where changing from async to sync after upgrade.
2321882 - ATTRIBUTE_WRONG_VALUE in Receiver Soap Adapter
Br,
Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.