Hi,

I am using hibernate 2.1.2 with tomcat and MSSQL 2000.
After doing hot deploy for several times I get OutOfMemoryError when hibernate initialize itself.
What can cause this problem?

Here is the last log:

[INFO] Environment - -Hibernate 2.1.2
[INFO] Environment - -loaded properties from resource hibernate.properties: {hibernate.connection.driver_class=com.sap.portals.jdbc.sqlserver.SQLServerDriver, hibernate.cglib.use_reflection_optimizer=true, hibernate.cache.provider_class=net
.sf.hibernate.cache.HashtableCacheProvider, hibernate.cache.use_query_cache=true
, hibernate.max_fetch_depth=1, hibernate.dialect=net.sf.hibernate.dialect.SQLSer
verDialect, hibernate.jdbc.use_streams_for_binary=true, hibernate.jdbc.batch_size=0, hibernate.query.substitutions=true 1, false 0, yes 'Y', no 'N', hibernate.connection.username=test, hibernate.connection.url=jdbc:sap:sqlserver://localhost:1433;DatabaseName=Test, hibernate.connection.password=test, hibernate.connection.pool_size=1}
[INFO] Environment - -using java.io streams to persist binary types
[INFO] Environment - -using CGLIB reflection optimizer
[INFO] Environment - -JVM does not support Statement.getGeneratedKeys()
[INFO] Environment - -JVM does not support LinkedHasMap,LinkedHashSet - ordered maps and sets disabled
[INFO] Environment - -using workaround for JVM bug in java.sql.Timestamp
[INFO] Configuration - -Mapping resource: com/sap/xteam/exam/Answer.hbm.xml
java.lang.OutOfMemoryError
<<no stack trace available>>

close session factory before to undeploy "servlet.destroy()", "ContextListener" can help too.

I do sessionFactory.close() when I undeploy the servlet but I am still getting the error.
Can it be something with the cache?
I am using HashtableCacheProvider and I am thinking maybe it not clear it when undeploy.
Any one have a suggestion?

It can be caused by cglib looks like it holds strong reference on classloader indirectly, it is not tested at this time, but try to build cglib from cvs, I will test it today myself.

How does one do that?