And since I did that it seems to be working. Even HTTP Request (although now I have other problems but not with Jmeter). My guess is, that my Java machine got it's nickers in a tangle. Currently I can't reproduce the error anymore. :-(
But I'd still like somebody to try and mirror what I was doing and confirm that it works/doesn't work. If I can't reproduce till Friday afternoon I'll close the Fault I logged. Cheers Oliver -----Original Message----- From: Oliver Erlewein (DSLWN) [mailto:[EMAIL PROTECTED] Sent: Wednesday, 15 March 2006 12:51 To: JMeter Users List Subject: RE: Remote testing with JMeter Hi sebb, Used "HTTP Request HTTPClient" and it works like a charm! (*DUH* could have seen that earlier *grrrr-argh*). Just did a quick search but didn't find an explanation to the difference between the two. Do you have any details (or links with details) on that? But I think there should at least be a warning somwhere that the "normal" HTTP Request doesn't work or something of the sort. Cheers Oliver -----Original Message----- From: sebb [mailto:[EMAIL PROTECTED] Sent: Wednesday, 15 March 2006 12:11 To: JMeter Users List Subject: Re: Remote testing with JMeter We now know that the parameters are being picked up. I'm at a loss to explain why the settings don't seem to be picked up while running the test. Clutching at straws here: You can check the value of a property by using the __property() or __P() function; might be worth adding a Java sampler to double-check this during the test run. This checks the JMeter property bundle first, so is not ideal. To check a system property specifically, you could use the BeanShell function: ${__BeanShell(System.getProperty("propname"))} Which HTTP Sampler are you using? The original or HttpClient? I don't see why either would behave differently in server mode, but it could help to narrow things down. Or indeed you could try switching. S. On 14/03/06, Oliver Erlewein (DSLWN) <[EMAIL PROTECTED]> wrote: > Sebb, > > When I start the jmeter-server the jmeter.log lists: > > 2006/02/14 20:50:16 INFO - jmeter.util.JMeterUtils: Setting Locale to > en_US > 2006/02/14 20:50:17 INFO - jmeter.JMeter: Set http[s].proxyHost: > localhost Port: 5865 > 2006/02/14 20:50:17 INFO - jmeter.JMeter: Version 2.1.1 > 2006/02/14 20:50:17 INFO - jmeter.JMeter: java.version=1.4.2_11 > 2006/02/14 20:50:17 INFO - jmeter.JMeter: Locale=English (United > States) > 2006/02/14 20:50:17 INFO - jmeter.JMeter: Copyright (c) 1998-2005 The > Apache Software Foundation > 2006/02/14 20:50:17 INFO - jmeter.engine.RemoteJMeterEngineImpl: > Starting backing engine on 1099 > 2006/02/14 20:50:18 INFO - jmeter.engine.RemoteJMeterEngineImpl: > Bound to registry on port 1099 > > So it should work?!?! But then something else is wrong because it > definitely doesn't. Any ideas? > > Cheers Oliver > > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 15 March 2006 07:06 > To: JMeter Users List > Subject: Re: Remote testing with JMeter > > If the proxy command-line flags are recognised/processed, then JMeter > should log an informational message to say so. The way it implements > the proxy is to define the Java properties: > > http.proxyHost > http.proxyPort > > Likewise for https. > > These settings are then picked up by the HTTP protocol code. > > So it should work ... > > Perhaps you can check the jmeter.log files for the non-GUI and server > cases, and see if the message is logged. Perhaps you could add these > logs to the Bugzilla issue. > > You can also try defining the appropriate Java properties by using the > appropriate java command-line flags. > > S. > > --------------------------------------------------------------------- > 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]
