Adym, Yes, there are two proxy servers but Jmeter should only contact the one on the local machine. Yes and I tried putting in the IP and the actual name. No luck so far. The local proxy has no authentication. And why should it work if I start the script from the command line and not work it I start it as a server?
My hunch is, that the proxy routine is probably skipped if you start Jmeter with the "-s" option. Cheers Oliver P.S. Is there somebody that can simulate my problem? It should happen when you use a "jmeter-server" through a proxy. -----Original Message----- From: Lincoln, Adym [mailto:[EMAIL PROTECTED] Sent: Tuesday, 14 March 2006 05:06 To: JMeter Users List Subject: RE: Remote testing with JMeter Oliver, Just so we're clear...You're going thru 2 (two) proxy servers? Are both proxy servers using the same user/pwd parameters? Also, I might change the -H parameter from localhost to the actual name of the server, even though jmeter is running on it as a localhost...not knowing the network configuration, we have no idea which servers/proxies are hitting your DNS domain server and which aren't. If the -H server name doesn't work, try putting the actual tcp/ip address in... thx, Adym Lincoln I/S Corporate - I/S Internal Applications 603-245-3744 Ext : 53744 [EMAIL PROTECTED] ... It's a bug planet...it's an ugly planet...ever feel like your software project is going in the wrong direction. ... -----Original Message----- From: Oliver Erlewein (DSLWN) [mailto:[EMAIL PROTECTED] Sent: Sunday, March 12, 2006 10:33 PM To: JMeter Users List Subject: RE: Remote testing with JMeter Hi What am I doing? Jmeter runs on a Linux server that connects to an internal proxy server (on port 5865), which intern connects to the exterior internet proxy server. So I run "./jmeter -n -t openbc.jmx -l test.txt -H localhost -P 5865" and that works just excellent! Tcpdump gives me a whole lotta lines like this: 03:20:22.071691 IP 172.17.2.32.33156 > 172.25.10.102.http: . ack 18875.... Now I start "./jmeter-server -H localhost -P 5865" and runthe same script via remote. Tcpdump does this: 03:20:53.815486 IP 172.17.2.32.43208 > 213.238.59.20.http: S 180175323:180175323(0) win 5840.... 213.238.59.20 is www.openbc.com, which is the destination address. This times out because jmeter is not using the proxy. Any ideas why "jmeter -s" would not regard the -H and -P parameters that set the proxy??? Cheers Oliver P.S. If nobody knows this I'll rais this as a defect against jmeter. -----Original Message----- From: Oliver Erlewein (DSLWN) [mailto:[EMAIL PROTECTED] Sent: Friday, 10 March 2006 16:16 To: JMeter Users List Subject: RE: Remote testing with JMeter Hi Adym, Ok, looks like I got over my problem connecting to the jmeter-server. Now something funny's going on. If I start... ./jmeter -n -t openbc.jmx -l test.txt -H localhost -P 5865 All goes well. If I do... ./jmeter-server -H localhost -P 5865 And run the same test from my client, then it times out. It works if I run it locally and it works remotely on an XP box. Any ideas what's different? Cheers Oliver P.S. Thank you for all your excellent help! I've really gained a lot. I'm off to enjoy the weekend now and will continue on Monday. -----Original Message----- From: Lincoln, Adym [mailto:[EMAIL PROTECTED] Sent: Friday, 10 March 2006 09:18 To: JMeter Users List Subject: RE: Remote testing with JMeter Oliver, Scratch that idea on /etc/hosts.allow. That is related to a service called tcpd which is "optional" on a linux server. Issue the command system-config-securitylevel on your Linux server and check/verify whether the firewall is Enabled/Disabled. If the firewall is "Enabled" than TAB to the Customize button and look in there and verify what settings are checked for the Allow incoming: and also if there are any ports listed in the Other ports. hth, Adym Lincoln I/S Corporate - I/S Internal Applications 603-245-3744 Ext : 53744 [EMAIL PROTECTED] ... It's a bug planet...it's an ugly planet...ever feel like your software project is going in the wrong direction. ... --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]
