[
https://issues.apache.org/jira/browse/SLING-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2471.
-------------------------------------
Resolution: Fixed
I've changed the way the jsp scripts are hold. If now a jsp is reloaded and the
class loader gets invalided all loaded scripts are asynchronously invalided.
This frees the
classloader immediately and there is just one class loader used at a time.
In addition the classloader gets invalidated as soon as the jsp is changed and
not
when the jsp is used the next time.
Some more improvements like less locking etc.
> Free classloaders as soon as possible
> -------------------------------------
>
> Key: SLING-2471
> URL: https://issues.apache.org/jira/browse/SLING-2471
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting JSP 2.0.20
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.0.22
>
>
> Currently if a classloader is marked as invalid, it is still kept around as
> jsps are only reloaded the next time they're accessed. This can lead to many
> stale classloaders if there is at least one loaded jsp which is not touched.
> Over time this can lead to perm gen problems as the number of stale
> classloaders increases
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
