[ https://jira.jboss.org/browse/GTNPORTAL-1357?page=com.atlassian.jira.plug... ] Minh Hoang TO updated GTNPORTAL-1357: ------------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours Labels: sprint 36 (was: ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNPORTAL-1357?page=com.atlassian.jira.plug... ] Trong Tran updated GTNPORTAL-1357: ---------------------------------- Labels: sprint 36 (was: sprint_36) Description: Since GateIn 3.1, We changed a bit on template caching mechanism that the template resource key are combination of ResourceResolver#hashCode() + templateURL Unfortunately if a third party is using a custom ResourceResolver which is created newly for each request, that is the resource key will be always different in each request and it raises up a memory leak and a performance issues was: Since GateIn 3.1, We changed a bit on template caching mechanism that the template resource key are combination of ResourceResolver#hashCode() + templateURL This now raises up problems if a third party is using a custom ResourceResolver which is created newly for each request, that is a memory leak and a performance issue In fact, the most of problem is that there is no clear API of ResourceResolver. Ideally GateIn does not expect the method that the resource resolver is newly created in each request and if a third party that defines a custom ResourceResolver, it has to take care by itself to ensure the resource key is consistent for a particular URL So now what we need to do is to update the API to clear the contract between what GateIn provides and a third party has to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNPORTAL-1357?page=com.atlassian.jira.plug... ] Work on GTNPORTAL-1357 started by Vu Viet Phuong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNPORTAL-1357?page=com.atlassian.jira.plug... ] Work on GTNPORTAL-1357 stopped by Vu Viet Phuong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNPORTAL-1357?page=com.atlassian.jira.plug... ] Minh Hoang TO commented on GTNPORTAL-1357: ------------------------------------------ public ResourceKey createResourceKey(String url) { return new ResourceKey(hashCode(), url); } The Javadoc helps only if developers read it. There are two aimable solutions 1. Make the method getResourceKey abstract 2. Replace hashCode() with this.getClass().hashCode() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNPORTAL-1357?page=com.atlassian.jira.plug... ] Trong Tran resolved GTNPORTAL-1357. ----------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira