[
https://issues.apache.org/jira/browse/CONNECTORS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892057#comment-13892057
]
David Morana commented on CONNECTORS-875:
-----------------------------------------
the job failed again with lapi errors: failed to get document version. Couldn't
flush the socket.
Is it time to apply the refactor patch too?
Normally we can just restart the crawl but this time it hung on "starting up".
I tried aborting the job but that just hung on there for at least 10 minutes
here's the error:
{code}
2014-02-04 19:29:47,066 [Worker thread '12'] WARN org.apache.manifoldcf.jobs-
Pre-ingest service interruption reported for job 1386179485136 connection 'LISA
- ssl - QA - repo': Could not flush socket
2014-02-04 19:29:47,068 [Worker thread '47'] ERROR
org.apache.manifoldcf.crawlerthreads- Exception tossed: Repeated service
interruptions - failure processing document: Could not validate LAPI response
org.apache.manifoldcf.core.interfaces.ManifoldCFException: Repeated service
interruptions - failure processing document: Could not validate LAPI response
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:586)
Caused by: com.opentext.api.LLCouldNotConnectException: Could not validate LAPI
response
at com.opentext.api.LLConnect.goodResponse(Unknown Source)
at com.opentext.api.LLConnect.executeHTTP(Unknown Source)
at com.opentext.api.LLConnect.execute(Unknown Source)
at com.opentext.api.LAPI_DOCUMENTS.FetchVersion(Unknown Source)
at
org.apache.manifoldcf.crawler.connectors.livelink.LivelinkConnector$DocumentReadingThread.run(LivelinkConnector.java:7506)
2014-02-04 19:29:47,111 [Worker thread '35'] WARN org.apache.manifoldcf.jobs-
Pre-ingest service interruption reported for job 1386179485136 connection 'LISA
- ssl - QA - repo': Could not flush socket
2014-02-04 19:29:47,173 [Worker thread '10'] WARN org.apache.manifoldcf.jobs-
Pre-ingest service interruption reported for job 1386179485136 connection 'LISA
- ssl - QA - repo': Could not flush socket
2014-02-04 19:29:47,206 [Worker thread '22'] WARN org.apache.manifoldcf.jobs-
Pre-ingest service interruption reported for job 1386179485136 connection 'LISA
- ssl - QA - repo': Could not flush socket
2014-02-04 19:29:58,768 [Worker thread '38'] WARN org.apache.manifoldcf.jobs-
Pre-ingest service interruption reported for job 1386179485136 connection 'LISA
- ssl - QA - repo': Could not validate LAPI response
2014-02-04 19:29:58,768 [Worker thread '40'] WARN org.apache.manifoldcf.jobs-
Pre-ingest service interruption reported for job 1386179485136 connection 'LISA
- ssl - QA - repo': Could not validate LAPI response
{code}
> LiveLink connector: LAPI exceptions not always caught
> -----------------------------------------------------
>
> Key: CONNECTORS-875
> URL: https://issues.apache.org/jira/browse/CONNECTORS-875
> Project: ManifoldCF
> Issue Type: Bug
> Components: LiveLink connector
> Affects Versions: ManifoldCF 1.4.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.6
>
> Attachments: CONNECTORS-875.patch, refactor.patch
>
>
> LAPI has the ability to communicate via HTTP with the LiveLink server.
> Unfortunately, if something goes wrong on the server side, LAPI does not
> behave well and throws all sorts of runtime exceptions. For example:
> {code}
> 2014-01-30 17:44:17,773 [Worker thread '43'] FATAL
> org.apache.manifoldcf.crawlerthreads- Error tossed: For input string:
> "<h2>500"
> java.lang.NumberFormatException: For input string: "<h2>500"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:492)
> at java.lang.Integer.<init>(Integer.java:677)
> at com.opentext.api.LLConnect.readResponseHeaders(Unknown Source)
> at com.opentext.api.LLConnect.executeHTTP(Unknown Source)
> at com.opentext.api.LLConnect.execute(Unknown Source)
> at com.opentext.api.LAPI_DOCUMENTS.GetObjectInfo(Unknown Source)
> at
> org.apache.manifoldcf.crawler.connectors.livelink.LivelinkConnector$GetObjectInfoThread.run(LivelinkConnector.java:6370)
> {code}
> Other examples include ArrayIndexOutOfBoundsException, etc.
> It would be good to catch these and deal with them in a saner way than
> killing off and restarting the worker thread.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
