[
https://issues.jboss.org/browse/WELD-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Douglas resolved WELD-1058.
----------------------------------
Resolution: Rejected
This should already be fixed in 1.1.5 (not sure about the exact version it went
in).
Also it should not actually cause a noticeable leak, as the same proxy classes
should be re-used each time, so no further leaks will occur after the first
deployment.
> Perm heap bloat
> ---------------
>
> Key: WELD-1058
> URL: https://issues.jboss.org/browse/WELD-1058
> Project: Weld
> Issue Type: Bug
> Components: GlassFish Integration, Performance and Scalability
> Affects Versions: 1.1.2.Final
> Reporter: z xj
> Labels: licbug
>
> Synopsis:
> 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 repeated.
> Version:
> WELD 1.1.2
> Details:
> 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 behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
