Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of sebbaz@gmail.com designates
 66.249.92.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=CkEWT0kd62NP9h1Xf0h5Z9wDW4irE+DloDqdeDE4ck9FimDE7DuvJwnyjlszHj92d9XiWVzkp6UF4qiwskI10SVgMteUxpVbrfc2iqB8CJi/I0ons+O+YcM3g+o8Mrvo2imNiEh/mnpJRwuxzHzW6lV4b5jzQwreqKrjmOFwopc=
Message-ID: <25aac9fc0702051553j1bd7ae08s967d90be05a990f5@mail.gmail.com>
Date: Mon, 5 Feb 2007 23:53:50 +0000
From: sebb <sebbaz@gmail.com>
To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Subject: Re: spurious content from SOAP/XML-RPC Request
In-Reply-To: <5b0b6bb10702041737o5cdd7a45ka49c33f97f87163e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5b0b6bb10702022149w6291938dj4f5317bdb2d410b1@mail.gmail.com>
	 <5b0b6bb10702022158s11ff2337i104c5a0ddaea7460@mail.gmail.com>
	 <25aac9fc0702030244p71eb3405ybec3e0b1d0ca06b6@mail.gmail.com>
	 <5b0b6bb10702031406h68467767xff492fe429844819@mail.gmail.com>
	 <25aac9fc0702031449g2cdef84cjd868ebe14be1f640@mail.gmail.com>
	 <5b0b6bb10702031806s30ddbe90k2c6f0d04f114923a@mail.gmail.com>
	 <25aac9fc0702040357g556251cak886874a1d58bcef@mail.gmail.com>
	 <5b0b6bb10702041737o5cdd7a45ka49c33f97f87163e@mail.gmail.com>

Just for completeness: turns out it's not a bug.

However I have changed the SOAP-RPC sampler to not use chunked
encoding when sending data supplied in the text box.

On 05/02/07, Scott Cederberg <cederber@gmail.com> wrote:
> I have opened a bug regarding this issue and attached a JMX file that
> reproduces the problem.  The bug is #41536.
>
>
>                         Scott
>
> On 2/4/07, sebb <sebbaz@gmail.com> wrote:
> > On 04/02/07, Scott Cederberg <cederber@gmail.com> wrote:
> > > On 2/3/07, sebb <sebbaz@gmail.com> wrote:
> > > > You'e right - sorry, I misread the headers:
> > > >
> > > > Accept: multipart/*
> > > > Content-Length: 873
> > > > Content-Type: text/xml; charset=utf-8
> > > > SOAPAction: "urn:Path/To/Soap#mySoapAction"
> > > > User-Agent: Jakarta Commons-HttpClient/3.0.1
> > > >
> > > > It does seem odd that there are apparent part length markers.
> > > > There is already a content length header which should mean that the
> > > > part sizes are not needed.
> > > >
> > > > Which version of JMeter are you using?
> > >
> > > I'm using JMeter version 2.2.
> > >
> > > I notice that the SOAP Sampler is using the Jakarta Commons HTTPClient
> > > library, which the HTTP Sampler that I've used previously is not.  I
> > > tried using the HTTP Sampler HTTPClient to see if it also inserted
> > > part sizes into a POST request, which it did not on the request I
> > > tried.
> >
> > Looks like a bug in JMeter then, so please create a Bugzilla issue,
> > and attach (*) any relevant files such as jmeter.log and the jmx file
> > (scrub any private data first!). If you can provide a script that
> > shows the fault with a public SOAP server that would be ideal.
> >
> > (*) you need to create the issue before you can attach anything.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org