1. Have you tried running current SVN head without your own custom ResourceCacheImpl?
2. If the current SVN head also leads to OOM, a) does it give any stacktrace? b) could you try making getResource method in ResourceManagerImpl synchronized and see if it helps? If it does, the problem is related to concurrent parsing of templates. Otherwise the problem is somewhere else. 3. There is one JIRA issue which is suspicious: https://issues.apache.org/jira/browse/VELOCITY-570 - the reinit patch has not been applied to current SVN head but I wasn't able to get OOM errors anyway. You might try to apply that reinit patch and see if it has any effect. I tried running my own very simple Velocity demo app with 100 concurrent users but I wasn't able to get the OOM (granted, the templates are very small). Could you create some testbed which would reproduce this problem? Jarkko erron wrote: > > At the time, I was able to create the OOM with by myself clicking around > the > site. I doubt you would consider these templates very large, mostly just > html with a few variables.with the largest template being about 32k. And > my > JVM settings where the same as I had for the 1.5 version. However, I do > have my own ResourceCacheImpl (any issues jump out at you?): > -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28VELOCITY-607%29-Runtime-macro-rendering-very-slow-in-Velocity-1.6-dev-%28679708%29-compared-to-1.5-tp18648266p18983762.html Sent from the Velocity - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
