Hibernate version: 3.2 CR2

I've developed a desktop application that opens several Hibernate databases.

Each database uses a separate instance of SessionFactory.

I've recently upgraded to 3.2 CR2 and this is causing cache problems as indicated by the following error message:

detailMessage
"Attempt to restart an already started EhCacheProvider.
Use sessionFactory.close() between repeated calls to buildSessionFactory.
Consider using net.sf.ehcache.hibernate.SingletonEhCacheProvider.
Error from ehcache was: Cannot parseConfiguration CacheManager.
Attempt to create a new instance of CacheManager using the diskStorePath
"C:\DOCUME~1\chas00\LOCALS~1\Temp\" which is already used by an existing CacheManager.
The source of the configuration was classpath."

The code that causes the error is:
sessionFactory = annotationConfiguration.buildSessionFactory();

This instance of sessionFactory is null before the call; therefore it is not possible to follow the suggestion in the error message (the code for each database does not have access to the instances of sessionFactory for other databases).

I'll appreciate any suggestions.

Also,
where can I locate the class net.sf.ehcache.hibernate.SingletonEhCacheProvider;
it doesn't seem to be included in the distribution.

After locating this class, what is the procedure for using it.

In advance, thanks.

Charlie

Your problem might be caused by something else, but in 3.2 CR2 they upgraded from EhCache 1.1 to 1.2. Did you update that in your project?

I use the same version of Hibernate, I also use the annotationconfiguration with no error like this (I use a single database though):

Hi "szroland"

Thanks for your suggestion.

I'm using EhCache1.2 (and all the other jars from the 3.2 RC2 distribution).

The problem is caused by instantiating multiple instances of SessionFactory.

There is no problem with the first instantiation; the problem occurs with the second, and subsequent databases.

Charlie

Sorry, that wasn't really helpful then. I checked and I see your problem now.
I wonder while SingletonEhCacheProvider is missing from the ehcache-1.2 distribution, but they have it in ehcache cvs. Maybe it worth to take a look.

Roland

Better yet, you can actually configure for each of your session factories a different ehcache config file. I found this in the API doc, I also checked, and it works, you only need to specify different disk locations for each CacheManager.



Roland

Hi Roland,

Thanks for your research.

I'll try that method.

One potential problem: I distribute the application as an Eclipse rich client.
Therefore, I don't have access to the absolute class path where the application is intalled.

I will experiment.

Charlie

I'm pretty sure you could get the current absolute path some way. But the ehcache descriptor should be put into your jar file, it is loaded as a resource. So they will not be separate files.

Hi Charlie,

just upgrade your ehcache jar to ehcache-1.2.1rc,
and you problem will be solved.

Cheers
Javier Paniza