You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2007/03/21 18:29:40 UTC
DO NOT REPLY [Bug 41921] New: - samplers store all output, even when arbitrarily large
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41921>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41921
Summary: samplers store all output, even when arbitrarily large
Product: JMeter
Version: 2.2
Platform: All
OS/Version: All
Status: NEW
Severity: major
Priority: P2
Component: Main
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: nbryant@optonline.net
JDBCSampler (and I presume other samplers) store all the output received from
their test action. example:
Data data = getDataFromResultSet(rs);
res.setResponseData(data.toString().getBytes());
This is poor software design because the data could be arbitrarily large and
fill memory. It is causing OutOfMemoryErrors for us, even with not very many
threads. This is major or even critical because it prevents JMeter from being
used to generate significant load. All samplers should be rewritten to just
build an MD5 hash iteratively. The hash should be updated one buffer or row at a
time instead of in bulk.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 41921] - samplers store all output, even when arbitrarily large
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41921>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41921
nbryant@optonline.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |major
------- Additional Comments From nbryant@optonline.net 2007-03-21 11:47 -------
An MD5 or similar hash would be preferable over just storing part of the data,
for people who are using the data for functional testing. Then they could
compare everything for identity at least. I'm not doing functional testing so I
don't care, but I would recommend adding a configuration checkbox for an MD5 mode.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 41921] - samplers store all output, even when arbitrarily large
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41921>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41921
sebb@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal
------- Additional Comments From sebb@apache.org 2007-03-21 10:59 -------
The full sample results are needed for some purposes - e.g. the Tree View
Listener can display the results of an HTTP Sample, and Assertions need the
response to be present - so it would not make sense to _always_ throw away the
response data.
And the data needs to be retrieved, otherwise the sample time will not be
representative.
However sometimes it is not ideal to store all the response data.
As a work-round you could perhaps do one of the following:
* change the query to limit the data returned
* add a BeanShell Post-Processor to zap the responseData field.
As to how to fix this: there could be an option to limit the size of the stored
data. That should be fairly easy to do.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org