JSecurity

I've configured the cluster by creating a custom ehcache.xml file for each webapp (same file for both). However, I'm seem to be getting 2 separate caches, one for each webapp. In my ../tomcat/temp/jsecurity-ehcache directory I have the following entries:
jsecurity-ehcache

• ehcache_auto_created_1216763696593
  • org.jsecurity.realm.text.PropertiesRealm-0-roles.data
  • org.jsecurity.realm.text.PropertiesRealm-0-accounts.data
  • jsecurity-activeSessionCache.data
• ehcache_auto_created_1216763438343
  • org.jsecurity.realm.text.PropertiesRealm-0-roles.data
  • org.jsecurity.realm.text.PropertiesRealm-0-accounts.data
  • jsecurity-activeSessionCache.data
• jsecurity-activeSessionCache.index
• org.jsecurity.realm.text.PropertiesRealm-0-roles.data
• org.jsecurity.realm.text.PropertiesRealm-0-accounts.data
• jsecurity-activeSessionCache.data

I don't know if that tells you anything or not.

Here is my part of my filter code:
public SecurityManager getSecurityManager()
{
    if (this.securityManager == null)
    {
        DefaultRealm realm = new DefaultRealm();
        // DON'T init() it yet, see below.
        DefaultWebSecurityManager dwsm = new DefaultWebSecurityManager();
        EhCacheManager cacheManager = new org.jsecurity.cache.ehcache.EhCacheManager();
        cacheManager.setCacheManagerConfigFile("classpath:ehcache.xml");
        cacheManager.init();
        dwsm.setCacheManager(cacheManager);
        //other SM injected dependencies here
        dwsm.setRealm(realm);
        dwsm.setSessionMode(JSECURITY_SESSION_MODE);
        WebRememberMeManager wrmm = new WebRememberMeManager();
        wrmm.setCookiePath("/");
        dwsm.setRememberMeManager(wrmm);
        // This next call will automatically create an EhCacheManager and
        // inject it into 'myRealm'.
        dwsm.init();
        // Now that the CacheManager has been injected into the realm,
        // this next init() call will acquire the cache used by that realm
        // for Account objects:
        realm.init();
        this.securityManager = dwsm;
    }
    return this.securityManager;
}

I'm sure that I'm missing a small step somewhere.

Any suggestions?

Thanks,
Todd

Note that the above solution uses JSecurity and Ehcache with no Tomcat/container specific config.

Here is an approach that don't use clustering or sockets:

Put ehcache.jar in Tomcat's root lib directory and JSecurity's failsafe ehcache.xml at the root of Tomcat's classpath, ensuring both are shared among all webapps in Tomcat. Then when creating JSecurity's EhCacheManager, you can do this:

EhCacheManager cm = new EhCacheManager();
cm.setCacheManager( CacheManager.getInstance() ); //forces EhCache to statically initialize itself with an ehcache.xml file at the root of tomcat's classpath.
cm.init();
securityManager.setCacheManager( cm );
// same as above
...

When both JSecurity applications do the above code chunk, they will be using the same JVM statically-loaded ehcache CacheManager instance. That same instance is wrapped by JSecurity's EhCacheManager and everything else works the same. This means all Cache instances would be shared across the VM. No socket overhead.

This is very fast, but 1) requires tomcat-specific set up and 2) is not useful if you plan to re-locate the applications to separate machines. Also, in reality, the socket overhead for your environment on the same machine for both apps is probably negligible, such that it probably wouldn't matter much if you were using the clustered solution.

So, I guess the question to ask yourself is - would I want to spend the time to create a custom clustered ehcache config that is used by both apps? Or would I want to spend the time to configure both JSecurity apps to use the same VM memory instance via Tomcat classpath set up. The latter takes less time to set up and is faster at runtime, but not useful on anything more than the same Tomcat installation.

It might be worth just trying the latter just to get it working. Then you could fiddle with ehcache clustering or TerraCotta if you ever needed to move the apps to separate machines.

Cheers!

Les