Hello, I am doing some tests on an application that uses GET requests with a parameter nocache generated for each request. This application generates this request every second. So I simulated this and ran an endurance test. I noticed JMeter memory increased during the test. I made a Heap Dump and saw that CacheManager was overwhelmed by this request. There is of course an issue with WebServer config that should add Expires Header but I think we should protect JMeter from this by limiting size on Cachemanager HashMap, as it is the case for a real browser that has a limited memory size for cache.
Concerns nightly at 20 october 2011
Created attachment 27829 [details] Test plan to reproduce issue Add a static index.html file in Apache Tomcat webapps/ROOT folder.
Created attachment 27830 [details] Memory behaviour before fix
Created attachment 27831 [details] Memory behaviour after fix
Date: Thu Oct 20 19:07:13 2011 New Revision: 1186994 URL: http://svn.apache.org/viewvc?rev=1186994&view=rev Log: Bug 52064 - OutOfMemory Risk in CacheManager Modified: jakarta/jmeter/trunk/src/core/org/apache/jmeter/resources/messages.properties jakarta/jmeter/trunk/src/core/org/apache/jmeter/resources/messages_fr.properties jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/control/CacheManager.java jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/gui/CacheManagerGui.java jakarta/jmeter/trunk/xdocs/changes.xml
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2615