It’‘s actually been possible to manipulate the caches prior to 2.6.x but now it’‘s just a bit easier to see the changes you’'ve made in the Admin Console.
In order to tweak the cache sizes and expiration times on-the-fly you’'d have to write some code, however writing code to make changes at startup is not required. Below is a snippet of the Javadocs from the CacheManager:
The size and expiration time for the cache can be overridden by setting Jive properties in the format:
Size: “cache.CACHE_NAME.size”, in bytes.
Expiration: “cache.CACHE_NAME.expirationTime”, in milleseconds.
where CACHE_NAME is the name of the cache.
The following are the available CACHE_NAMEs and where they are used:
multicast / MulticastRouter
filetransfer / ProxyConnectionManager
offlinemessage / OfflineMessageStore
userGroup / GroupManager
pop3 / POP3AuthProvider
ldap / LdapAuthProvider
userCache / UserManager
registeredUsersCache / UserManager
username2roster / UserManager
listsCache / PrivacyListManager
group / GroupManager
vcardCache / VCardManager
Manipulating the caches probably isn’‘t going to be something that you’‘ll need to do very often, such as when you’'ve written your own UserProvider, but it is nice to have access to them.
Hope that helps,