Re: Mail Visualizer does not show up

2003-01-21 Thread Wolfram Rittmeyer
Finally I must admit that I was wrong, because if you just use the CVS and never built the project with the jar-files in place it will not work. A bout the other issue Mike raised (see below): I will post an enhancement-request to the bug-database. This is a serious issue in my opinion. Greetings,

Re: Remote Testing & memory issues.

2003-01-21 Thread Mike Stover
Is it possible it's running out of stack memory, as opposed to heap? I've had that problem before when I was parsing response HTML for certain things, there's a lot of recursive calls in the parsing of HTML sometimes, and for one particular test, I was running out of stack memory. The 4 proc

Remote Testing & memory issues. [edit]

2003-01-21 Thread Lawrence, Steve
Oops... (it's done about 500 counts) - this was an earlier test with 50 threads & 20 loops. Please forgive my absentmindedness. It hasn't actually finished the 500 count script either. Steve. -- Notice: This e-mail mes

Remote Testing & memory issues.

2003-01-21 Thread Lawrence, Steve
Hi all, I'm seeing some very strange behaviour when running Jmeter in 'distributed mode'. I've successfully gotten my client / server set up, running on Windows 2k. (Still can't get it working under Linux, but that's another story). I've recorded a very small script which hits a couple of urls on

Send file with request is not working for me (using 1.8 version)

2003-01-21 Thread Amos Sonnenwirth
Hi, I'm trying to upload a file with JMeter and resolve the file with Oreilly's MultipartParser class, but when expecting the File part i receive null. I'm sending the following parameters: one parameter: name=string value=yadayada second parameter: is a file with the following deetails FileNam

Re: Remote Testing

2003-01-21 Thread Jordi Salvat i Alabart
Scott Eade wrote: I am pretty sure Jordi patched cvs to allow JMeter to run against jdk 1.3 (and I think even 1.2). Current CVS code compiles and runs on 1.3. 1.2 is proving a tougher task :-( but it's still a target. Salut, Jordi. -- To unsubscribe, e-mail: F

Re: Remote Testing

2003-01-21 Thread Scott Eade
On 21/01/2003 8:18 PM, "Keld Helbig Hansen" <[EMAIL PROTECTED]> wrote: > I'd love to see an explanation on how to do remote testing the 'proper > way'. > Could anyone give a step-by-step guide for newbies on how to do this? > As far as I understand it you need 3 machines - your own workstation > r

RE: Remote Testing

2003-01-21 Thread Keld Helbig Hansen
I'd love to see an explanation on how to do remote testing the 'proper way'. Could anyone give a step-by-step guide for newbies on how to do this? As far as I understand it you need 3 machines - your own workstation running the JMeter GUI, an intermediate JMeter server that sits between your GUI a

RE: Remote Testing

2003-01-21 Thread Martin Samm
> If you got it from cvs HEAD then it is 1.8 plus fixes. i use co with '-r' and the v1_7_3 tag I'll certainly try 1.8 against jdk 1.3 as i;d like to use the latest version. Thanks again for the help Scott. -Original Message- From: Scott Eade [mailto:[EMAIL PROTECTED]] Sent: 21 January 20

Re: Remote Testing

2003-01-21 Thread Scott Eade
On 21/01/2003 7:18 PM, "Martin Samm" <[EMAIL PROTECTED]> wrote: > i got the latest 1.7 version from CVS and it fixed the remote problem. If you got it from cvs HEAD then it is 1.8 plus fixes. > > As for where to run JMeter, the best practices section of the documentation > says to run it on the a

RE: GUI Errors on Sun with nongui.sh

2003-01-21 Thread Martin Samm
Scott, thanks for that - i got the latest 1.7 from CVS and indeed it fixed the remote errors. Thanks -Original Message- From: Scott Eade [mailto:[EMAIL PROTECTED]] Sent: 20 January 2003 21:11 To: JMeter Users List Subject: Re: GUI Errors on Sun with nongui.sh I can't comment on whether

RE: Remote Testing

2003-01-21 Thread Martin Samm
i got the latest 1.7 version from CVS and it fixed the remote problem. As for where to run JMeter, the best practices section of the documentation says to run it on the app server to remove any bottle necks, plus the app server we have is far more capable of running a heavy load then my (rubbish