[CONNECTORS-225] When using Derby, ManifoldCF incremental indexer sometimes gets a deadlock exception

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
• Fix Version/s: ManifoldCF 0.3
• Component/s: Framework agents process
• Assignee: Karl Wright
• Reporter: Karl Wright
• Created: 24/Jul/11 22:17
• Updated: 24/Jul/11 22:21
• Resolved: 24/Jul/11 22:21

Description

When working with Derby and indexing documents rapidly, sometimes the following deadlock stack trace is thrown:

at org.apache.manifoldcf.core.database.DBInterfaceDerby.reinterpretExcep
tion(DBInterfaceDerby.java:803)
at org.apache.manifoldcf.core.database.DBInterfaceDerby.performQuery(DBI
nterfaceDerby.java:961)
at org.apache.manifoldcf.core.database.BaseTable.performQuery(BaseTable.
java:229)
at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.no
teDocumentIngest(IncrementalIngester.java:1372)
at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.pe
rformIngestion(IncrementalIngester.java:469)
at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.do
cumentIngest(IncrementalIngester.java:365)
at org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ing
estDocument(WorkerThread.java:1587)
at org.apache.manifoldcf.crawler.connectors.webcrawler.WebcrawlerConnect
or.processDocuments(WebcrawlerConnector.java:1222)
at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.proc
essDocuments(BaseRepositoryConnector.java:423)
at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja