In my application, I only started seeing the CacheManager warnings that I mentioned after I added Jackrabbit support. Also, the Cachemanager emits its warnings immediately after the Jackrabbit repository starts up; I assumed that the timing was not coincidental.
However, when I disable the JCR support, I still get that warning. I guess I should have tried that before coming here to complain about Jackrabbit caching ;) Thanks! -Brian On 2/28/07, Stefan Guggisberg <[EMAIL PROTECTED]> wrote:
hi brian, On 2/27/07, Brian Thompson <[EMAIL PROTECTED]> wrote: > Hello, > > In my project, I'm using both Jackrabbit and Hibernate for different > purposes, both of which use ehcache. When my project starts up, I get a jackrabbit doesn't use ehcache, at least i am not aware off ;-) what leads you to believe that jackrabbit uses ehcache? cheers stefan > warning: > > [APP] INFO [main] RepositoryImpl.<init>(329) | Repository started > [APP] WARN [main] CacheManager.detectAndFixDiskStorePathConflict(271) | > Creating a new instance of CacheManager using the diskStorePath "C:\Program > Files\apache-tomcat-5.5.20\temp" which is already used by an existing > CacheManager. > The source of the configuration was classpath. > The diskStore path for this CacheManager will be set to C:\Program > Files\apache-tomcat-5.5.20\temp\ehcache_auto_created_1172597783217. > To avoid this warning consider using the CacheManager factory methods to > create a singleton CacheManager or specifying a separate ehcache > configuration (ehcache.xml) for each CacheManager instance. > > I'd like to configure both tools to use the same CacheManager, but I can't > seem to find any information on configuring the CacheManager for > Jackrabbit. Has anyone dealt with this type of cacheManager collision > before? > > Thanks, > > -Brian >
