JDBC DB2 UPDATE_INSERT Delay

Question

Hello everybody,
I have the following asynchronous scenario
SAP ECC IDOC -> SAP PI 7.11 - > JDBC DB2 Database
now, I receive ARTMAS Idoc's from ECC and do mapping to create XML Query statements, now mapping is working correclty and UPDATE_INSERT statements also, the problem is that the Adapter Engine sends the statements, the database recieves them and process them in milliseconds each, and when the database finished ,PI keeps waiting for something for 2 minutes and 6 seconds each message, I already did the following:
1.- Tried Idoc packaging in development in Mapping to send as much statements as I can considering bandwith, but the problem remains.
2.- I tried sending only one stamente and takes the same time.
3.- I already disabled in SAP PI the acknowledge for the Idocs and times are the same.
4.- I already tried the option "Disconnect from database after each message" with this checkbox activated and deactivated, and the times still the same.
5.- Already tried the Isolation level with all different options and times still the same.
6.- Pool waiting advanced parameter not defined so it should take the default that is 5 seconds, but I'm not sure that parameter can control that, do you think?
The readl problem after monitoring both PI and the database is that the database finishes really fast but PI still waits for something I don't know what for more than two minutes for each message, this creates queueing of messages in the Adapter Engine for this interface, cause each message takes this time.
I thank in advance your attention and recomendations.
Regards,
Julio

Answer 1

PI should be waiting back the response with the count of recordsinserted or updated. and this delay corresponde with the time that DB take to insert or update the fields i think
see this. i took it from help sap.
did you configured the response mapping?
action=UPDATE_INSERT
The statement has the same format as for the UPDATE action. Initially, the same action is executed as for UPDATE. If no update to the database table can be made for this action (the condition does not apply to any table entry), values of the table described in the <access> element are inserted in accordance with the description of the action INSERT. <key> elements are ignored in this case.
The response document has the following format; one of the two values is always 0 because either an UPDATE or an INSERT action is always executed:
<update_count>count</update_count>
<insert_count>count</insert_count>