[
https://issues.apache.org/jira/browse/CONNECTORS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892848#comment-13892848
]
Karl Wright commented on CONNECTORS-883:
----------------------------------------
There are two issues in this ticket. First, is making the code take an
alternate path when the notification fails. Second is keeping track of how
many retries etc took place so far someplace in the database. I believe that
the second requires a schema change.
> Framework: Job notification thread does not handle notification service
> interruptions properly
> ----------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-883
> URL: https://issues.apache.org/jira/browse/CONNECTORS-883
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework crawler agent
> Affects Versions: ManifoldCF 1.5
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.6
>
>
> When a job notification fails because of a ServiceInterruption, the
> notification is retried indefinitely. This is incorrect; the notification
> retry should at the very least obey the ServiceInterruption specification
> pertaining to number of retries, retry interval, and failure mode.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
