Quantcast
Channel: SCN : Unanswered Discussions - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 6719

Slow Response

$
0
0

Hi,

 

Within our QA environment we have a scenario which is occasionally being slow to return a response to the sender. Within the trace there is a section:

 

<Trace level="2" type="Timestamp">2015-01-19T18:02:49Z CET Message Level Security for Request (outbound)</Trace>

<Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-CALL_XMS_HTTP">

  <Trace level="2" type="T">Addressing mode: url</Trace>

  <Trace level="3" type="T">Host = hneccqci01s</Trace>

  <Trace level="3" type="T">Port = 8000</Trace>

  <Trace level="3" type="T">Transport protocol = HTTP 1.0</Trace>

  <Trace level="3" type="T">Message protocol =</Trace>

  <Trace level="3" type="T">Path = /sap/xi/engine?type=receiver</Trace>

  <Trace level="2" type="T">Auth mode: basicSAP</Trace>

  <Trace level="3" type="T">Conversion of language from char2 to char1 EN</Trace>

  <Trace level="3" type="T">User = PIAPPLUSER</Trace>

  <Trace level="3" type="T">Client = 300</Trace>

  <Trace level="3" type="T">Language = E</Trace>

  <Trace level="3" type="T">Creating HTTP-client</Trace>

  <Trace level="3" type="T">HTTP-client: creation finished</Trace>

  <Trace level="3" type="T">Security: Basic authentication SAP</Trace>

  <Trace level="3" type="T">Serializing message object...</Trace>

  <Trace level="1" type="T">HTTP Multipart document length: 4427</Trace>

  <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>

  <Trace level="1" type="T">HTTP-client: request sent</Trace>

  <Trace level="3" type="T">HTTP-client: request sent</Trace>

  <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>

  <Trace level="1" type="T">HTTP-client: response received</Trace>

  <Trace level="3" type="T">HTTP-client: checking status code...</Trace>

  <Trace level="1" type="T">sap-xi-messageid 5FB92F35A00511E4C8F1000000BD59A2</Trace>

  <Trace level="1" type="T">HTTP-client: status code = 200</Trace>

  <Trace level="3" type="T">Deserializing message object...</Trace>

  <Trace level="1" type="T">HTTP-client: parsed & response message object created</Trace>

  <Trace level="3" type="T">HTTP-client: closing...</Trace>

</Trace>

<Trace level="2" type="T">Switch back to normalized party (HTTP response)</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="3" type="Timestamp">2015-01-19T18:04:22Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>

 

As you can see it starts this section of the trace at 18:02:49 but doesn't finish until 18:04:22.

 

My question is what could possibly be making this section take so long. Usually it runs straight through with barely a difference in the clock from start to end. However, sometimes it does the above. Is there anyone out there expert enough in PI traces/architecture to say what the above section relates to and why it might be going so slowly.

 

Cheers,

 

PaulC.


Viewing all articles
Browse latest Browse all 6719

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>