> 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 -- 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
