I did get it working with a little brute force before I received your latest suggestion. First, I added "ssl.provider" and "javax.net.ssl.keyStorePassword" to the jmeter.properties. These were not present as options in the jmeter.properties that came with the 2.3.2 JMeter.
Next, I modified the source JMeterMojo. I simply hard-coded "-H", "-P", and "-N" and their corresponding values as arguments into the Jmeter().start() call itself... sort of like I did by adding these parameters to the JMeter bat. It worked! I know this isn't optimal, but it did prove that the proxy and port were not being set. To confirm, the beanshell.server.port and httpclient.localaddress identify which port and proxy for JMeter to use to access the Internet? The names don't seem to jive, but I will give it a try. Last question. Can a Mojo access configuration from the Maven settings.xml and how? If I need to go with my modified version, I would like to leverage the proxy information already present in the settings.xml. Thanks! "Martin Gainty" <mgai...@hotmail.com> 03/03/2009 08:22 PM Please respond to "Maven Users List" <users@maven.apache.org> To users@maven.apache.org cc Subject RE: JMETER the Jmeter host and port parameters should be located in %JMETER_HOME%\bin\jmeter.properties e.g. beanshell.server.port=8080 httpclient.localaddress=1.2.3.4 --find the SecureHandshake your SSH client is using and configure the https.default.protocol to use it https.default.protocol=SSLv3 there was a bug in Jmeter v2.2 that didnt read localaddress properly but that should be resolved in later distros ..let me know how this resolves your situation HTH Martin ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. > To: users@maven.apache.org > Subject: RE: JMETER > From: jerry.th...@hewitt.com > Date: Tue, 3 Mar 2009 15:49:29 -0600 > > Thanks Martin! I was able to compile that class and recreate the > jorphan.jar. Got past the issue. On to the next... > > <responseData class="java.lang.String">java.net.ConnectException: > Connection refused: connect
 > at java.net.PlainSocketImpl.socketConnect(Native Method)
 > at > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 > at > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 > at > java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 > at java.net.Socket.connect(Socket.java:520)
 > at java.net.Socket.connect(Socket.java:470)
 > at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 > at > sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
 > at > sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
 > at > sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:278)
 > at > sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:335)
 > at > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:176)
 > at > sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
 > at > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:162)
 > at > com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnectionOldImpl.connect(HttpsURLConnectionOldImpl.java:122)
 > at > org.apache.jmeter.protocol.http.sampler.HTTPSampler.sample(HTTPSampler.java:406)
 > at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:658)
 > at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:647)
 > at > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:247)
 > at java.lang.Thread.run(Thread.java:595)
 > </responseData> > > The URL I'm attempting to access is outside our firewall. I'm trying my > best to ensure the proxy information is setup and I have the third party's > SSL certificate in the correct keystore/truststore. I have the proxy info > setup in my settings.xml, but I'm not confident this plug-in is using that > information. I also have http.proxyHost and such set in the > jmeter.properties, but I'm not confident that is correct either. > > The URL I'm trying to access is available via the browser and works when I > use the JMeter application, just not the Maven2 plugin. The main > difference is that I pass in the -H and -P via the jmeter.bat when I fire > that up. BTW, several corporate URLs are executing correctly prior to the > third party one. It fails as soon as I try to go *outside*. > > Any thoughts? > > Thanks. > > > > > "Martin Gainty" <mgai...@hotmail.com> > > 03/02/2009 07:41 PM > Please respond to > "Maven Users List" <users@maven.apache.org> > > > > To > users@maven.apache.org > cc > > Subject > RE: JMETER > > > > > > > > Hi Jerry- > I dont know what your timeframe is but you'll need rel 2-2 of > JorphanUtils.java > > http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/src/jorphan/org/apache/jorphan/util/JOrphanUtils.java?view=markup&pathrev=463044 > > > i would download it compile it and put on classpath before the outdated > jar that causes error > > HTH > Martin > ______________________________________________ > Disclaimer and confidentiality note > Everything in this e-mail and any attachments relates to the official > business of Sender. This transmission is of a confidential nature and > Sender does not endorse distribution to any party other than intended > recipient. Sender does not necessarily endorse content contained within > this transmission. > > > > > > To: users@maven.apache.org > > Subject: JMETER > > From: jerry.th...@hewitt.com > > Date: Mon, 2 Mar 2009 12:36:35 -0600 > > > > The best source of information regarding JMETER that I have found is > here > > > http://jlorenzen.blogspot.com/2008/03/automated-performance-tests-using.html?showComment=1234202880000#c1509976267762769707 > > > > > After following Jame's blog, I was able to record and successfully > execute > > a script in JMeter. I then moved the JMX to my local project and it's > > failing with the below message. I'm running on Maven 2.0.9, JDK 1.5. I > > > followed the install/deploy instructions exactly (well, I think I did). > > The java.lang.NoSuchMethodError makes me think I'm not using the correct > > > version of JOrphan or jmeter.jar itself. Has anyone encountered this > > before or have ideas? > > > > 2009/03/02 12:12:04 INFO - jmeter.util.JMeterUtils: Setting Locale to > > en_US > > 2009/03/02 12:12:04 INFO - jmeter.JMeter: Copyright (c) 1998-2006 The > > Apache Software Foundation > > 2009/03/02 12:12:04 INFO - jmeter.JMeter: Version 2.2 > > 2009/03/02 12:12:04 INFO - jmeter.JMeter: java.version=1.5.0_14 > > 2009/03/02 12:12:04 INFO - jmeter.JMeter: os.name=Windows XP > > 2009/03/02 12:12:04 INFO - jmeter.JMeter: os.arch=x86 > > 2009/03/02 12:12:04 INFO - jmeter.JMeter: os.version=5.1 > > 2009/03/02 12:12:04 INFO - jmeter.JMeter: Default Locale=English > (United > > States) > > 2009/03/02 12:12:04 INFO - jmeter.JMeter: JMeter Locale=English > (United > > States) > > ... > > 2009/03/02 12:12:05 INFO - jmeter.util.SSLManager: JmeterKeyStore type: > > > class org.apache.jmeter.util.keystore.DefaultKeyStore > > 2009/03/02 12:12:05 INFO - jmeter.util.JsseSSLManager: class > > org.apache.jmeter.util.keystore.DefaultKeyStore > > 2009/03/02 12:12:05 INFO - jmeter.util.SSLManager: TrustStore Type: JKS > > > 2009/03/02 12:12:05 INFO - jmeter.util.SSLManager: TrustStore Location: > > > 2009/03/02 12:12:05 INFO - jmeter.util.SSLManager: TrustStore type: > class > > org.apache.jmeter.util.keystore.DefaultKeyStore > > 2009/03/02 12:12:05 INFO - jmeter.util.JsseSSLManager: JsseSSLManager > > installed > > 2009/03/02 12:12:06 ERROR - jmeter.threads.JMeterThread: Test failed! > > java.lang.NoSuchMethodError: > > > org.apache.jorphan.util.JOrphanUtils.encode(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String; > > at > > > org.apache.jmeter.protocol.http.util.EncoderCache.getEncoded(EncoderCache.java:45) > > at > > > org.apache.jmeter.protocol.http.util.HTTPArgument.getEncodedName(HTTPArgument.java:144) > > at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.getQueryString(HTTPSamplerBase.java:570) > > at > > > org.apache.jmeter.protocol.http.sampler.HTTPSampler.setupConnection(HTTPSampler.java:186) > > at > > > org.apache.jmeter.protocol.http.sampler.HTTPSampler.sample(HTTPSampler.java:404) > > at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:658) > > at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:647) > > at > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:247) > > at java.lang.Thread.run(Thread.java:595) > > > > I also have a few more questions: > > 1. Is the JMETER Maven plug-in in a repository somewhere yet? I'm > > suprised an apache project is not in a maven2 repo. > > 2. Where would I find more recent updates? > > 3. Does anyone have a recommendation for an automated testing tool like > > > JMETER (record or create scripts that are played back) that they feel is > > > better? > > > > Thank you! > > > > > > > > > > The information contained in this e-mail and any accompanying documents > may contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately alert > the sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents > of this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure > compliance with our internal policies and to protect our business. E-mails > are not secure and cannot be guaranteed to be error free as they can be > intercepted, amended, lost or destroyed, or contain viruses. You are > deemed to have accepted these risks if you communicate with us by e-mail. > > > > > > _________________________________________________________________ > Hotmail® is up to 70% faster. Now good news travels really fast. > http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009 > > > > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. > > _________________________________________________________________ Hotmail® is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
