[
https://issues.apache.org/jira/browse/CONNECTORS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-875:
-----------------------------------
Attachment: CONNECTORS-875.patch
> 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)
