Hi paul,
The trace I pasted is the result of the jersey logging filter.
Thats how i knew jmeter sent something different from a browser or the java client using jersey.
Le 13 oct. 2010 à 13:49, Paul Sandoz <Paul.Sandoz_at_oracle.com> a écrit :
>
> Hi,
>
> Can you enable Jersey logging so that we can see what Jersey receives rather than what jmeter claims to send? alternative using a network snooper would be another way.
>
> FWIW the jmeter output looks correct, but Jersey is throwing the exception because it attempts to obtain a body part as a String value and it claims the media type of the body part is not text/plain, implying there is a Content-Type explicitly declared to something other than text/plain.
>
> You could also verify the content-type explicitly before you call FormDataBodyPart.getValue just to check assumptions.
>
> Paul.
>
> On Sep 24, 2010, at 6:34 PM, EZZAT Mani wrote:
>
>> Hi Paul and thanks for your answer.
>> Here's the request log sent by Jmeter :
>> Accept-Language: fr,en;q=0.8,fr-fr;q=0.5,en-us;q=0.3
>> Content-Length: 7716
>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>> Accept-Encoding: gzip,deflate
>> Keep-Alive: 115
>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0E)
>> Connection: close
>> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
>> Content-Type: multipart/form-data; boundary=---------------------------7d159c1302d0y0
>> POST data:
>> -----------------------------7d159c1302d0y0
>> Content-Disposition: form-data; name="charset"
>> Content-Type: text/plain; charset=ISO-8859-1
>> Content-Transfer-Encoding: 8bit