Skip to Content

Persistence: Reprocessing Synchronous messages in error

Hi,

OSS Note 872388 - "Troubleshooting Archiving and Deletion in PI" states that synchronous messages in error are persisted and can be reprocessed:

Per default only asynchronous messages (EO and EOIO) will be persisted on the ABAP and Java side. Synchronous messages (Best Effort) will only be persisted if an error occurs during processing or if the parameter LOGGING_SYNC (ABAP only) is set. Setting LOGGING_SYNC is not recommended to reduce processing overhead.

It is not clear if the above applies to the synchronous request or response message? or both?

My question is:

1) if a synchronous SOAP request comes into PI and the mapping fails, will the request message persist so the XML can be edited and restarted?

2) what happens to the response message? surely the pipe has been lost and the response will have no significance?

Your input appreciated.

Che

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Jan 08, 2014 at 01:42 PM

    Hi Che,

    1) if a synchronous SOAP request comes into PI and the mapping fails, will the request message persist so the XML can be edited and restarted?

    Synchronous messages cant be reprocessed because the sender cant wait eternally.

    2) what happens to the response message? surely the pipe has been lost and the response will have no significance?

    Self explanatory with the later answer.

    Regards.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 08, 2014 at 02:02 PM

    Fast and comprehensive answers from both Amit and Iñaki. Amit do you mind if I reward Iñaki as his original reply came in just before yours.

    Che

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Amit,

      From my understanding PI will return a system response (HTTP 200) immediately on receiving the SOAP request. This may then be followed by a system response for failure if the request could not be delivered to the end point. In case of mapping error then no system level response will be returned. I thought mapping exceptions do not automatically generate a system level error response? or do they? HTTP 500 Error?

      3rd party SOAP request -> PI -> ECC

      Che

  • Posted on Jan 08, 2014 at 01:42 PM

    Hello,

    >>It is not clear if the above applies to the synchronous request or response message? or both?

    1) if a synchronous SOAP request comes into PI and the mapping fails, will the request message persist so the XML can be edited and restarted?

    >>Yes, request message will persist in PI but u cannot edit/restart that failed sync request message - that's how sync call works. The sender system has to reinitiate the call.

    2) what happens to the response message? surely the pipe has been lost and the response will have no significance?

    >>Yes, since request has been failed so no response message will come into PI

    Thanks

    Amit Srivastava

    Add a comment
    10|10000 characters needed characters exceeded

    • Hello,

      >>What is the point of persisting the synchronous message? is it only for short term logging?

      Failed sync messages are persisted so that u can monitor them and identify the root cause of the error😊.

      >>So only asynchronous messages may be edited and restarted.

      Yes

      Thanks

      Amit Srivastava

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.