Bug 41878 - JMeter GUI crashes when performing SOAP requests
Summary: JMeter GUI crashes when performing SOAP requests
Status: RESOLVED WONTFIX
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 2.2
Hardware: PC Windows XP
: P2 major with 1 vote (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-17 15:09 UTC by Michael Doris
Modified: 2009-05-08 18:39 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Doris 2007-03-17 15:09:38 UTC
I am using JMeter to stress a SOAP server and JMeter keeps crashing whenever I
simulate a server load of greater than 2 threads.

There isn't anything in the log that gives me an indication of the problem, and
the server being tested against keeps processing the SOAP request after JMeter
crashes.

The following is the log from the last test run:

2007/03/17 14:49:09 INFO  - jmeter.engine.StandardJMeterEngine: Starting 3
threads for group Thread Group. Ramp up = 1. 
2007/03/17 14:49:09 INFO  - jmeter.engine.StandardJMeterEngine: Continue on error 
2007/03/17 14:49:09 WARN  - jmeter.threads.JMeterThread:
jmeterthread.startearlier=true (see jmeter.properties) 
2007/03/17 14:49:09 INFO  - jmeter.threads.JMeterThread: Thread Thread Group 1-1
started 
2007/03/17 14:49:10 INFO  - jmeter.threads.JMeterThread: Thread Thread Group 1-2
started 
2007/03/17 14:49:10 INFO  - jmeter.threads.JMeterThread: Thread Thread Group 1-3
started 
2007/03/17 14:49:10 INFO  - jmeter.threads.JMeterThread: Thread Thread Group 1-1
is done 
2007/03/17 14:49:10 INFO  - jmeter.engine.StandardJMeterEngine: Ending thread 0 
2007/03/17 14:52:49 INFO  - jmeter.threads.JMeterThread: Thread Thread Group 1-2
is done 
2007/03/17 14:52:49 INFO  - jmeter.engine.StandardJMeterEngine: Ending thread 1
Comment 1 Sebb 2007-03-17 16:12:34 UTC
There's not enough information here to do anything; and the logfile extract is 
incomplete.

Please *attach* the full jmeter.log.

Also were there any errors in the console window? JMeter tries to log all 
errors, but some are logged to the console.
Comment 2 Michael Doris 2007-03-19 13:29:01 UTC
The problem was shown in the console, I missed it the first time, OutOfMemory.

Can resolve, but seems strange that it should be getting out of memory with the
default 256M footprint, no input params beyond the SOAP envelope, and only 16M
response size.

This was with the reading SOAP response turned on.
Comment 3 Sebb 2007-03-19 14:07:32 UTC
If you can reproduce the error, please can you post the console error message?

We can then see if it is possible to capture the error and log it properly.

Thanks!
Comment 4 Michael Doris 2007-03-19 14:28:13 UTC
Exception java.lang.OutOfMemoryError: requested 36052328 bytes for promotion.
Out of swap space?

This is with 3 simultaneous response of 16M each. 256M starting Heap and 256M
max Heap.
Comment 5 Sebb 2007-03-19 15:15:52 UTC
Was there no stack trace?

Or any other context?

Without further information, there's not a lot can be done.
Comment 6 Michael Doris 2007-03-19 16:19:02 UTC
What I posted is the only output in the console. There is no stack trace or dump
of any kind.
Comment 7 Sebb 2007-03-20 13:49:08 UTC
Which SOAP sampler were you using?
Comment 8 Michael Doris 2007-03-20 15:47:18 UTC
Webservice (SOAP) Request
Comment 9 Sebb 2007-03-30 10:13:32 UTC
Try using one of the recent nightly builds.
Comment 10 Sebb 2007-09-02 10:01:27 UTC
See also bug 41921
Comment 11 Sebb 2009-05-08 18:39:57 UTC
There's not a lot can be done here
Comment 12 The ASF infrastructure team 2022-09-24 20:37:39 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1888