DB_ENTRY_QUEUING Taking longer time

[Former Member]

Hi All,

I was observing the performance header of XI message and found that DB_ENTRY_QUEUING and DB_SPLITTER_QUEUING are taking most of time.

What could the reason and when does this step occur during pipeline service? what is the ways for improving the timing for these step?

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Response

-->

- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205746.475</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205748.975</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205748.975</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205804.163</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205804.163</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205804.225</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205804.225</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205804.225</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205804.225</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205804.288</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205804.288</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205844.039</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205844.055</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205844.055</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205844.055</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205844.055</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205844.055</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">HTTP_SEND</SAP:Name>

<SAP:Timestamp type="begin" host="eimreyxip0">20071213205844.055</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">HTTP_SEND</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205844.664</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>

<SAP:Timestamp type="end" host="eimreyxip0">20071213205844.664</SAP:Timestamp>

</SAP:RunTimeItem>

</SAP:PerformanceHeader>

Ranjeet Singh.

[former_member334189 · Accepted solution]

Dear Ranjeet,

the steps DB_<...>_QUEUEING are the denote the retention of XI messages

in the qRFC queue. In general there are 1-2 such queueing steps during

processing of asynchronous messages.

When a message enters the Integration Server the core engine does some

inital work and the stores the message to an inbound queue (like XBTI...).

In this queue the message remains until all preceding message in that queue

are processed. Then the qRFC reads this message from the queue and

starts XI inbound processing. Hence, DB_ENTRY_QUEUING denotes how

long the message was remaining in the inbound queue. In your example

the message was waiting for 15.188 seconds in the inbound queue to be

processed.

After the split service has completed there is another queueing step. This

time the message is stored to an outbound queue (like XBTO...). When all

preceding messages in that queue are processed the qRFC again

reads the message from the queue and starts XI outbound processing.

So, DB_ENTRY_QUEUING denotes the retention period in the outbound

queue. In your example the message was waiting for 39.751 seconds in

the outbound queue to be processed.

There are various reasons for a message to remain in a queue. A detailed

explanation will go beyond the scope of this answer. Please find a

comprehensive elaboration of this topic in the document "SAP NetWeaver

Process Integration Performance Check - Analysis of Performance Problems

and Possible Solution Strategies", especially sections 4.4.2 and 4.4.3. You

can download this document at

http://service.sap.com/instguidesnw04

-> Operations

-> SAP XI

-> Process Integration Performance Check (SAP XI 3.0/NW 7.0)

(Or you might refer to OSS Note 894509.)

Furthermore I highly recommend the document "Tuning Guide - SAP XI 3.0"

which you can find at the same place as the first document. Here section 3.1

might be of interest for you.

For PI7.0 you can find the Tuning guide at

http://service.sap.com/instguidesNW70

-> Operations

-> Process Integration

-> SAP NetWeaver Process Integration Tuning Guide

Best Regards,

Harald Keimer

XI Development Support

SAP AG, Walldorf

[Former Member · Accepted solution]

Thanks Harald,

I thinks I have got all the required docs for analysis the prblem.

[Former Member · Accepted solution]

Hi Harald,

Thanks for putting the details here, it helped me a lot

Regards,

Ashutosh

[Former Member]

Check this PDF....http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f...              

Page 25

Regards,

Ashutosh

[Former Member]

Hi Ranjeeth,

I am facing a similar issue with message flow from PI to ECC system.They leave PI without delay. But when they come to ECC they are delayed for 40 min.s at the step DB_ENTRY_QUEUING "begin" Any suggestions on how to resolve it? The QoS is EOIO. Would it help to add the parameter eo_inbound_parallel?(This parameter is recommended for EO messages) I couldn't check the SARFC resources during the run-time. I already looked at the doc: [PI Performance check|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782?QuickLink=index&overridelayout=true] I am looking for more input based on how you went about resolving it when you faced this issue. Any input would be appreciated.

Thanks!

Koti

[Former Member]

Dear all,

Thanks for the info.

Now i know what is happening there.

Regards,

khoo Yee Loon

[Former Member]

Hi Experts,

Please help with some answer.

Ranjeet Singh.