On 11/14/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > there's a setting in jmeter.properties. change it from INFO to DEBUG and > rerun it. if there's an error happening with Apache SOAP, it should output > the error to jmeter.log.
Not doing much more than changing that and restarting JMeter seems to have fixed my problem! I can now send SOAP to my server and get it back. Now I have another problem though :o( I have my WebsService Sampler in a ThreadGroup with a CSV Data Set Config. The WebServiceListener has some $[variable} entries in and they are correctly substituted: but the CSV file line counter is never incremented, so the substitution accessed each time is the same one (the first line of the file). Is this a bug or have I misunderstood something? The same config with the same CSV file worked the JDBC Sampler, and intelligently moved on to the next line in the CSV with each new thread or repeat. If it is a bug, is there a workaround? I've found another bug, too. When you run a test, perform Clear All, then re-run it, the Results Tree output for the WebService Sampler remains blank, showing just the URL and "null". I suspect the Clear All method breaks something. Only restarting JMeter seems to fix this -- that's why I spent so long chasing my tail yesterday, assuming JMeter had problems it didn't have!
