db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendleton.de...@gmail.com>
Subject Re: Need help understanding a database deadlock that was detected
Date Wed, 02 Sep 2015 23:03:40 GMT
> Lock : ROW, MANAGED_HARDWARE_SUMMARY, (47,8)
>    Waiting XID : {50633, S} , CSEM, SELECT CHASSIS_9145E10G_ID, IP_STR, DS.TEMPLATE,
DS.SYSTEM_TEMPLATE, DS.ADMIN_ENABLED, DS.ALIAS_NAME, DS.MODEL, DS.HARDWARE_VERSION, DS.ACTIVE_FIRMWARE,
DS.INACTIVE_FIRMWARE, DS.BOOTCODE, CONTACT, CIRCUIT, CIRCUIT_2,
> LOCATION, HAS_MGMT_PORT, HAS_CONSOLE_PORT, POWERSUPPLY_A_MODEL, POWERSUPPLY_B_MODEL,
HAS_FANS, HAS_TEMP_SENSOR, HAS_USER_XFP_CONNECTOR, USER_XFP_MODEL, HAS_NET_XFP_CONNECTOR,
NET_XFP_MODEL, IP, SYNCHRONIZING, LAST_SYNCHRONIZED_TIMESTAMP, CREATED_TIMESTAMP,
> ADMIN_STATE_TIMESTAMP, MACADDRESS_STR, PEER_MACADDRESS_STR, ZTP_STAGED, ZTP_STAGED_TIMESTAMP,
ZTP_PROVISIONING_STATE, ZTP_PROVISIONING_STATE_TIMESTAMP, R2_MODEL FROM --DERBY-PROPERTIES
joinOrder=FIXED
> PKG_9145E10G.DEVICE_SUMMARY DS JOIN CORE_V1.MANAGED_HARDWARE_SUMMARY MHS ON DS.CHASSIS_9145E10G_ID
= MHS.MANAGED_HARDWARE_ID WHERE DS.CHASSIS_9145E10G_ID = ?
>    Granted XID : {50631, X}

50631 has an exclusive lock on row 8 of page 47 of table MANAGED_HARDWARE_SUMMARY.

50633 is trying to get a share lock on that same row, and is hence blocked.

> Lock : ROW, DEVICE_SUMMARY, (4,8)
>    Waiting XID : {50631, X} , CSEM, UPDATE PKG_9145E10G.DEVICE_SUMMARY SET ZTP_STAGED_TIMESTAMP
= ?, ZTP_STAGED = ? WHERE (ID = ?)
>    Granted XID : {50633, S}

50633 has a share lock on row 8 of page 4 of table DEVICE_SUMMARY.

50631 is trying to get an exclusive lock on that same row,
and is hence blocked.

So in the MANAGED_HARDWARE_SUMMARY table, 50633 is waiting on 50631.

And in the DEVICE_SUMMARY table, 50631 is waiting on 50633.

Deadlock.

thanks,

bryan



Mime
View raw message