Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
Running the bench tool, the customer get Java errors like those :
jmeter.util.XPathUtil: Type=Val=false Tol=false org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
1492094215983,21037,/qlikview/,Non HTTP response code: java.net.ConnectException,Non HTTP response message: Connection timed out: connect,QlikView 1-1,text,false,1888,1,1,0
He sent me the attached file also.
Thanks for the help
Hi,
The attached file do not contain the "Non HTTP response....", so we might be dealing with two problems here.
For the problems that I see from the attachment. The failures are on QvAJAXZfc/AccessPoint.aspx with HTTP 404 response.
The most common mistake here is the wrong URL to the document. For example providing Access Point URL in the config file (like: http://test.target.com/qlikview/index.htm) instead of URL pointing to document that should be tested (example: http://test.target.com/QvAJAXZfc/opendoc.htm?document=SC_BenchmarkApp1_200M.qvw&host=Local)
I would also suggest to check if the recommended JVM is installed (64-bit version is required), and run Benchmarking test from admin command line window.
In case of problems, please let us know.
Best regards,
Pawel
> The most common mistake here is the wrong URL to the document
The URL used was the right one.
The JVM also was OK.
Test were run with an admin account.
Hi,
Sorry for late reply.
Could you please clarify which errors are we dealing with right now.
The one mentioned by cpo in the description are not matching the one I saw in the excel file.
Another thing that comes to my mind if it comes to setup is the configuration of WebServer and setting the header authentication. Could you please check if it setup according to documentation?
The next step will be to try to run the test. You can choose to run only the 1 group. If first test fails it will not continue.
You can attach the following files:
- 01BenchmarkApp1-PreLoad-LoC text file found in Results
- jmeter.log file found in bin subfolder of JMeter.
This might help us to further investigate the issue.
We have identified some breaking changes between JMeter 3.0 and 3.2
If you're using Jmeter 3.2 please try with Jmeter 3.0 (https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-3.0.zip)