[ https://issues.apache.org/jira/browse/CONNECTORS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wright updated CONNECTORS-876: ----------------------------------- Component/s: (was: LiveLink connector) Lucene/SOLR connector Description: When Solr throws an error, it would be great if the connector could include enough diagnostic information in the exception and/or log so that people could chase down the originating document in question. Right now all you get is: {code} Exception tossed: Repeated service interruptions - failure processing document: Server at https://llsrchsolqa1:8443/solr/Lisa returned non ok status:500, message:Internal Server Error org.apache.manifoldcf.core.interfaces.ManifoldCFException: Repeated service interruptions - failure processing document: Server at https://llsrchsolqa1:8443/solr/Lisa returned non ok status:500, message:Internal Server Error at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:586) Caused by: org.apache.solr.common.SolrException: Server at https://llsrchsolqa1:8443/solr/Lisa returned non ok status:500, message:Internal Server Error at org.apache.manifoldcf.agents.output.solr.ModifiedHttpSolrServer.request(ModifiedHttpSolrServer.java:311) at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:180) at org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117) at org.apache.manifoldcf.agents.output.solr.HttpPoster$IngestThread.run(HttpPoster.java:919) {code} was: When LAPI throws an error, it would be great if the connector could include enough diagnostic information in the exception and/or log so that people could chase down the document in question. Summary: Solr connector: when HTTP error code 500 is returned, the error message should contain some identifying information (was: Livelink connector: when HTTP error code 500 is returned, the error message should contain some identifying information) > Solr connector: when HTTP error code 500 is returned, the error message > should contain some identifying information > ------------------------------------------------------------------------------------------------------------------- > > Key: CONNECTORS-876 > URL: https://issues.apache.org/jira/browse/CONNECTORS-876 > Project: ManifoldCF > Issue Type: Bug > Components: Lucene/SOLR connector > Affects Versions: ManifoldCF 1.4.1 > Reporter: Karl Wright > Assignee: Karl Wright > Fix For: ManifoldCF 1.6 > > > When Solr throws an error, it would be great if the connector could include > enough diagnostic information in the exception and/or log so that people > could chase down the originating document in question. Right now all you get > is: > {code} > Exception tossed: Repeated service interruptions - failure processing > document: Server at https://llsrchsolqa1:8443/solr/Lisa returned non ok > status:500, message:Internal Server Error > org.apache.manifoldcf.core.interfaces.ManifoldCFException: Repeated service > interruptions - failure processing document: Server at > https://llsrchsolqa1:8443/solr/Lisa returned non ok status:500, > message:Internal Server Error > at > org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:586) > Caused by: org.apache.solr.common.SolrException: Server at > https://llsrchsolqa1:8443/solr/Lisa returned non ok status:500, > message:Internal Server Error > at > org.apache.manifoldcf.agents.output.solr.ModifiedHttpSolrServer.request(ModifiedHttpSolrServer.java:311) > at > org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:180) > at > org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117) > at > org.apache.manifoldcf.agents.output.solr.HttpPoster$IngestThread.run(HttpPoster.java:919) > {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)