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: [email protected] ReportedBy: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
