[
https://issues.jboss.org/browse/WELD-1058?page=com.atlassian.jira.plugin....
]
Ales Justin commented on WELD-1058:
-----------------------------------
I guess this is not only GlassFish problem, but any app server's?
(as I would expect all (actually both - JBossAS and GF) do this the same way)
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