• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Jeanne Boyarsky
  • paul wheaton
  • Junilu Lacar
  • Paul Clapham
  • Knute Snortum
Saloon Keepers:
  • Stephan van Hulst
  • Ron McLeod
  • Tim Moores
  • salvin francis
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Vijitha Kumara

Named CDI Bean with Interceptor - Memory Leak  RSS feed

Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In my project (JEE 6, JBoss 7.1, JDK 1.7), I have several @Named CDI, all inheriting from a common @ConversationScoped abstract class.

I've noticed that if I define an interceptor and I apply this interceptor to the same abstract (thus, applying it by inheritance to all the CDI beans mentioned before), it happens that:

the method this.getClass() called on an instance returns the proxy class and no more the class itself;
the performance of the application is dramatically getting worse, both during the initial startup both during the normal activity; it seems that the amount of memory used by the application has increased a lot, simply adding this interceptor.
I'm a little confused, because it looks like applying the interceptor makes the beans "managed", whereas they all should be seen as "managed" also without the interceptor, since they already were "named".

What am i missing? Did anyone have the same problem about performance? Is there something I can check?

Thanks in advance for your help.
Doody calls. I would really rather that it didn't. Comfort me wise and sterile tiny ad:
global solutions you can do at home or in your backyard
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!