Thanks Clebert, My initial feeling was that it might be the ServiceTimer because we just added the code that uses it and because it's not available in an @Service context we're using it creatively through a SLSB injected into an @Service. However, if this was the case, I think it would be fairly track-able because we set a TimerService event at a fairly consistent interval.
After the crash yesterday we upped the MaxPermSize from 128m to 256m and the max heap size from 512m to 1024m. The server hasn't hit the PermGen problem since and the RES size of java on the server has stabilized in the 650m range. At this point it looks like it is not a memory leak issue after all, but rather simply a change in memory requirements between to the two versions of JBoss AS/EJB3 and the changes to our app. I'm keeping a close eye on it and will report more information when I have it, but I'm thinking I was raising a false alarm. djr667 - I don't think our issues are related. We run JBoss with the -server setting. We have had trouble with CGLib/Hibernate when running in -client mode due to differences in bytecode optimization between the two with Sun's Linux JVM (not memory leak related), but -server has been fine for us. Thanks again, Jonn View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951402#3951402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951402 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
