Hi,
The order of the elements in the test was like:
Test plan==> Thread Group======> OS Process Sampler======> Debug Sampler======>
Beanshell Post Processor======> HTTP Cookie Manager======> HTTP Request (this
does the POST)======> View Results Tree======> Summary
I hadn't tried changing the position before I changed to using the Debug Post
Processor.
Why would that Debug Sampler be position sensitive, to the point that it would
cause the "unknown_ca" error on the HTTP request?
Thanks,Jim
On Thursday, August 22, 2019, 2:48:59 PM UTC, Felix Schumacher
<[email protected]> wrote:
Am 22.08.19 um 13:03 schrieb [email protected]:
> Hi,
> I think that I found the problem, and it is really weird! I had included a
> Debug Sampler in the modified test plan so that I could double-check that it
> was using the different parameter values, but I think I just found that if I
> disable that Debug Sampler, then the test plan starts working. However now I
> need to figure out way to see/check that the test plan is actually rotating
> through the CSV file.
> Is there something wrong with including the Debug Sampler? I notice there is
> a different Debug element, the Debug Post processor.
>
> It looks like adding in that Debug Post processor instead of the Debug
> Sampler, the modified test plan works!!
Where have you defined the Beanshell post processor? Might it be in a
position that it is applied to the debug sampler?
Felix
> Jim
>
>
>
> On Thursday, August 22, 2019, 9:25:27 AM UTC, Felix Schumacher
><[email protected]> wrote:
>
>
>
> Am 22. August 2019 11:21:30 MESZ schrieb "[email protected]"
> <[email protected]>:
>> Hi,
>> No, I am not sending client certs from the Jmeter at all. That is the
>> puzzling thing. Again, the weird thing is that this test plan was
>> working fine until I tried to change that one command line parameter in
>> the OS Process Sampler to a variable that comes from the CSV element.
> What happens, when you use the old test again?
>
> Have you checked all certificates (including those of the servers) for
> expiration?
>
> Felix
>> Jim
>>
>> On Thursday, August 22, 2019, 7:39:56 AM UTC, Felix Schumacher
>> <[email protected]> wrote:
>>
>> Are you using client certificates for authentication? Maybe they are
>> expired?
>>
>> Regards
>> Felix
>>
>> Am 22. August 2019 00:06:03 MESZ schrieb "[email protected]"
>> <[email protected]>:
>>> Hi,
>>> As I described previously, I have a test plan that has:
>>> - OS Process Sampler ==> Runs a Java app to produce string for a
>>> POST BODY - HTTP Request ==> Does an HTTP POST to a URL like
>>> "https://xxxxx/...";
>>> This test plan was working fine.
>>> The OS Process Sampler was running a Java command line and that
>>> included a file path as one of the parameters, but I wanted to
>>> parameterize that file path parameter, getting the file path from a
>> CSV
>>> element.
>>> So I created a text file, "list-gsp-parameter-files.csv" that
>> contains:
>>> D:\\gxjxl03\\properties\\test.properties,111
>>> D:\\gxjxl03\\properties\\test.properties,222
>>> However, when I run the test plan now, it is getting an error when it
>>> does the HTTP request, I am getting this error:
>>>
>>> javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca
>>> at sun.reflect.GeneratedConstructorAccessor58.newInstance(Unknown
>>> Source)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
>>> Source)
>>> at java.lang.reflect.Constructor.newInstance(Unknown Source)
>>> at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown
>>> Source)
>>> at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown
>>> Source)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown
>>> Source)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown
>>> Source)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
>>> Source)
>>> at java.net.HttpURLConnection.getResponseCode(Unknown Source)
>>> at
>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown
>>> Source)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPJavaImpl.readResponse(HTTPJavaImpl.java:268)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPJavaImpl.sample(HTTPJavaImpl.java:570)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:74)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.followRedirects(HTTPSamplerBase.java:1542)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.resultProcessing(HTTPSamplerBase.java:1636)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPAbstractImpl.resultProcessing(HTTPAbstractImpl.java:525)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPJavaImpl.sample(HTTPJavaImpl.java:644)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:74)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1189)
>>> at
>>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1178)
>>> at
>>> org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:490)
>>> at
>>> org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:416)
>>> at
>>> org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:250)
>>> at java.lang.Thread.run(Unknown Source)
>>>
>>> I can't figure out why, with just making the change that I made to the
>>> test plan, the HTTP Request is all of a sudden getting that
>>> "unknown_ca" error, when it was working fine before?
>>> Does anyone know what might be wrong, and also how I can get this
>>> fixed?
>>> Thanks,Jim
> ---------------------------------------------------------------------
> 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]
