I did force n number of times manual garbage collection while taking memory snapshot.But no luck. I am sure that those instances get never released.
>From your input, I tried to look at EJB3/EJB instances leakage. Thanks god >they are not leaked. It seems there is something to do with ThreadLocal or >ServerThread instance. Just as a quick test, I opened some file handles within POJO singleton class implementation,which internally used by one of my ejb3 slsb. In finalize() of singleton class I close these filehandles. I tried redeploying my app n number of times,singleton instance is created n times(ofcourse) , but as no singleton is garbaged, all file handles are still kept opened (Used a ProcessExplorer tool in windows) ofcourse which leads to memory leak. I will try providing you a testcase. Till that time, here is referrer details: <h3>Instance Detail</h3> <h4>Referrer Tree</h4> TestEJB3 1480368 StatelessBeanContext 1480412 (bean) ThreadLocal$ThreadLocalMap$Entry 1482804 (value) ThreadLocal$ThreadLocalMap$Entry [512] 1293433 ([151]) ThreadLocal$ThreadLocalMap 1281230 (table) ServerThread 741958 (threadLocals) LinkedList$Entry 819620 (element) WeakHashMap$Entry 777095 (referent) Thread [32] 775226 ([20]) 1152921504606849020 Java Frame 1152921504606846993 Java Frame 1152921504606846990 Java Frame 1152921504606846989 thx. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928716#3928716 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928716 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
