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=28630>. 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=28630 Painfully slow proxy server recording ------- Additional Comments From [EMAIL PROTECTED] 2004-04-28 18:38 ------- Following Sebb's advice I turned logging on. When I turned on the logging I got some strange behaviour. The recording proxy was actually fast. I thought I would just have to leave logging on, and that would be a work-around. No-go though. After about 4 items were captured in a "Simple Controller" on a proxy that excluded: .*/.js .*/.css .*/.gif .*/.jpg there was consistantly a 34-35 second delay between these two lines: 2004/04/28 13:28:34 DEBUG - jmeter.protocol.http.sampler.HTTPSampler: Start : samplehttp://server:port/Application/document/resource/StyleSheet.css 2004/04/28 13:29:08 DEBUG - jmeter.protocol.http.sampler.HTTPSampler: Location set to - null This occured for *.gif, *.jpg, *.css, *.js (non-captured) *.html (captured) but not any of our struts actions *.do The struts actions were captured almost instantly with POSTs and GETs and appeared much differently in the log. Thus if a page has a style sheet, a javascript validator and a few tiny gifs it will take 3+ minutes. Is there some chance that there is a "send buffer" on the proxy for embedded objects that timeouts after 35 seconds? This happened against our internal applications and external sites (www.google.ca, jakarta.apache.org/jmeter). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
