[
https://issues.apache.org/jira/browse/CONNECTORS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277027#comment-14277027
]
Karl Wright commented on CONNECTORS-1143:
-----------------------------------------
Hi David,
ManifoldCF does cache connection instances, and is very robust about knowing
when to flush those. You should not need to do anything other than make sure
everything is correctly configured.
The first thing to do is to verify that there's a caching failure. To do that,
simply shut down your agents process(es), and start them up again. If you are
running the single-process example, then shut the whole thing down and start it
up again. See if your jobs succeed on the same documents they failed on
before. If they do, then caching is to blame, and we can do some research to
figure out why. If they continue to fail, then please remember that the
connection checker cannot check *all* possible situations for *all* documents
you intend to crawl. It's a basic sanity check only, for most connection
types. In that case, please supply more details and I can help determine what
the issue is.
Thanks!
> Problem with cached versions of e.g. a repository connection
> ------------------------------------------------------------
>
> Key: CONNECTORS-1143
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1143
> Project: ManifoldCF
> Issue Type: Bug
> Reporter: Daniel Aschauer
>
> I have some issues when i change settings in repository connection:
> I had to change the password for my connection (JIRA), i review the
> connection and it works.
> However the related job(s) keep failing because of an unautorized error. What
> is more i created a new job with the repository connection and it failed too.
> I don't know how these things are kept cached in Manifold. Is this a bug or
> do I have to do some regular cleanup??
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
