z xj commented on WELD-1058:
This should already be fixed in 1.1.5 (not sure about the exact
version it went in).
Could you please tell me which issue number addressed this problem?
Perm heap bloat
Issue Type: Bug
Components: GlassFish Integration, Performance and Scalability
Affects Versions: 1.1.2.Final
Reporter: z xj
The proxy classes generated at application start time are kept after stopping
application. It will result in perm heap bloat if application's start/stop are
The current RI uses javassist to generate the corresponding proxy class of Principal,
UserTransaction, ValidatorFactory and Validator at application start time. Javassist load
those proxy classes via system's class loader and that class loader is not discarded
after stopping application, therefore those proxy classes remain there. At application
development phase, repeating application's start/stop will lead to memory leak with
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira