Thanks for yuour reply. I'm using Jmeter 2.4.20110623. I didn't manage to run the script with the SOAP/XML-RPC sampler. It gives the following output:
java.io.IOException: Stream closed at java.io.BufferedInputStream.getBufIfOpen(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.commons.httpclient.ContentLengthInputStream.read(ContentLengthInputStream.java:170) at java.io.FilterInputStream.read(Unknown Source) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:108) at java.io.FilterInputStream.read(Unknown Source) at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:127) at org.apache.jmeter.protocol.http.sampler.SoapSampler.sample(SoapSampler.java:277) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:965) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:951) at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:350) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:245) at java.lang.Thread.run(Unknown Source) I haven't find out yet, why the above error occured. Kind regards, Mark ________________________________________ Van: sebb [[email protected]] Verzonden: maandag 25 juli 2011 11:05 Aan: JMeter Users List Onderwerp: Re: Proxy problems using JMeter for webservices On 25 July 2011 09:55, Schut, Mark <[email protected]> wrote: > Hi all, > > While using JMeter for testing webservices, we have a problem getting through > the proxy. When we fire a SOAP message into the endpoint, we get the > followinging JMeter message: > > "Response message: Error opening socket: java.io.IOException: Unable to > tunnel through <proxyserver>:<portnr>. Proxy returns "HTTP/1.1 407 > Proxy Authentication Required ( The ISA Server requires authorization to > fulfill the request. Access to the Web Proxy service is denied. )"" > > We start JMeter as described with the following commandline: > > jmeter.bat -H <proxyserver> -P <portnr> -u <username> -a <password> > > We have copied the proxy settings and message from a SOAPui project, in which > the SOAPui script is correctly working and is able to get through the proxy. > > Does anyone know what the problem could be? For example, do we need to find a > solution in the configuration settings of JMeter or is there a possibility > that JMeter (as application) has been blocked by the proxy server. > > If you need anymore information, please let me know. Which sampler are you using? If you are using the WebService(SOAP) request try using SOAP/XML-RPC instead. Which version of JMeter? > Thanks in advance, > Mark > > Disclaimer: > This message contains information that may be privileged or confidential and > is the property of Sogeti Nederland B.V. or its Group members. It is intended > only for the person to whom it is addressed. If you are not the intended > recipient, you are not authorized to read, print, retain, copy, disseminate, > distribute, or use this message or any part thereof. If you receive this > message in error, please notify the sender immediately and delete all copies > of this message. > > --------------------------------------------------------------------- > 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] Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
