Bug 38694 - UnsupportedEncodingException in Webservice (SOAP) Request
UnsupportedEncodingException in Webservice (SOAP) Request
Status: RESOLVED INVALID
Product: JMeter
Classification: Unclassified
Component: HTTP
2.1.1
Other other
: P3 normal (vote)
: ---
Assigned To: JMeter issues mailing list
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2006-02-17 17:03 UTC by Ronald Sigmund
Modified: 2007-02-12 16:25 UTC (History)
0 users



Attachments
Testplan (10.53 KB, text/xml)
2006-02-17 17:05 UTC, Ronald Sigmund
Details
Resultlog (1.90 KB, text/xml)
2006-02-17 17:05 UTC, Ronald Sigmund
Details
jmeter.log (5.62 KB, text/plain)
2006-02-17 17:06 UTC, Ronald Sigmund
Details
Extended Testplan (15.98 KB, text/xml)
2006-02-20 09:13 UTC, Ronald Sigmund
Details
New Jmeter.log (14.11 KB, text/plain)
2006-02-20 09:15 UTC, Ronald Sigmund
Details
Resultlog for the extended Testplan (5.60 KB, text/xml)
2006-02-20 09:19 UTC, Ronald Sigmund
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ronald Sigmund 2006-02-17 17:03:51 UTC
I tested the WebService(SOAP) Request and the Soap/XML-RPC Sampler. 
The WebService(SOAP) Request interprets the encoding and charset not correctly.

jmeter.log:
Could not decode response java.io.UnsupportedEncodingException: text/xml;
charset=utf-8

in the resultlog the field de="text/xml; charset=utf-8" und not de="utf-8"

i will attach a simple testplan, the resultlog and the jmeter.log
Comment 1 Ronald Sigmund 2006-02-17 17:05:01 UTC
Created attachment 17728 [details]
Testplan
Comment 2 Ronald Sigmund 2006-02-17 17:05:43 UTC
Created attachment 17729 [details]
Resultlog
Comment 3 Ronald Sigmund 2006-02-17 17:06:40 UTC
Created attachment 17730 [details]
jmeter.log
Comment 4 Sebb 2006-02-18 17:03:12 UTC
The jmeter.log file does not seem to be the correct one - I can find no
reference to java.io.UnsupportedEncodingException in it.
Comment 5 Ronald Sigmund 2006-02-20 09:11:15 UTC
Excuse me, I have not controlled the log again.

I have extended the testplan.

My testenvironment:
jmeter -> axis tcpmon(8081) -> axis Simpeserver (8080)

I have restarted the test plan and found out that the Exception comes when one
looks at "View Result Tree" in the GUI. However, this is not the problem. 
The problem consists in the fact that the web service (SOAP) Request, the
Returncode of the server interprets not properly. In the Testresult.jtl one can
see in the last "sample" element, the attributes rc="200" and de = "text/xml;
charset=utf-8 " is. But it should be rc=500 and de=utf-8. The "Soap/XML-RPC
Sampler" last element in Resultlog.jtl do ist correct. Same call, same server
response, different log and sampler.
Comment 6 Ronald Sigmund 2006-02-20 09:13:56 UTC
Created attachment 17744 [details]
Extended Testplan

Testplan with 2 OK und 2 Errorsampler
Comment 7 Ronald Sigmund 2006-02-20 09:15:42 UTC
Created attachment 17745 [details]
New Jmeter.log

Ok, here is the exception.
Comment 8 Ronald Sigmund 2006-02-20 09:19:19 UTC
Created attachment 17746 [details]
Resultlog for the extended Testplan

i had run the testplan several time. the last 4 elements are:
 2 x OK
 2 x Error
the sample element can't interpret the encoding
Comment 9 Sebb 2006-04-13 21:09:40 UTC
Sorry for the delay in attending to this.

The dataEncoding (de) field should now be set correctly from the charset
attribute in the Web Service (SOAP) Request sampler.

The code has been updated in the 2.1 branch, and is in the nightly 2-1.20060413

If you do get a chance to test it, please update this issue. Thanks.
Comment 10 Ronald Sigmund 2006-06-08 08:03:49 UTC
Apology for my late answer. The Encoding is now ok. 
Unfortunately the Resultcode is not set correctly. It is always 200, even if the
server supplies an error. But that is perhaps another error.
Comment 11 Sebb 2006-06-09 15:57:37 UTC
When you say that server errors are not detected, what do you mean?

JMeter won't set the status to error unless the sample itself fails, i.e. 
there is a problem getting the reply document.

If the reply is returned OK, then you need an Assertion to check the contents.

Or is there some other generic error indicator that JMeter is not detecting?