Hi Felix,

I finally tested Version r1676403 , (build on April, 28).
It fixes the problem, that now is logged as a protocol error, without any 
exception.

The originating problem was a 307 HTTP return code, with no URL specified in the header, while the sampler had the "follow redirect" flag set.
These conditions caused the exception, without much details.

The target URL is specified is the payload, but obviously this could be not 
used by Jmeter.

Again, thank you very much for your support.
Regards

Sergio


Il 26/04/2015 13.57, Felix Schumacher ha scritto:
Am 26.04.2015 um 13:07 schrieb Felix Schumacher:
Am 26.04.2015 um 11:17 schrieb Sergio Boso:
Hi everybody,

in a rather large test environment, I'm facing the following error:

2015/04/24 16:44:47 ERROR - jmeter.samplers.SampleResult: sampleEnd called 
twice java.lang.Throwable: Invalid call sequence
    at org.apache.jmeter.samplers.SampleResult.sampleEnd(SampleResult.java:1064)
    at 
org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:421)
This is in a catch-Block when a RuntimeException was thrown. It will try to set the sample endtime, which can be set previously in line 355.

The exception would be logged one line later in line 422, but we will of course not get there. So the first thing I will do, is to swap the log line and the sample end call. That way you should be able to see the reason for the RuntimeException.

If you want to try the patch yourself, I will (try to) attach it to this mail.

After that I will try to fix the double setting of the sample end.
Should be fixed in the next nightly and release. I have created an issue at

https://bz.apache.org/bugzilla/show_bug.cgi?id=57858.

It would be nice, if you could test it and give feedback. To see the exceptions that caused the double call, you might want to enable debug logging on org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl in bin/user.properties.

Regards
 Felix

Regards
 Felix

    at 
org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:74)
    at 
org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1146)
    at 
org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1135)
    at 
org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:434)
    at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:261)
    at java.lang.Thread.run(Unknown Source)

in the sample result field, I get the following message:
    Non HTTP response code: java.lang.IllegalArgumentException

_Environment information:_
- Jmeter 2.13, r1665067
- distributed environment, 4 slaves, with Windows 2012: the error is evenly 
distributed
- the master just harvests results, non GUI mode
- JVM:
    java version "1.7.0_55"
    Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
    Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)

Other info:

 *      this does *not* happen when running a single thread
 *      this happens only on a specific sampler, error rate is around 10%
 *      the sampler is a pretty simple HTTPS GET operation, Http4 client 
implementation
 *      I also get several other errors, like 503 and connection exception: 
global error rate is around 1%

The last info brings me to guess that  this is induced by a server-side error, 
however I cannot guess what is going on.
Unfortunately, the test is reserved and I cannot share the script and login 
information.

Any though? suggestions? other possible tests to do?

Thank you in advance, best regards

Sergio


---------------------------------------------------------------------
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