manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Morana (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-875) LiveLink connector: LAPI exceptions not always caught
Date Wed, 05 Feb 2014 13:44:09 GMT


David Morana commented on CONNECTORS-875:

Livelink is up
Solr is up.
I can't restart the job on mainfold.
I've rerun the scripts and I've even killed all java and it still hangs there.
I can't start the job or view the livelink connector or authority.
Is there anything else I can try?
I may have to reverse this patch and go back to the earlier revision.

> LiveLink connector: LAPI exceptions not always caught
> -----------------------------------------------------
>                 Key: CONNECTORS-875
>                 URL:
>             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(
>        at java.lang.Integer.parseInt(
>        at java.lang.Integer.<init>(
>        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$
> {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

View raw message