Friends,
I have a similar problem, The error i get is the basic one:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:434)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(DashoA6275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(DashoA6275)
at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket
(DashoA6275)
at sun.net.www.protocol.https.HttpsClient.doConnect(DashoA6275)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:386)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:602)
at sun.net.www.protocol.https.HttpsClient.<init>(DashoA6275)
at sun.net.www.protocol.https.HttpsClient.a(DashoA6275)
at sun.net.www.protocol.https.HttpsClient.a(DashoA6275)
at sun.net.www.protocol.https.HttpsClient.a(DashoA6275)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.plainConnect
(DashoA6275)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
(DashoA6275)
at
com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnectionOldImpl.connect
(DashoA6275)
at org.apache.jmeter.protocol.http.sampler.HTTPSampler.sample(
HTTPSampler.java:464)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(
HTTPSamplerBase.java:590)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(
HTTPSamplerBase.java:578)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:281)
at java.lang.Thread.run(Thread.java:536)
I have done following steps so far:
1) copied jsse.jar in jmeter's lib directoy to get into the classpath.
2) specified following in jmeter.properties
ssl.provider=com.sun.net.ssl.internal.ssl.Provider
ssl.pkgs=com.sun.net.ssl.internal.www.protocol
javax.net.ssl.trustStore=c:/bea81sp2/jdk141_05/jre/lib/security/cacerts
#javax.net.ssl.keyStore=/path/to/keystore
#The password to your keystore
javax.net.ssl.keyStorePassword=password
Please help me whether what i did is correct and what I am missing. Many
thanks
On 2/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> So which password is used as the password is not the one from the
> jmeter.properties file and it is not specified in the command line.
>
> Why do I still get the 'Key not found' if the path to my keystore is
> correct and the password in th jmeter.properties is ok ?
>
> Jan
>
>
> >----- Oorspronkelijk bericht -----
> >Van: sebb [mailto:[EMAIL PROTECTED]
> >Verzonden: dinsdag, februari 14, 2006 03:06 PM
> >Aan: 'JMeter Users List'
> >Onderwerp: Re: SSL Connection problems
> >
> >The properties *are* used by JMeter - as far as I can tell:
> >
> >SSLManager.class
> >protected JmeterKeyStore getKeyStore(){
> >...
> >String fileName =
> >JMeterUtils.getJMeterProperties().getProperty("javax.net.ssl.keyStore",
> >defaultName);
> >System.setProperty("javax.net.ssl.keyStore", fileName);
> >...
> >}
> >
> >Similarly for the password.
> >
> >Most of the entries in jmeter.properties are stored as JMeter
> >properties, and not system properties.
> >
> >The -D command line flag operates on System properties; -J only on
> >JMeter properties.
> >
> >Entries in jmeter.properties are roughly equivalent to -J command-line
> >options, except that they are processed a bit earlier.
> >
> >S.
> >On 14/02/06, Noam Paz <[EMAIL PROTECTED]> wrote:
> >>
> >> Jan,
> >> 1. I didn't change anything in the properties. Below are the entries,
> but JMeter apparently does not use them:
> >> javax.net.ssl.keyStore is NOT in
> /usr/java/jdk1.5.0_02/jre/lib/security/cacerts,
> >> javax.net.ssl.keyStorePassword is NOT changeit
> >> etc.
> >>
> >>
> >> #Classname of the ssl provider to be used (to enable testing of https
> urls)
> >> #And the package name where Stream Handlers can be found
> >> #These provided defaults can be uncommented, and they will work if you
> are using
> >> #Sun's JSSE implementation.
> >>
> >> ssl.provider=com.sun.net.ssl.internal.ssl.Provider
> >> #ssl.provider=iaik.security.jsse.provider.IAIKJSSEProvider
> >> ssl.pkgs=com.sun.net.ssl.internal.www.protocol
> >>
> >> #The location of the truststore (trusted certificates) and keystore (
> if other than the default.
> >> #you can uncomment this and change the path to the correct location.
> >> #javax.net.ssl.trustStore=/path/to/cacerts
> >> javax.net.ssl.keyStore=/usr/java/jdk1.5.0_02/jre/lib/security/cacerts
> >>
> >> #The password to your keystore
> >> javax.net.ssl.keyStorePassword=changeit
> >>
> >> #Alternative protocol of the ssl provider for IAIK JCE + iSaSiLk
> >> #You can also override IAIK specific Providers as well.
> >>
> >> #ssl.pkgs=iaik.protocol
> >> #ssl.provider=com.mycompany.security.provider.SmartProvider
> >> #iaik.provider=com.mycompany.security.provider.SmartSSLProvider
> >>
> >>
> >> 2. I have extracted in DER-format
> >>
> >> Best regards / Viele Grüße
> >>
> >> Noam Paz
> >>
> >>
> >>
> >>
> >>
> >>
> >> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> >>
> >> 14.02.200614:24
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> To
> >>
> "JMeter Users List" <[email protected]>
> >>
> cc
> >>
> Please respond to
> >>
> "JMeter Users List" <[email protected]>
> Subject
> >>
> Re: SSL Connection problems
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Thanks for the advice, but it still gives me the same message. If you
> add the keystore reference to the commandline, where do you set the password
> for it then. Do I have to keep it in the properties file and comment out the
> truststore line and the keystore line ?
> >> When extracting the certificate information, what kind of format do I
> use (DER or Base-64) ?
> >>
> >> Jan
> >>
> >> >----- Oorspronkelijk bericht -----
> >> >Van: Noam Paz [mailto:[EMAIL PROTECTED]
> >> >Verzonden: dinsdag, februari 14, 2006 12:07 PM
> >> >Aan: 'JMeter Users List'
> >> >Onderwerp: Re: SSL Connection problems
> >> >
> >> >
> >> >Jan,
> >> >SSL works for me and the only difference I identify between the
> methods is that I refer to the keystore from jmeter.bat and not from the
> properties:
> >> >
> >> >-
> Djavax.net.ssl.trustStore=C:\Programme\j2sdk1.4.2_05\jre\lib\security\my_root
> >> >
> >> >perhaps worth trying...
> >> >
> >> >Best regards / Viele Grüße
> >> >
> >> >Noam Paz
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >> > "Jan Vangenechten" <[EMAIL PROTECTED]>
> >>
> >> >
> >>
> >> > 13.02.200621:39
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > To
> >>
> >>
> >
> "'JMeter Users List'" <[email protected]>
> >>
> >>
> >
> cc
> >>
> >>
> >
> Please respond to
> >>
> >>
> >
> "JMeter Users List" <[email protected]>
> Subject
> >>
> >>
> >
> SSL Connection problems
> >>
> >> >
> >>
> >> >
> >>
> >> >
> >>
> >> >
> >>
> >> >
> >>
> >> >
> >>
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >I am trying to do SSL connections, but I am not succeeding to get it
> up and
> >> >running.
> >> >I exported my certificate, stored it in the cacerts, put my
> jmeterproperties
> >> >to this file and added the standard changeit password.
> >> >Result :
> >> >
> >> >jmeter.util.SSLManager: Couldn't load keystore java.lang.Exception: No
> key
> >> >found
> >> >
> >> >I tried to export it with other encryption, in other files, tried it
> without
> >> >password (which gave some other error saying I should provide a
> password)
> >> >but it is just not working.
> >> >
> >> >I am using JRE 5 with jmeter 2.1.1
> >> >
> >> >I read a lot about this error, but never saw any answers that can help
> me
> >> >out.
> >> >
> >> >Does anyone have an idea or did anyone succeed in setting up the
> connection
> >> >right and test over SSL.
> >> >
> >> >Best regards,
> >> >
> >> >Jan Vangenechten
> >> >
> >> >
> >> >
> >> >
> >> >---------------------------------------------------------------------
> >> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >For additional commands, e-mail: [EMAIL PROTECTED]
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >--
> >> >
> >> >Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
> >> >
> >> >This e-mail may contain confidential and/or privileged information. If
> you are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
> >> >
> >> >
> >> >
> >> >---------------------------------------------------------------------
> >> >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]
> >>
> >>
> >>
> >>
> >>
> >> --
> >>
> >> Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
> >>
> >> This e-mail may contain confidential and/or privileged information. If
> you are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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]
>
>
--
Manish Joshi
---------------------------------
HP: 81432711
