[jira] [Commented] (CONNECTORS-1609) SharePoint connector ignore 503 errors
[ https://issues.apache.org/jira/browse/CONNECTORS-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849069#comment-16849069 ] Julien Massiera commented on CONNECTORS-1609: - [~kwri...@metacarta.com], no the patch does not addresses the problem. It does not focus on the concerned code lines : Error fetching document xx': 503 at org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.fetchAndIndexFile(SharePointRepository.java:1778) ~[?:?] at org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:1542) ~[?:?] at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:399) [mcf-pull-agent.jar:?] > SharePoint connector ignore 503 errors > -- > > Key: CONNECTORS-1609 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1609 > Project: ManifoldCF > Issue Type: Improvement > Components: SharePoint connector >Affects Versions: ManifoldCF 2.12 >Reporter: Julien Massiera >Assignee: Karl Wright >Priority: Critical > Attachments: CONNECTORS-1609.diff > > > During a job, it may occur, for some reasons (related to the SharePoint > server configuration), that some resources of a SP site are not available > (for instance if it requires some credentials to open a resource). In that > case, the SP connector gets a 403 or a 503 response code from the SharePoint. > The problem is that whenever it gets this kind of response code, the job is > aborted with an error. > Since the response codes are clearly identified (403 and 503), it would be > better that, at least for a 503 error, the connector ignores it, continues > the job, and log something into the repo history instead of aborting the job -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CONNECTORS-1609) SharePoint connector ignore 503 errors
[ https://issues.apache.org/jira/browse/CONNECTORS-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848719#comment-16848719 ] Karl Wright commented on CONNECTORS-1609: - Patched attached. Please try and tell me whether it addresses your problem. > SharePoint connector ignore 503 errors > -- > > Key: CONNECTORS-1609 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1609 > Project: ManifoldCF > Issue Type: Improvement > Components: SharePoint connector >Affects Versions: ManifoldCF 2.12 >Reporter: Julien Massiera >Assignee: Karl Wright >Priority: Critical > Attachments: CONNECTORS-1609.diff > > > During a job, it may occur, for some reasons (related to the SharePoint > server configuration), that some resources of a SP site are not available > (for instance if it requires some credentials to open a resource). In that > case, the SP connector gets a 403 or a 503 response code from the SharePoint. > The problem is that whenever it gets this kind of response code, the job is > aborted with an error. > Since the response codes are clearly identified (403 and 503), it would be > better that, at least for a 503 error, the connector ignores it, continues > the job, and log something into the repo history instead of aborting the job -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CONNECTORS-1609) SharePoint connector ignore 503 errors
[ https://issues.apache.org/jira/browse/CONNECTORS-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848713#comment-16848713 ] Karl Wright commented on CONNECTORS-1609: - As discussed in email, 403 actually means something already: "permission denied". As such it is returned when the credentials provided are incorrect. It would be a bad idea to make the connector just keep going when it receives these error codes, in my opinion. > SharePoint connector ignore 503 errors > -- > > Key: CONNECTORS-1609 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1609 > Project: ManifoldCF > Issue Type: Improvement > Components: SharePoint connector >Affects Versions: ManifoldCF 2.12 >Reporter: Julien Massiera >Assignee: Karl Wright >Priority: Critical > > During a job, it may occur, for some reasons (related to the SharePoint > server configuration), that some resources of a SP site are not available > (for instance if it requires some credentials to open a resource). In that > case, the SP connector gets a 403 or a 503 response code from the SharePoint. > The problem is that whenever it gets this kind of response code, the job is > aborted with an error. > Since the response codes are clearly identified (403 and 503), it would be > better that, at least for a 503 error, the connector ignores it, continues > the job, and log something into the repo history instead of aborting the job -- This message was sent by Atlassian JIRA (v7.6.3#76005)
