Thanks guys. That was indeed the case. The Java control panel settings were set to connect using a Direct connection. Setting it to use the browser's settings fixed it. And interestingly, explicitly specifying the proxy seems work just fine as well.
-----Original Message----- From: sebb [mailto:[email protected]] Sent: Tuesday, November 09, 2010 10:14 AM To: JMeter Users List Subject: Re: Applet requests On 9 November 2010 15:07, Deepak Shetty <[email protected]> wrote: > In windows control panel --> java --> network settings. If that applies to all Java programs, then won't that affect JMeter too? In which case it may end up proxying back to itself which would be rather messy... > However the default should be use the browsers settings... That should work better. If it still does not seem to work, then use a protocol analyser such as Wireshark to find out where the requests are going. > On Tue, Nov 9, 2010 at 7:02 AM, sebb <[email protected]> wrote: > >> On 9 November 2010 13:56, Somagani, Seeta X >> <[email protected]> wrote: >> > Hi all, >> > >> > Our application is primarily an applet loaded by JavaScript. I'm >> > trying to load test our app using JMeter by first recording the >> > traffic using the JMeter proxy. I find that the JMeter proxy >> > captures the initial requests for the JSPs and the .js files. I, >> > however, do not see any requests that are made by the applet. The >> > proxy seems to totally ignore the requests for .class files, image >> > files and other multi-part requests made by the applet. Any ideas about what the problem could be? >> >> The applet has not been told to use the proxy, so JMeter does not see >> the requests. >> >> I don't know if it is possible to tell the applet to use a proxy. >> >> > Thanks, >> > Seeta >> > >> > P.S. I tried using FireBug and BadBoy and they don't capture the >> > requests as well, but that was kind of expected of those tools. >> > >> > >> > ------------------------------------------ >> > The contents of this message, together with any attachments, are >> > intended only for the use of the person(s) to which they are >> > addressed and may contain confidential and/or privileged >> > information. Further, any medical information herein is >> > confidential and protected by law. It is unlawful for unauthorized >> > persons to use, review, copy, disclose, or disseminate confidential >> > medical information. If you are not the intended recipient, >> > immediately advise the sender and delete this message and any >> > attachments. Any distribution, or copying of this message, or any >> > attachment, is prohibited. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] ------------------------------------------ The contents of this message, together with any attachments, are intended only for the use of the person(s) to which they are addressed and may contain confidential and/or privileged information. Further, any medical information herein is confidential and protected by law. It is unlawful for unauthorized persons to use, review, copy, disclose, or disseminate confidential medical information. If you are not the intended recipient, immediately advise the sender and delete this message and any attachments. Any distribution, or copying of this message, or any attachment, is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
