[
https://issues.apache.org/jira/browse/CONNECTORS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897868#comment-13897868
]
Florian Schmedding commented on CONNECTORS-880:
-----------------------------------------------
Unfortunately, there are still the same errors with the new revision. I'm using
the manifoldcf-combined-service.war under Tomcat 7 but I don't know if there
are multiple agents processes running (according to the build doc I think there
should be only one) nor how to check that.
About the Solr connection:
Connection status: Connection working (View Output Connection Status)
I cannot find any wrong parameter, Solr admin is working fine. The ping request
from manifold is visible in the access log:
127.0.0.1 - - [11/Feb/2014:15:08:52 +0100] "GET
/solr/default/admin/ping?wt=xml&version=2.2 HTTP/1.1" 200 1329
Other manually executed requests work as well:
0:0:0:0:0:0:0:1 - - [11/Feb/2014:15:12:21 +0100] "GET
/solr/default/update?commit=true HTTP/1.1" 200 160
However, no further requests from manifold are logged. Did the Solr connection
handler change? I'm using Solr 4.3.1.
*********
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)
**********
WARN 2014-02-11 15:02:28,180 (Job notification thread) - Notification service
interruption reported for job 1392112746052 output connection 'solr localhost':
IO exception during commit: The target server failed to respond
org.apache.manifoldcf.agents.interfaces.ServiceInterruption: IO exception
during commit: The target server failed to respond
at
org.apache.manifoldcf.agents.output.solr.HttpPoster.handleIOException(HttpPoster.java:477)
at
org.apache.manifoldcf.agents.output.solr.HttpPoster.handleSolrServerException(HttpPoster.java:357)
at
org.apache.manifoldcf.agents.output.solr.HttpPoster.commitPost(HttpPoster.java:304)
at
org.apache.manifoldcf.agents.output.solr.SolrConnector.noteJobComplete(SolrConnector.java:744)
at
org.apache.manifoldcf.crawler.system.JobNotificationThread.run(JobNotificationThread.java:118)
Caused by: org.apache.http.NoHttpResponseException: The target server failed to
respond
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:95)
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:61)
at
org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:254)
at
org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:289)
at
org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:252)
at
org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java:191)
at
org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:300)
at
org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:127)
at
org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:715)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:520)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784)
at
org.apache.manifoldcf.agents.output.solr.ModifiedHttpSolrServer.request(ModifiedHttpSolrServer.java:291)
at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:197)
at
org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117)
at
org.apache.manifoldcf.agents.output.solr.HttpPoster$CommitThread.run(HttpPoster.java:1219)
> Under the right conditions, job aborts do not update "last checked" time
> ------------------------------------------------------------------------
>
> Key: CONNECTORS-880
> URL: https://issues.apache.org/jira/browse/CONNECTORS-880
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework crawler agent
> Affects Versions: ManifoldCF 1.4.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.6
>
>
> When a scheduled job is being considered to be started, MCF updates the
> last-check field ONLY if the job didn't start. It relies on the job's
> completion to set the last-check field in the case where the job does start.
> But if the job aborts, in at least one case the last-check field is NOT
> updated. This leads to the job being run over and over again within the
> schedule window.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
