[
https://issues.apache.org/jira/browse/VELOCITY-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027071#comment-13027071
]
Nathan Bubna commented on VELOCITY-801:
---------------------------------------
Those cached templates are discarded if the RuntimeInstance is discarded.
Here's the bottom line on this. No relevant changes are going to be made for
this without a test that demonstrates the problem and thus allows us to confirm
the benefit of whatever solution is proposed. The use of string.intern() was
added because it was demonstrated that it fixed some major performance issues.
It will not be removed unless it is A) demonstrated to be a problem, as claimed
and B) a replacement solution is offered that does not simply restore our
previous issues.
Also, since we are talking about a native method and deep JVM voodoo :),
Alexander, it would be best if you included more environment info. Most
especially, the JDK version, as that may well be relevant.
Evidence/description of your application's particular symptom(s) would also be
meaningful in supporting your diagnosis.
> Velocity 1.7 uses string interning
> ----------------------------------
>
> Key: VELOCITY-801
> URL: https://issues.apache.org/jira/browse/VELOCITY-801
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.7.x
> Environment: n.a.
> Reporter: Alexander Veit
> Priority: Critical
>
> String interning consumes memory that cannot be reclaimed by the java runtime
> even if the velocity runtime singleton is being discarded.
> This is an issue for server applications that use Velocity (e.g. we have a
> software product that may use tens of thousands of Velocity files to create
> content dynamically).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
