Hi experts,
we have some messages on production environment that are executing during the night and which take way too much time to end.
The scenario is http to file, with a mapping including a RFC lookup;we receive about a hundred messages so the volume is not too high and the size of each xml message is about 20Ko so not too large
The issue is the following, the 'mapping' part takes too much time, here is an extract of the trace of one PI message :
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST"> <Trace level="1" type="Timestamp">2010-05-17T00:16:46Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace> </Trace> <Trace level="1" type="Timestamp">2010-05-17T05:30:27Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace> </Trace>
When I execute mapping test on development environment with the same message, it takes about 15 seconds, whereas it takes much more time on production.
My guess is that there is something really consuming on production environment, but I can't figure out what. I tried checking SM50, but there is nothing abnormal in both environment.
So my question would be, how can I trace in detail what causes the message to take so much time ? How can I identify what is so consuming in term of resources on production environment ?
Any help would be greatly appreciated
Kind regards,
Jamal