[CONNECTORS-244] Derby deadlocks in a new way on the IngestStatus table, which isn't caught and retried

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: ManifoldCF 0.3
• Fix Version/s: ManifoldCF 0.3
• Component/s: Framework agents process
• Assignee: Karl Wright
• Reporter: Karl Wright
• Created: 30/Aug/11 14:35
• Updated: 30/Aug/11 15:26
• Resolved: 30/Aug/11 15:26

Description

Derby deadlocks when a file system job is run, as follows:

Irrecoverable Derby deadlock at:
at org.apache.manifoldcf.core.database.DBInterfaceDerby.reinterpretException(DBInterfaceDerby.java:803)
at org.apache.manifoldcf.core.database.DBInterfaceDerby.performQuery(DBInterfaceDerby.java:961)
at org.apache.manifoldcf.core.database.BaseTable.performQuery(BaseTable.java:229)
at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.performIngestion(IncrementalIngester.java:388)
at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentIngest(IncrementalIngester.java:364)
at org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ingestDocument(WorkerThread.java:1555)
at org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.processDocuments(FileConnector.java:283)
at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)

The deadlock needs to be caught, backed off, and retried.