[
https://issues.apache.org/jira/browse/CONNECTORS-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-998:
-----------------------------------
Attachment: edited.manifoldcf.log
This log is a partial ManifoldCF database debugging log, showing the problem.
I've included annotations, all of which start with ">>>".
You read the log as follows:
For each ManifoldCF thread that does a database activity, a "Requesting" line
is emitted. Then, a secondary thread is spun up to execute that activity,
which has "actual query" and the parameters to the query. At the end of the
query, the ManifoldCF thread logs a commit and logs the end of the transaction.
All of this takes a bit of practice to learn how to read, especially since
there are multiple threads active at once.
> FileSystem connector derby tests lock up when non-empty version string is
> used for directories
> ----------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-998
> URL: https://issues.apache.org/jira/browse/CONNECTORS-998
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
> Affects Versions: ManifoldCF 1.7
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.7
>
> Attachments: edited.manifoldcf.log
>
>
> The reason for the lock-up seems to be multiple threads trying to change the
> same records in the JobQueue table. One thread is adding references, and
> another thread is marking the record as "complete". The starting record
> status field seems to be the same, despite transactions and FOR UPDATE
> clauses on both queries.
> Since this requires incorrect file connector code, I will be creating a
> branch to explore it in more detail, and perhaps open a Derby ticket. I also
> updated the Derby version to the current release in hopes that this may have
> fixed the problem.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
