JDBC RECEIVER ADAPTER take too long time in delivering status finally success in PO 750

[chen_nina2]

HI, I met a tough problem ,

I will be very Appreciative if you can give me some advice to solve it.

our scenario is ECC---(SOAP)--PI---(JDBC)---MDW .

it's the log in po message monitor following ,it took more than 16 minutes at the point

''Receiver JDBC adapter: processing started; QoS required: ExactlyOnce'' and at the end this message came to success . I don't know what Influenced the performance and what can I do to avoid this situation.

it was not happened always.it was

just happened sometimes. sometimes it was dealt with very fast.

7/12/2019 01:35:39.308 PMInformationSOAP: Request message entering the adapter processing with user ERPSLD

7/12/2019 01:35:39.308 PMInformationMP: processing local module localejbs/CallSapAdapter

7/12/2019 01:35:39.308 PMInformationApplication attempting to send an XI message asynchronously using connection SOAP_http://sap.com/xi/XI/System

7/12/2019 01:35:39.332 PMInformationTrying to put the message into the send queue

7/12/2019 01:35:39.363 PMInformationMessage successfully put into the queue

7/12/2019 01:35:39.363 PMInformationThe application sent the message asynchronously using connection SOAP_http://sap.com/xi/XI/System. Returning to application

7/12/2019 01:35:39.363 PMInformationThe message was successfully retrieved from the send queue

7/12/2019 01:35:39.366 PMInformationSOAP: Processing completed

7/12/2019 01:35:39.366 PMInformationSOAP: Response message leaving the adapter

7/12/2019 01:35:39.369 PMInformationMessage status set to DLNG

7/12/2019 01:35:39.369 PMInformationTrying to put the message into the send queue

7/12/2019 01:35:39.396 PMInformationMessage successfully put into the queue

7/12/2019 01:35:39.396 PMInformationThe message was successfully retrieved from the send queue

7/12/2019 01:35:39.398 PMInformationMessage status set to DLNG

7/12/2019 01:35:39.399 PMInformationTrying to put the message into the send queue

7/12/2019 01:35:39.426 PMInformationMessage successfully put into the queue

7/12/2019 01:35:39.427 PMInformationThe message was successfully retrieved from the send queue

7/12/2019 01:35:39.429 PMInformationMessage status set to DLNG

7/12/2019 01:35:39.430 PMInformationExecuting Request Mapping

"http://host:port/b11/mes/OM_ECC2MDW_Asy" (SWCV 19f8dfe0a10111e8c904e2950a010267)

7/12/2019 01:35:39.509 PMInformationTrying to put the message into the send queue

7/12/2019 01:35:39.538 PMInformationMessage successfully put into the queue

7/12/2019 01:35:39.538 PMInformationThe message was successfully retrieved from the send queue

7/12/2019 01:35:39.540 PMInformationMessage status set to DLNG

7/12/2019 01:35:39.540 PMInformationTrying to put the message into the send queue

7/12/2019 01:35:39.570 PMInformationMessage successfully put into the queue

7/12/2019 01:35:39.571 PMInformationThe message was successfully retrieved from the send queue

7/12/2019 01:35:39.573 PMInformationMessage status set to DLNG

7/12/2019 01:35:39.573 PMInformationDelivering to channel: CC_MDW_JDBC_Receiver

7/12/2019 01:35:39.573 PMInformationMP: processing local module localejbs/CallSapAdapter

7/12/2019 01:35:39.573 PMInformationReceiver JDBC adapter: processing started; QoS required: ExactlyOnce 7/12/2019 01:51:55.595 PMInformationJDBC Adapter Receiver Channel CC_MDW_JDBC_Receiver: Processing started; party / service ZBS_MDW 7/12/2019 01:51:56.830 PMInformationINSERT INTO ERP_INT_MDW (FABID, SEQ, FTRMI, AUFNR, TXT04, MATRN, VORNR, MAKTX, MENGE, BADH, ZZPSH, SDATE, MENGE_ZS, MENGE_BF, MENGE_ZT) VALUES (MODULE, 0100000019105, to_date(20180101,YYYYMMDD), 000600023338, TECO, 47-7090214, 0010, TOUCH IC_FST1BA59Y_BGA87_7*4.2*0.47MM_59, 0.000 , 1.00000 , 0.000 , TO_DATE(20190711,YYYYMMDD), 0.000 , 0.000 , 0.000 )

hope your reply!thank you so much! If there is something not described clearly ,please tell me.

[former_member104582]

Did you resolve this?

We have a similar issue. Sometimes it takes 15 minutes to process a single message (usually after idle time). During that time the message is in "Delivering" status

[ravicarpenter]

You may also check your message size, jdbc threads availability. You can take help of xpi_inspector for detailed logs.

[chen_nina2]

thank for your reply . the size of message is not large about 885 kb,

the same size of message can be dealt with fast in 1 minute.maybe the jdbc threads was not availability at that time.

Put aside the problem. would you like to give me some advise or method to slove this kind of questions

thank you so much!!!

[ravicarpenter]

What is the transaction isolation level select in receiver channel ? It can be that target table is locked for updates (for consistency purpose) while it is being updated by other process/applications. You can check that from the logs of target database.

[chen_nina2]

Ravi Carpenter ,thank for your reply.

in the receiver channel , transaction isolation level ,I choose 'default'(tartget data base is oracle). I have asked Colleague of target database about the log,and I will tell you the result after they answer me. I hava difficulty to judge problems according to po message log(

I also hava difficulty to judge problems according log of performance monitor) when message has no error just Slow execution .I can't judge which system caused slow execution and if po system caused slow execution how can I locate Problem Points and slove them . Can you recommend some metiral or link for me to study ,thank you so much!!!