BTW, the Java version is shown at the start of the jmeter.log file.

On Wed, 27 Oct 2004 16:17:20 -0600, Earl Lewis <[EMAIL PROTECTED]> wrote:
> Holy moly Sarah - you nailed it! The Oracle client tools were hijacking the JVM in 
> the system path. Putting them at the end of the path worked!!
> 
> Thank you sooooo much! I've been staring at this problem for 2 days and was frankly 
> getting a little sick of it. I never would have thought to look at that.
> 
> Earl
> 
> >>> Bartlett, Sarah<[EMAIL PROTECTED]> 10/27/2004 2:16:21 PM >>>
> 
> 
> I had this problem also even though I had the latest jdk.  What I found was that 
> when I installed Oracle on my machine it put an older jdk in my path in front of the 
> correct one.  I found this out when, on a hunch I did a java -version in the command 
> window and found that it was not showing 1.4.whatever.  Moving the oracle paths to 
> the back of the line fixed it.
> 
> -----Original Message-----
> From: Earl Lewis [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 27, 2004 3:53 PM
> To: [EMAIL PROTECTED]
> Subject: Re: SSL problems
> 
> sebb,
> 
> Thanks for the reply. After your reply I started looking into the Jmeter classpath 
> question - to see what JVM it's pointing to. Here's what the JMeter help says about 
> classpath.
> 
> -- begin help text --
> 
> JMeter automatically finds classes from jars in its /lib and /lib/ext directories. 
> If you want to add other JAR files to JMeter's classpath, then you must copy them to 
> JMeter's "lib" directory. If you have developed new JMeter specific components, then 
> you should jar them and copy the jar into JMeter's /lib/ext directory. JMeter will 
> automatically find JMeter components in any jars found here.
> 
> You can also install utility Jar files in $JAVA_HOME/jre/lib/ext
> 
> Note that setting the CLASSPATH environment variable will have no effect. This is 
> because JMeter is started with "java -jar", and the java command silently ignores 
> the CLASSPATH variable, and the -classpath/-cp options when -jar is used. [This 
> occurs with all Java programs, not just JMeter.]
> 
> -- end help text --
> 
> OK - I'll buy that. If the jars need to go someplace else I'll put them there. So I 
> go find the JSSE jars (jcert.jar, jsse.jar, jnet.jar) and copy them into 
> $JAVA_HOME/jre/lib/ext like the help says - and still no luck. And still the same 
> error - see first post.
> 
> Any suggestions?
> 
> Earl
> 
> >>> sebb<[EMAIL PROTECTED]> 10/27/2004 11:19:18 AM >>>
> On Wed, 27 Oct 2004 11:08:19 -0600, Earl Lewis <[EMAIL PROTECTED]> wrote:
> > I can't seem to get JMeter to process any SSL requests. I downloaded version 2.0.1 
> > to make sure I was current and neither it nor 1.9 will run my test.
> >
> > First, so you know, I'm running a local Jmeter client and trying to hit a site 
> > that's running SSL and is all dynamic content, i.e. lots of request parameters, 
> > intermediate calls and redirects. I'm _not_ doing any remote testing stuff.
> >
> > To start with I recorded a script using Badboy and exported it to Jmeter format. 
> > Opened it in Jmeter and all looked well. However the full script would never run. 
> > In my aggregate report window I would only see two request entries instead of the 
> > 7 or 8 that were in the test plan.
> >
> > Since it was bombing I started stripping stuff out until I got to just a single 
> > HTTPRequest sampler. Even that failed. Here's the error text from JMeter response 
> > in the View Results Tree.
> >
> > java.net.MalformedURLException: unknown protocol: https
> 
> AFAIK, this means that the JVM does not support https - so it's not
> surprising that JMeter fails.
> 
> You may need to install a later JVM, or at least add the necessary
> jars to your existing one.
> 
> >         at java.net.URL.<init>(Unknown Source)
> >         at java.net.URL.<init>(Unknown Source)
> >         at 
> > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.getUrl(HTTPSamplerBase.java:437)
> >         at 
> > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:585)
> >         at 
> > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:573)
> >         at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:254)
> >         at java.lang.Thread.run(Unknown Source)
> >
> > The HTTP request is very simple. I think I've got it right.
> > Name: login
> > server: my.server.name.edu
> > protocol: https
> > port: tried 80 and 443 - both fail
> > method: tried both get and post
> > path: /dept.html - - which redirects to /pls/procs/!maindept.login?
> > redirect automatically: unchecked
> > follow redirects: unchecked
> > use keepalive: unchecked
> >
> > no additional parameters and no file attachments
> >
> > Anyone have any ideas about this one.
> >
> > Earl
> >
> > ---------------------------------------------------------------------
> > 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]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to