JIRA issue CAS-793 filed ( http://www.ja-sig.org/issues/browse/CAS-793 )
On 7/15/09 2:48 PM, "Andrew Feller" <[email protected]> wrote: > I have broke down and analyzed the 3.3.3 code base and there is no code that > calls the reload() method. I would have assumed that the default services > manager call the reload after a service is added, updated, or deleted. > > I will file a JIRA issue for this as this is something that should be > addressed in some form or fashion. > > Thanks for the insight M, > A > > > On 7/15/09 2:14 PM, "Marvin Addison" <[email protected]> wrote: > >>> I dont know how it is managed with JPA, but with ldap serviceregistry, >>> the ldap is not read until tomcat restart to get service list. >> >> Wow, that is surprising. My code review shows it's a fundamental >> design of DefaultServicesManagerImpl, so it would affect all service >> registry implementations that use it. We've been using >> JpaServiceRegistryDaoImpl on an active-active load balanced cluster in >> our test environment for a while now, and have never noticed a >> problem, but it is restarted frequently which could explain why we >> never noticed this limitation. >> >> The good news is the point that Andrew noted, that >> DefaultServicesManagerImpl implements ReloadableServicesManager, so >> you could set up a Quartz job in one the Spring contexts to call the >> reload() method regularly to sync the other nodes with the one that >> changed. >> >> M -- Andrew Feller, Business System Programmer LSU University Information Services 200 Frey Computing Services Center Baton Rouge, LA 70803 Office: 225.578.3737 Fax: 225.578.6400 -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
