Apr 18th, 2009, 04:36 PM
Easy memory leaking with custom Poincut implementation
I have run into a problem with PermGenSpace memory leak using programmatical creation of CgLib proxies. This was only due to my mistake, that I could probably avoid if there was better explanation in Spring documentation. I have explained details of the problem in the article Spring CgLib Dynamic AOP Proxies - proper Pointcut equals method is simply essential.
Do you think, you can somehow extend chapter 7.2.6. Custom pointcuts in the documentation with the warning connected to the proper equals implementation in custom Pointcuts? Maybe it could save several hours to developers running at the same problem as me.
I hope I've chosen the right way to tell you - raising Jira issue seemed too much for me in this case.
Thanks for the reply.
Tags for this Thread