I am directly acessing the wildfire database (Yes, I know I should not be doing this!) and I was wondering if there is any way to refresh the servers memory, so it picks up on any of the changes I made to the database. For example, I am manually adding users to the mucAffliliation table, and Wildfire won’'t pick up any of the changes. Am I just shit out of luck on this one?
I did never try the /system-cache.jsp page of the web console but the “Clear Selected” button makes me think that the cache can be cleared so Wifi must re-read the contents of a table. There seems to be no “mucAffliliation” cache, I assume that it is included in “User” or “User Group Cache”.
By refreshing the cache every 5 minutes you might hurt any performance improvement that you typically get by using a cache. But, if your Wildfire installation doesn’'t have to handle a very high load that may be a non-issue for you. There are a couple of different approaches you could take:
Disable the cache all together. This can be done by creating a new system property named, cache.userGroup.size and setting its value to 0 (zero).
Write a plugin that periodically and/or on demand refreshes the cache (you can configue plugins to bypass logging into the Admin Console).
Thanks for the response. Do I need the latest version of WildFire (2.6.2) to access the cache.userGroup.size property? Can I get a list of the properties that deal with cache? I am mostly interested in the cache that deals with the mucAffiliation table and mucMember table.
I am well aware that I should not be accessing the database directly, but I have a project that is pretty much a hack job so far and I only plan on going this route for a little longer, tell I get more time to find some jabber framework api that will suite my needs.