db2 deadlock timeout

blockSystem.out.println ("interruptered"); } return"Haha"; } }); Executor.execute (Futuretask); //There's something else you can do here.String result=NULL; Try{result= Futuretask.get (Timeunit.milliseconds);//The result is obtained, and the timeout execution time is set at 5 seconds. You can also use Future.get (), do not set the execution timeout time to g

transactionTRX_REQUESTED_LOCK_ID: The lock ID of the waiting transactionTrx_wait_started: The start time of the transaction waitTrx_weight: The weight of the transaction, which reflects the number of rows modified and locked by a transaction, the smaller the weight value is rolled back when a deadlock is found to be rolled backThe process ID in Trx_mysql_thread_id:mysql, corresponding to the ID value in show processlistTrx_query: SQL statement run by

trx_concurrency_tickets:0 Trx_ Isolation_level:repeatable READ trx_unique_checks:1 trx_foreign_key_checks:1 Trx_last_foreign_key_ Error:null trx_adaptive_hash_latched:0 trx_adaptive_hash_timeout:10000 2 rows in Set (0.00 sec) root@127.0.0.1 : Information_schema 13:40:12> select * from innodb_ Locks G *************************** 1. Row *************************** Lock_id:3669d83:49:3:4 # # 2nd transaction Required Lock LOCK_TRX_ID:3669D83 lock_mode:x Lock_type:record lock

The database used in the production environment is DB2. But lately there's been a strange deadlock phenomenon: a SELECT SQL statement always has a deadlock. According to past experience, it is usually the problem of update/delete such as updating SQL statements that will cause deadlocks. And this select SQL statement is a very common SQL, without any large amoun