Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
3.16.1
-
None
-
None
-
SB/KB
Description
The following is an extract of the derby.log file. This shows evidence of deadlock in the derby database; cause seems to be DomainDBDAO.update method.
There is no evidence of deadlock in the application logs!
2011-09-05 09:02:05.473 GMT Thread[DRDAConnThread_7,5,main] (XID = 574387168), (SESSIONID = 10), (DATABASE = harvestdefinitionbasedir/fullhddb), (DRDAID = NF000001.P117-1011338277834039902{5}), Cleanup action starting
2011-09-05 09:02:05.473 GMT Thread[DRDAConnThread_7,5,main] (XID = 574387168), (SESSIONID = 10), (DATABASE = harvestdefinitionbasedir/fullhddb), (DRDAID = NF000001.P117-1011338277834039902{5}), Failed Statement is: UPDATE domains SET comments = ?, crawlertraps = ?, edition = ?,alias = ?, lastAliasUpdate = ? WHERE domain_id = ? AND edition = ? with 7 parameters begin parameter #1: :end parameter begin parameter #2: .jp\.dk.(sendmail|printme=1|\/feed\/rss\/|dd-report-comments|printversion).* :end parameter begin parameter #3: 18153 :end parameter begin parameter #4: null :end parameter begin parameter #5: null :end parameter begin parameter #6: 275982 :end parameter begin parameter #7: 18152 :end parameter
ERROR 40XL2: A lock could not be obtained within the time requested. The lockTable dump is:
2011-09-05 09:02:05.408 GMT
XID |TYPE |MODE|LOCKCOUNT|LOCKNAME |STATE|TABLETYPE / LOCKOBJ |INDEXNAME / CONTAINER_ID / (MODE for LATCH only) |TABLENAME / CONGLOM_ID |
-