db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2817) Error messages for deadlocks contain less information than in 10.2
Date Thu, 14 Jun 2007 11:35:27 GMT
Error messages for deadlocks contain less information than in 10.2
------------------------------------------------------------------

                 Key: DERBY-2817
                 URL: https://issues.apache.org/jira/browse/DERBY-2817
             Project: Derby
          Issue Type: Bug
          Components: Services
    Affects Versions: 10.3.0.0
            Reporter: Knut Anders Hatlen
            Priority: Minor


In 10.2, an error message for a deadlock would look like this:

ERROR 40001: A lock could not be obtained due to a deadlock, cycle of locks and waiters is:
Lock : ROW, T, (1,8)
  Waiting XID : {235, S} , APP, select * from t where id = 2
  Granted XID : {238, X} 
Lock : ROW, T, (1,7)
  Waiting XID : {238, S} , APP, select * from t where id = 1
  Granted XID : {235, X} 
. The selected victim is XID : 235.

On trunk, the same deadlock would be reported as

java.sql.SQLException: A lock could not be obtained due to a deadlock, cycle of locks and
waiters is:
Lock : ROW, T, (1,8)
  Waiting XID : {org.apache.derby.impl.services.locks.LockSpace@94884d, S} 
  Granted XID : {org.apache.derby.impl.services.locks.LockSpace@da6bf4, X} 
Lock : ROW, T, (1,7)
  Waiting XID : {org.apache.derby.impl.services.locks.LockSpace@da6bf4, S} 
  Granted XID : {org.apache.derby.impl.services.locks.LockSpace@94884d, X} 
. The selected victim is XID : org.apache.derby.impl.services.locks.LockSpace@94884d.

That is, the transaction id and the failing statement are not shown.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message