Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version:

Hibernate 3.0.5

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:

It appears that I can not profile application with profiler (I have tried JProfiler 4.x and Yourkit 5.0) if it uses runtime bytecode instrumentalization to enable precise method invocation tracing.
If lazy is set to true at class level in metadata working thread just exits if I use Yourkit or I am starting to get runtime ClassNotFound exceptions if I use JProfiler.
If I set lazy=false for all classes in metadata everything works just fine and I am able to profile the application.

Is there any solution for this? For example using some kind of design time enhancement or something like that?

p.s. Application works just fine with lazy=true if there is no profiler agent loaded...