the datbase location should not affect sessionfactory creation unless you have schemaupdate activated.

And should definitly not affect the classloader performance ...

"many small" files can be a startup performance problem on some file systems too, try to put stuff to single jar file (it can be faster in some cases). Proxy generation takes a lot of time in my tests, but it can depend on use case too. I see proxy can be 100% lazy generated, Class.newInstance() is synchronized in new JVM implementatios anyway.

Could it be because you have
<property name="hibernate.hbm2ddl.auto">update</property>
or something like that in the config?
That would definitely make startup with remote DB slower.

I get the following error when using addCacheableFile on

sessionFactory = cfg.addCacheableFile(CONFIG_FILE_LOCATION).configure().buildSessionFactory();

if I use the standard approach works fine but it takes more than 15 sec to build the session factory.

Any help is appreciated . thank you.

%%%% Error Creating SessionFactory %%%%
org.hibernate.MappingException: org.dom4j.DocumentException: \com\estudiowebs\hibernate\hibernate.cfg.xml (The system cannot find the path specified) Nested exception: \com\estudiowebs\hibernate\hibernate.cfg.xml (The system cannot find the path specified)
at org.hibernate.cfg.Configuration.addCacheableFile(Configuration.java:297)
at org.hibernate.cfg.Configuration.addCacheableFile(Configuration.java:302)
at com.estudiowebs.Hibernate.HibernateSessionFactory.currentSession(HibernateSessionFactory.java:54)
at com.estudiowebs.RafaCentroRCP.Jobs.HibernateInitTask.run(HibernateStartUp.java:72)
Caused by: org.dom4j.DocumentException: \com\estudiowebs\hibernate\hibernate.cfg.xml (The system cannot find the path specified) Nested exception: \com\estudiowebs\hibernate\hibernate.cfg.xml (The system cannot find the path specified)
at org.dom4j.io.SAXReader.read(SAXReader.java:266)
at org.hibernate.cfg.Configuration.addCacheableFile(Configuration.java:281)
... 3 more
java.lang.NullPointerException
at com.estudiowebs.Hibernate.HibernateSessionFactory.currentSession(HibernateSessionFactory.java:64)
at com.estudiowebs.RafaCentroRCP.Jobs.HibernateInitTask.run(HibernateStartUp.java:72)
Input changed to: null

doesnt look like anything to do with addcachablefile. more something to with the loading of your cfg.xml - is it a valid path ?

yes, it is a valid path in fact, if I use the following code it works fine but it takes around 15 secs to startup:

cfg.configure(CONFIG_FILE_LOCATION);
sessionFactory = cfg.buildSessionFactory();

so you *dont* have the exception ? ok.

a call to buildsessionfactory can take that time for large set of classes - how many classes do you have ?

I have around 30 mapping files and it is a RCP eclipse desktop application so everytime the user opens it it takes 15 - 20 secs to load hibernate wich is a lot. I wouldn't mine if it was a webapp.

I would like to find an example about how to use the cacheable file or serialize the configuration file.

Thank you in advance

Raul.

the cfg.xml have never been intended so serialize. It is the hbm.xml files that can be serialized.

/max

Thanks for clarifying it for some reason I thought that it was done adding the cfg.xml since all the other mapping files were define there.

Since this is a configuration aspect It would make more sense to add an optional attribute in the mapping tag such as cacheable="true" and let hibernate look for a cacheable file instead of having to do it in java.

Thanks for your answer it was helpfull, I will try calling it passing each file individually.

you can suggest the cachable attribute in jira - it might be ok

Hi Max

I'd like to rate your answer, how do I do that?

there should be a rate button (but it only works for the original poster of the topic)

You can read the rules by clicking on the "Whats this" next to the rating.

I have posted a temporary solution for improving startup time.
http://forum.hibernate.org/viewtopic.ph ... 68#2262468