Hi Luis, This is a known behavior, it seems CAS management is also using the scheduled reloading of all service definitions just like CAS server itself. The effect at CAS management is, that changes are not immediately reflected in the GUI. You may try the reload button to see the changes.
Other than that, feel invited to improve the CAS management GUI any time by creating PRs at https://github.com/apereo/cas-management. Regards Martin On Friday, May 10, 2024 at 11:40:05 AM UTC+2 Luís Costa wrote: > CAS management (with MongoDB as service registry) delay on showing changes > to configurations > > Hello community, > > > I’m having some problems related with CAS management web app and MongoDB > as Service Registry. > > I'm using CAs server 6.6.14, CAS management 6.6.4 and MongoDB 4.0.5. > > I also have other technologies involved, like docker and apache web server. > > > One of the problems is related with saving configuration changes. > > Everytime I make changes to the configurations (eg CAS Services => Basics > => Description), those changes are not immediately reflected on CAS > management screens. After some debugging it seems that those changes take > some time (some seconds, a minute or more) to be reflected on CAS > management. > > I found no errors on MongoDB log, /var/log/mongod.log and on CAS > management log, with trace on several packages. > > It seems that this problem is related with MongoDB configurations, > technology which I don't know well. > > Initially I’ve tried to change CAS management documented configs > “cas.service-registry.mongo.read-concern=LINEARIZABLE” and > “cas.service-registry.mongo.write-concern=MAJORITY”, but it seems they are > ignored by MongoDB initialization code. > > Then I tried to force Read Concern config and Write Concern config on the > connection string, like this, > “mongodb://<user>:<password>@mongodb:<port>/<database>?readConcernLevel=linearizable&w=majority&wtimeoutMS=5000”, > > hoping to prioritize data consistency over performance. This configuration > seems to be applied, but the delay behaviour keeps happening. > > > This may be more a MongoDB question than a CAS question, but I ask if > someone had this problem. > > > Kind Regards, > > Luís Costa > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/e092ec93-9ae9-426a-bb16-b87d7fffe433n%40apereo.org.
