Return string in View Results Tree in v2.1

Hi all, I have a .jmx script which returns the name from a SOAP/XML-RPC Request into the View Results Tree. The name of the SOAP request exists of strings (like this: ${testcase} - ${errordescription} - ${errorcode} ) which are converted (from a .cvs file) to the actual name (like: TC01 -

Unexpected IO-Traffic local Data Writer needed

Hi, I am supposed to do some performance test. Instead of this I do mainly stability testing. I have eight generator PCs. Each of then simulate 80 Users. The number of simulated user is limited thought the IO capacity of the PC. I start my PCs with the remote start. It is not possible log

RE: Return string in View Results Tree in v2.1

I tried with the 2.1-20050914 nightly, but run into the following Warning. I also don't get any visible respons (except for the green light) that something is happening. 2005/09/15 16:04:09 WARN - jmeter.functions.CSVRead: Thread-3 - invalid column number: 2 at row 0

RE: Substitution in SOAP

Hi, The substitution ${myVariable} still works for me in Jmeter2.1, but actually I use webscarab to contol the jmeter output and response of the SAOP-request. It works fine! Regards, Miklos - To unsubscribe, e-mail:

Re: Return string in View Results Tree in v2.1

The warning means that there aren't enough columns in the data. It would not have appeared in 2.1 because the CSVRead() function was not actually being invoked. Fix the data, and the problem should go away. S. On 15/09/05, Jelmer de Haas [EMAIL PROTECTED] wrote: I tried with the 2.1-20050914

[proposal] - add the feature to allow user classpaths

I'm planning on adding another feature to the 2.1 branch and provide a way for users to add classpaths to JMeter in the GUI. I was thinking of something like User Defined Classpath. Users can then select the jar files they want and the config element will add them to the classloader. Any

Re: [proposal] - add the feature to allow user classpaths

Not sure it's necessary to have a GUI to do this. The additional classpaths are probably known before starting JMeter, so would it not be simpler to use a property to define the extra classpaths? S. On 15/09/05, Peter Lin [EMAIL PROTECTED] wrote: I'm planning on adding another feature to the

Re: [proposal] - add the feature to allow user classpaths

Hi, I think it makes a perfect sense to keep a class paths with a test plan. In this case one will be able to open a new test plan and the class paths will be modified according to plan content. If class paths are set as a properties, one needs to restart JMeter. sebb wrote: Not sure it's