Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

LAMS uses the JBossCache. It was primarily chosen as it is the cache that comes with JBoss. It also ties in with Hibernate. We are using the cache as an MBean. This may have to change if we were to change application servers.

When an object is added to the cache, it is added to a node. The nodes are a tree - starting with /, then /org, then /org/lamsfoundation
and so on.

To use the JBoss cache requires four pieces of configuration:

  • The jboss-cache.jar and jgroups.jar need to be copied from /server/all/lib to /server/default/lib.
  • The configuration file local-service.xml needs to be copied to /server/default/deploy. This is done by the copy-files task in the master build script. The definition in the script gives the MBean name as "jboss.cache:service=TreeCache"
  • The cacheManager property cacheObjectName should be "jboss.cache:service=TreeCache". This value must match the name in the local-service.xml file. If the parameter is not set, then the CacheManager class will default to this value.
  • The commonContext.xml file (in lams_common) must configure Hibernate and the LAMS Cache Manager to use the same name (jboss.cache:service=TreeCache) as the local-service.xml file. This has already done.
    • The cacheManager.cacheObjectName should be "jboss.cache:service=TreeCache". If the parameter is not set, then the CacheManager class will default to this value.
    • The should be "org.jboss.hibernate.cache.DeployedTreeCacheProvider". This configures Hibernate to use a cache already set up in JBoss.
    • The should be "jboss.cache:service=TreeCache"

If you want to change the "name" of the cache from "jboss.cache:service=TreeCache" to something else, you will need to change it in three places - once in local-service.xml and twice in commonContext.xml.

Hibernate Second Level Cache

The easiest way to use the cache is to add your objects to the region setup in the local-service.xml. This will trigger the objects to be cached in a second level Hibernate cache. The objects will be added/removed from the cache by Hibernate.

I'll write up later how to do this. I have it working with the content repository, but now I can't work out how I did it!

Programmatically Adding To The Cache

The cache can be used programmatically. The class org.lamsfoundation.lams.cache.CacheManager handles putting objects in and out of the cache. To access this class, set up a reference to the bean "cacheManager" in your Spring context.

The CacheManager expects all entries in the cache to be based on the class name of the object. Please use the methods in the CacheManager to ensure your nodes follow the expected format. If you do not, then the cached objects cannot be managed via the administration page.

For an example of how it may be used, see org.lamsfoundation.lams.usermanagement.service.UserManagementService.getUserById().

Manual Cache Management

An administration page, http://localhost:8080/lams/admin/, has been set up to allow manual cache management. This lists all the current nodes in the hibernate cache. The objects created by Hibernate are a little different to the objects cached manually.

To clear the whole cache, use the Remove option at the top level ("/"). Alternatively, you can remove one of the subnodes, leaving objects from other nodes still in the cache.

Debugging Cache Entries

To monitor the addition and removal of objects from the cache, turn on the cache listener. This may be done by setting UseCacheDebugListener to true in the lams.xml. This should not be turned on in production as it may cause performance issues.

  • No labels