If crowd-ehcache.xml is misconfigured, Bamboo Crowd Integration Client uses wrong default cache

In Bamboo we have two config files for ehcache - ehcache.xml and crowd-ehcache.xml.

In the CacheManagerImpl constructor, the cache manager retrieved is actually the one Bamboo created for its caches with our default settings.

If you have specific caches specified in the crowd-ehcache.xml file, these are then created correctly. if you don't, Crowd will use bamboo's cache manager to create the default CROWD_CACHE rather than create the default cache using the default properties in the crowd-ehcache.xml. Bamboo's default cache is set to eternal=true=bad!!!.

The work around for this is to explicitly define the cache in the crowd config file.