You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2014/02/11 22:43:20 UTC
[jira] [Resolved] (CONNECTORS-889) JobResetThread seems to be
colliding with other threads, causing unexpected state exceptions
[ https://issues.apache.org/jira/browse/CONNECTORS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wright resolved CONNECTORS-889.
------------------------------------
Resolution: Not A Problem
> JobResetThread seems to be colliding with other threads, causing unexpected state exceptions
> --------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-889
> URL: https://issues.apache.org/jira/browse/CONNECTORS-889
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework crawler agent
> Affects Versions: ManifoldCF 1.5
> Environment: MySQL 5.6
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.5.1, ManifoldCF 1.6
>
>
> Even in a single-agents-process environment, notification failures are producing unknown state exceptions:
> {code}
> DEBUG 2014-02-11 14:54:17,774 (Job reset thread) - Job 1385456433981 now completed
> ERROR 2014-02-11 14:54:17,801 (Job reset thread) - Exception tossed: Unexpected job status encountered: 33
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected job status encountered: 33
> at org.apache.manifoldcf.crawler.jobs.Jobs.returnJobToActive(Jobs.java:1901)
> at org.apache.manifoldcf.crawler.jobs.JobManager.resetJobs(JobManager.java:7726)
> at org.apache.manifoldcf.crawler.system.JobResetThread.run(JobResetThread.java:91)
> DEBUG 2014-02-11 14:54:17,857 (Job notification thread) - Found job 1385456433981 in need of notification
> DEBUG 2014-02-11 14:54:17,862 (Job notification thread) - Found job 1392051994515 in need of notification
> DEBUG 2014-02-11 14:54:17,867 (Job notification thread) - Found job 1392109738731 in need of notification
> DEBUG 2014-02-11 14:54:17,871 (Job notification thread) - Found job 1392112746052 in need of notification
> DEBUG 2014-02-11 14:54:17,891 (Job reset thread) - Job 1385456433981 now completed
> ERROR 2014-02-11 14:54:17,928 (Job reset thread) - Exception tossed: Unexpected job status encountered: 34
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected job status encountered: 34
> at org.apache.manifoldcf.crawler.jobs.Jobs.returnJobToActive(Jobs.java:1901)
> at org.apache.manifoldcf.crawler.jobs.JobManager.resetJobs(JobManager.java:7726)
> at org.apache.manifoldcf.crawler.system.JobResetThread.run(JobResetThread.java:91)
> {code}
> The JobResetThread *should* be the only actor which can transform jobs in the SHUTTINGDOWN state to any other state. But we're seeing indications that this is not true. It could be a MySQL transactional integrity issue.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)