Hi, Unfortunately with compile time weaving I endup without PermGen. Our application replaces objects on the cache from time to time. I have done some stress tests with high load of cache insertions (replacemente: insert on an exiting node) and I endup with OurOfMemory on the permanent generation (no matter the max limit of PermGen). I took a look at the tmp dir, and I have a class object for each instantiation of my aspectized objects:
-rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14571.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14572.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14573.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14563.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14564.class | -rw-rw-r-- 1 cerberus cerberus 6680 Dez 6 17:13 AOPClassProxy$14565.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14566.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14567.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14568.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14569.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14570.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:13 AOPClassProxy$14562.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14557.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14558.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14559.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14560.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14561.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14551.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14552.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14553.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14554.class | -rw-rw-r-- 1 cerberus cerberus 9952 Dez 6 17:12 AOPClassProxy$14555.class | I have done a memory dump (1 GB) and I'm going to analyze it. Although I think there is a bug somewhere, because objects replaced on the cache don't seem to be garbage collected. This makes my old generation increase, and the same for the permanent generation. Are Cache replaced objects correctly garbage collected? Why do I have a new Class object created for each instantiation of my aspectized objects? Is this the expected behavior? At the moment I have having serious problems, no matter I use compile time weaving or load time weaving. Although, load time weaving is the option I would go for, if I wouldn't have the strange startup error (object not aspectized). I am really getting "crazy" with this problems. Any hint to solve my problem? Thanks in advance. Best regards, Victor Batista PS: I upgraded JBossCache to 1.4.1.SP14 PS2: I will to replace the PojoCache by a TreeCache. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269187#4269187 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269187 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
