Hello everyone,

I have a memory leak in my application which has been very hard to fix. My application classes don't leave the memory after an undeploy. I don't even need to use the application, if I just deploy and instantly undeploy, almost all of the classes remain in memory. I used jhat and jmap to track them, as described in this link http://blogs.sun.com/fkieviet/entry/how ... he_dreaded.

From what I could understand, even the simplest EAR application which uses hibernate (and its dependencies) along with Stateless Session Beans, leaks memory, and you don't even need to use the application, just deploy and undeploy it to see that all the classes remain in memory.

Are there any advices to have a perfectly clean undeploy in my server, if my application uses EJB and Hibernate? I'm running out of permgen space all the time.

My current versions are:

Glassfish 2.1.1 (latest build)
JDK 1.6 u18

Thanks.

Hello
As i think u initialize your POJO CLASS object with the other object class.
And you are not free that object show you face such a problem

bump.

I have the simplest hibernate application possible. It just creates an EntityManagerFactory and closes it immediately. It doesn't use any other libraries, except for the DB driver. There is only one @Entity with a single integer field. I've tried with both derby and h2 and the permgen always shows up after some redeploys (the jdbc driver is deployed on tomcat lib folder, outside the webapp).

I've also created a dummy webapp containing a single class weighting 2mb. After redeploying this webapp Tomcat unloads it as expected and never runs out of memory. Hence, I'm suspecting the problem might be Hibernate's.

Any advice?

I'm using hibernate-core 3.3.2.GA and hibernate-entitymanager 3.4.0.GA.