Context :
- JVM IBM 1.5.0 AIX 64 bits
- LTW weaving classes in packages ( WebMethod IS server). The application is
big
I got a memory leak, with a lot of aspectj classes in the heapdump.
Examples :
- 590 000 instances of org.aspectj.ReferenceType
- 430 000 instances of org.aspectj.UnresolvedType
- 418 000 instances of org.aspectj.ResolvedType
- 280 000 instances of org.aspectj. ResolvedMemberImpl
AspectJ Development build of 22032008 (but I am not sure).
In aop.xml, in the weaver element, I have *not* exclude AspectJ package (
org.aspectj..) and I have *not* exclude my own aspect
In the heapdump my aspect is shown once ( default persingleton scope)
The number of classes woven is less than 50.
Do you think is a bug?
Cordialement / Best regards
Jean-Louis Pasturel
<mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]
*********************************
This message and any attachments (the "message") are confidential and intended
solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or
falsified.
If you are not the intended addressee of this message, please cancel it
immediately and inform the sender.
********************************
_______________________________________________
aspectj-users mailing list
aspectj-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users
