The GTK error was mentioned by someone else recently - check the archives.

Non-GUI mode is likely to be better for you than remote mode, as this
is currently not very efficient: all the data has to be sent back to a
single server, which becomes a bottle-neck, or the link to it may.

You may find that a single non-GUI instance of JMeter is sufficient to
run 150 sessions.

If not, use two systems, and combine the data afterwards.

Remove all listeners from the test plan; just save the data in the jtl
file using the -l flag.

Add a summariser if you want to follow the progress of the test.

S.
P.S. Email was in text format.
On 08/03/06, Oliver Erlewein (DSLWN) <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I'm new to the list. Please excuse if this mail is text and HTML I'm
> trying to send with Outlook and did say that the message should be plain
> text only but I don't really trust M$ to do just that. If it doesn't
> work I'll switch to webmail so excuse the possible breach of form.
>
> Now to my problem. I'm tasked with doing a performance test for the
> project I'm working for. Pretty basic HTTPS frontend with LOTS of HW
> behind it to handle big loads. The load I need to generate will be more
> than on PC can drive. So I'll have to build a bigger test harness that
> can drive min. 150 HTTPS sessions concurrently indefinitely.
>
> I'm using JMeter 2.1.1 with Java 1.4.2. It's all running fine on my
> notebook (WinXP, Internal IP 172.22.1.120) and a second notebook (WinXP,
> IP 172.22.1.205). I can even set the second notebook up as a
> jmeter-server. Now the jmeter-servers I want to set up are Linux Fedora
> Core 4 machines that only run the most necessary stuff so that I can get
> more grunt out of them. There should be no X window system of any kind
> on the system.
>
> So I have a test server set up with FC4 and it's on 172.22.2.32. Now I
> have 2 problems.
>
> 1) I've imported a small test jmx to run in text mode so that I can see
> that the jmeter is working. When I start it (./jmeter -n -t 'UAT -
> Simple Login.jmx') it returns the following:
>
> Created the tree successfully
> Starting the test
>
> (.:3172): Gtk-WARNING **: cannot open display:
>
> Now I've searched Google and it seems as if jmeter is trying to do
> something with X-windows. Has anybody any idea what I'm seeing? The
> jmeter.log said:
>
> 2006/02/09 10:51:49 INFO  - jmeter.util.JMeterUtils: Setting Locale to
> en_US
> 2006/02/09 10:51:49 INFO  - jmeter.JMeter: Version 2.1.1
> 2006/02/09 10:51:49 INFO  - jmeter.JMeter: java.version=1.4.2
> 2006/02/09 10:51:49 INFO  - jmeter.JMeter: Locale=en (US)
> 2006/02/09 10:51:49 INFO  - jmeter.JMeter: Copyright (c) 1998-2005 The
> Apache Software Foundation
> 2006/02/09 10:51:49 INFO  - jmeter.JMeter: Loading file: UAT - Simple
> Login.jmx
> 2006/02/09 10:51:50 INFO  - jmeter.samplers.SampleResult: Note: Sample
> TimeStamps are END times
> 2006/02/09 10:51:50 INFO  - jmeter.samplers.SampleResult:
> sampleresult.default.encoding is set to ISO-8859-1
> 2006/02/09 10:51:50 WARN  - jmeter.save.SaveService: Could not set up
> alias WebServiceSampler java.lang.NoClassDefFoundError: while resolving
> class: org.apache.jmeter.protocol.http.sampler.WebServiceSampler
> 2006/02/09 10:51:50 INFO  - jmeter.save.SaveService: Using SaveService
> properties file 1.7
> 2006/02/09 10:51:50 INFO  - jmeter.protocol.http.sampler.HTTPSampler2:
> httpsampler2.basicauth=false
> 2006/02/09 10:51:50 INFO  - jmeter.save.SaveService: All converter
> versions present and correct
> 2006/02/09 10:51:51 INFO  - jmeter.engine.StandardJMeterEngine: Running
> the test!
>
> Which seems to tell me that something's happening. I've got the hunch
> it's just a Linux setup thing.
>
> 2) When I run jmeter-server all seems to be fine. Rmi is running, jmeter
> is running but when I want to connect the client machine (where jmeter
> display runs) gives me the foillowing errors in the jmeter.log:
>
> 2006/03/09 09:52:15 INFO  - jmeter.engine.ClientJMeterEngine: about to
> run remote test
> 2006/03/09 09:52:15 INFO  - jmeter.engine.ClientJMeterEngine: done
> initiating run command
> 2006/03/09 09:52:15 INFO  - jmeter.engine.ClientJMeterEngine: running
> clientengine run method
> 2006/03/09 09:52:15 INFO  - jmeter.engine.ConvertListeners: num threads
> = 1
> 2006/03/09 09:52:15 INFO  - jmeter.engine.ConvertListeners: num threads
> = 1
> 2006/03/09 09:52:15 INFO  - jmeter.samplers.StandardSampleSender: Using
> Standard Remote Sampler for this test run
> 2006/03/09 09:52:15 INFO  - jmeter.samplers.StandardSampleSender: Using
> Standard Remote Sampler for this test run
> 2006/03/09 09:52:15 INFO  - jmeter.samplers.StandardSampleSender: Using
> Standard Remote Sampler for this test run
> 2006/03/09 09:52:15 INFO  - jmeter.samplers.StandardSampleSender: Using
> Standard Remote Sampler for this test run
> 2006/03/09 09:52:16 ERROR - jmeter.engine.ClientJMeterEngine:
> java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested
> exception is:
>         java.net.ConnectException: Connection refused: connect
>         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
>         at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown
> Source)
>         at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown
> Source)
>         at sun.rmi.server.UnicastRef.invoke(Unknown Source)
>         at
> org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub.setHost(Unknown
> Source)
>         at
> org.apache.jmeter.engine.ClientJMeterEngine.run(ClientJMeterEngine.java:
> 123)
>         at java.lang.Thread.run(Unknown Source)
> Caused by: java.net.ConnectException: Connection refused: connect
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(Unknown Source)
>         at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
>         at java.net.PlainSocketImpl.connect(Unknown Source)
>         at java.net.Socket.connect(Unknown Source)
>         at java.net.Socket.connect(Unknown Source)
>         at java.net.Socket.<init>(Unknown Source)
>         at java.net.Socket.<init>(Unknown Source)
>         at
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown
> Source)
>         at
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown
> Source)
>         ... 7 more
>
>
> I hope someone can point me in the right direction to fix this. (As
> another info, the 172.22.xx.xx is one subnet!) I don't know where the
> 127.0.0.1 comes from.
>
> Thanx for the help and the jmeter-user list has already helped a lot! So
> thanx 4 all guys (and gals ;-)
>
> Cheers from Wellington (NZ)
> Oliver Erlewein
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to