[
https://issues.apache.org/jira/browse/CONNECTORS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282618#comment-14282618
]
Karl Wright commented on CONNECTORS-1143:
-----------------------------------------
If I had to guess, I'd propose that your multi-process setup was using two
distinct properties.xml files, each pointing to a different synchronization
provider (e.g. synch directory or zookeeper instance). That would definitely
make cache invalidations fail to happen properly. For instance, your web
applications might be using different synchronization than your agents
process(es). The database might be shared, but that's insufficient on its own
to handle things like cache invalidation.
> 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
> Components: Framework core
> Affects Versions: ManifoldCF 1.5.1, ManifoldCF 1.6.1, ManifoldCF 1.7.2,
> ManifoldCF 1.8, ManifoldCF 2.0
> Reporter: Daniel Aschauer
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.9, ManifoldCF 2.1
>
>
> 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)
