cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Issue

Former Member
0 Kudos

Hi,

We had an issue with production where the jdbc adapter picked up the message early morning 2:30 and delivered to IS.  It is an JDBC to IDOC scenario.

I can see the end time as 4:30. When analysed further into the payload, The inbound message soap header->runtime shows as 2:30 and followed by that all the other pipeline steps shows as 4:30.

I have checked the queues, sm21 logs and could not find any clue.  How do we check what went wrong and the reason for this delay.

Since it did not deliver the idocs on time, it missed the batch job posting in ECC.

Any help on this would be useful.

Regards

Anandh.B

Accepted Solutions (1)

Accepted Solutions (1)

rajasekhar_reddy14
Active Contributor
0 Kudos

it looks some issue with messaging system(mainly integration engine) like response time was not good, take help from basis and analyse the log files.

Response time also depends on load on PI server, are you facing the same issue oftenly? if yes then create a oss note and SAP sugegsts some solution(may be upgrading support pack).

Answers (1)

Answers (1)

SudhirT
Active Contributor
0 Kudos

Hi Anandha,

Check the inbound message soap header -> Performance Header section .

If the message was delivered to IE on time 2:30 then you can analyze all pipeline steps here and can check to see which one caused the delay.

Thanks!