On 08/09/06, Bruno Charloup <[EMAIL PROTECTED]> wrote:
Hi all, i'm running a test with JMeter 2.1.1 under windows xp (sp2).
The latest version is 2.2, and has lots of fixes compared with 2.1.1
My script create and update data in a mysql database. When running my test with Jmeter, I've no error in my listener result tree, but when I look at the data in my database, it seems that not all the operations were made. That the reason why I glance at the file Jmeter.log. In this file I've got many lines like the following : 2006/09/08 09:12:16 ERROR - jmeter.threads.JMeterThread: java.lang.IllegalArgumentException: protocol = http host = null
This means that at least one of the arguments was wrong. Most likely "host", which should probably not be "null". "protocol" looks OK.
at sun.net.spi.DefaultProxySelector.select(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source) at org.apache.jmeter.protocol.http.sampler.HTTPSampler.disconnect(HTTPSampler.j ava:468)
This suggests that the code is trying to disconnect the connection.
at org.apache.jmeter.protocol.http.sampler.HTTPSampler.sample(HTTPSampler.java: 462) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBa se.java:544) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBa se.java:533) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:247) at java.lang.Thread.run(Unknown Source) As I'm not a java developper, I don't undestand this message (it's clearly an error, but what is the link with my script ?).
There is no direct link with your script - it is not possible to find out which line of the script is being executed from the stack dump. The dump is mainly of use for developers. The intention is always to catch the error where it occurs, in which case more useful information can normally be provided. However, it is difficult to anticipate all the possible errors that can occur, and so the default is to log the stack trace as has happened here. Someone with access to the appropriate source may be able to work out what went wrong from the stack trace, which includes the line numbers in the code. But even that may be insufficient to determine the cause, as that may depend on the values of data items that are not shown.
Thanks in advance for any help.
I suggest you upgrade to 2.2 and see if the problem recurs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
