Replying to this old thread just to notice that the issue was finally solved:
https://issues.apache.org/jira/browse/SYNCOPE-1628
Fix will be available with upcoming Syncope 2.1.10.
Regards.
On 04/04/18 07:32, Elena Hong wrote:
Thanks to your help :D
2018년 4월 3일 (화) 오전 1:29, Francesco
Thanks to your help :D
2018년 4월 3일 (화) 오전 1:29, Francesco Chicchiriccò 님이 작성:
> Hi Elena,
> my personal congrats, it seems you've got most of the picture :-)
>
> If your HA setup is correct, in fact, writing any data via REST on node A
> and then read the same data from
Hi Elena,
my personal congrats, it seems you've got most of the picture :-)
If your HA setup is correct, in fact, writing any data via REST on node
A and then read the same data from node B is perfectly fine.
When such data are in fact related to connector configuration (or even
resource
Hi Elena,
What do you exactly mean with "in memory"?
If I correctly got your observation I can suggest that: Syncope, indeed,
saves relevant data on database and does not maintain them in memory.
You should configure properly your Syncope cluster in order to avoid
such problems, especially
How can each syncope servers in high available environment share connector
which saved as spring bean at inmemory?
* My environment.
I set high available with two syncope servers called A, B and nginx.
* My problem
1. I call connector update api to nginx.
2. nginx call syncope server A,