Deadlock occur proxy to jdbcAsync integration?

[polanidevivaraprasad]

Dear Experts,

please help on this issue,

Unable to execute statement for table or stored procedure. INT_GRN_Batch_Char (Structure Statement) due to com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 426) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. INT_GRN_Batch_Char (structure Statement): com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 426) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. INT_GRN_Batch_Char (structure Statement): com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 426) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. INT_GRN_Batch_Char (structure Statement): com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 426) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. INT_GRN_Batch_Char (structure Statement): com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 426) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Regards,

Prasad Polani

[former_member183908]

one simple option is to stop and start the channel to process the messages however always this is not the best practice the reason can be huge volume of data and the same communication channel might be used to call SP/Query.

Thanks

[polanidevivaraprasad]

Hi Pavan,

if we click on restart button then the system error messages in adapter Engine by handwork then it goes.Is any methode need to follow to avoid deadlock?

Thanks & Regards

prasad

[iaki_vila]

Hi Polani,

May be you are overloading your DB, have you tried to set Disconnect from Database After Processing Each Message in your JDBC receiver?

Check this link with your DB team Troubleshooting Deadlocks as well

Regards.

[polanidevivaraprasad]

Hi Iñaki Vila,

if we click on restart button then the system error messages in adapter Engine by handwork then it goes.Is any methode need to follow to avoid deadlock.

Thanks & Regards

prasad

[vkaushik82]

It looks more on Query/SP issue , try running Query/SP on db without using PI see how it behaves.

[polanidevivaraprasad]

Hi Vikrant Kaushik,

if we click on restart button then the system error messages in adapter Engine by handwork then it goes.

Thanks & Regards

prasad