I am seeing class definition and/or class version errors relating to the classloader with regarding to some of the JOS support classes that Hibernate uses, such as Jakarta commons logging, as an example. Our situation is that we have two applications, that run in separate JVMs, that call each other. Each use Hibernate to do persistence to their own databases. Intermittently, I see these errors when I have the hibernate.jar and the supporting .jars in each application's app-inf/lib's. However, if I move the .jars to the server classpath then the issues go away.

This configuration is not optimal because one application may use a latter version of the .jars and then this would require regression testing for all apps that use Hibernate and the associated .jars on the server.

In general, I am wondering how others have configured their .jars. Is this something you just have to live with?? Or is there a viable solution to have the .jars live in each application?

Thanks,
Lou



Hibernate version:
2.1.6
Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt: