cancel
Showing results for 
Search instead for 
Did you mean: 

SAP PI resposneonwwaybean

former_member354078
Participant
0 Kudos
488

Hi Experts,

For one of my interface, i have used Async/sync bridge in reciever soap channel . In few cases, messages are getting failed with below reason:

SOAP: request message entering the adapter with user J2EE_GUEST

SOAP: Target url: https://*****.com/api/v16

SOAP: completed the processing

SOAP: continuing to response message 5f7b7a95-e8a6-11e8-a8b4-0000075fc362

MP: processing local module localejbs/AF_Modules/ResponseOnewayBean

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.ConfigException: No sender agreement configured that matches the message's header fields (sender party: "", sender service: "***", interface: "http://***/****_Response_In", receiver party: "", receiver service: "***")

Here receiver system is also sending the response, but after 30 -40 minutes and hence messages are getting failed and then due to system retry parameter, the same message is getting restarted and data posted thrice and causing duplication in the receiver system.

Can you please help on this?

1. How I can make my interface to wait for 30 to 40 minutes to wait for a response , before ResponseOnewayBean step get started.

2. Do i need to use XMBWS.Timeout = 40 min, in my receiver channel or sender channel of another interface, through which we catch resposne.

Accepted Solutions (1)

Accepted Solutions (1)

former_member190293
Active Contributor
0 Kudos

Hi Shivshankar!

What if your scenario takes 45 min (or 50 min, or an hour) to respond next time you'll make a call? I'd strongly suggest to change it to asynchronous mode, when receiver responds to the sender using separate asynchronous interface.

Regards, Evgeniy.

Answers (1)

Answers (1)

former_member190293
Active Contributor

Hi!

If your receiver system sends response after 30-40 minutes - you shouldn't use synchronous communication at all.

Regards, Evgeniy.

former_member354078
Participant
0 Kudos

Hi Evgeniy,

Actually, this is not happening for each and every message. Its happen when PI is writing huge data in receiver system and its taking time to respond back with either true or false response about data posting.

Is there anyway, we can wait PI after posting data and before our resposonewaybean step to come into picture.

Can I use XMBWS.Timeout = 40 Min (in sender CC of next interface to which we are feeding response), or i should use this parameter in reciever channel of main interface (through which we are posting data into receiver system).

Strange thing is that, now after 40 min, resposne message is coming and processing succesfuly