We have a total of 554 managed objects in our domain model that are configured in our hibernate.cfg.xml file. After SessionFactory initialization, a heap dump is showing that the SessionFactoryImpl has references to objects totalling 67Mb.

Is this considered normal? Are there any configuration options or mapping recommendations to reduce this memory usage? The majority of our classes are mapped with lazy="true", with only a small handful using lazy="false".

This has reached an unacceptable size in our deployment environment since we are constrained by memory (the max heap size we can run with is -Xmx512M on Websphere 5.1 running on AIX 5.2, IBM JDK 1.4.2 SR5)

Any suggestions?

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

Hibernate version:
3.0.4
Mapping documents:
554 managed objects in configuration file
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:


Problems with Session and transaction handling?

Read this: http://hibernate.org/42.html