On 11/04/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I'm happy to provide logs or details, if there is any way to do that?
Probably best to create a Bugzilla issue, and then re-open it. You can then attach files to it. Remember to obscure any private information first. FIles needed are: jmeter.log JMX file
Basically it works (securely) if i specify http, so presumably some code
Where are you specifying http?
somewhere is falling back to https. If i specify https it does seem to
There is no such code that I know of. Perhaps your server is forwarding the request? Might be worth including the port number in the https request.
connect to our server, however the server responds with errors. Implying something was wrong in the request. > On 10/04/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Ok, this is resolved. Ha. The change seems to be that even though the >> XML service is https, the url used must be http otherwise it doesnt >> work. > > Not sure I understand the above. > > How can it work at all if the XML service is https and the URL is http? > > There may well be a problem here, but I'm not sure what it is, which > makes it difficult to fix ... > >> The traffic is indeed encrypted. >> >> It would probably be worth while working out which change caused this >> and >> highlighting it on: >> >> http://jakarta.apache.org/jmeter/changes.html > > The SOAP/RPC sampler was changed in 2.2 to use HTTPClient instead of > the default Java HTTP protocol, which is presumably what caused the > change you are seeing. > >> Thanks, >> Dan >> >> > Sorry for replying to my own post, but here's some further info. >> > >> > In JMeter 2.1 a request in the results tree looks like this: >> > >> > POST >> > https://messaging_450:450/scanner-messaging/ScannerMessagingServiceXmlRpc >> > Query data: >> > >> > However in 2.2 it looks like this: >> > >> > https://messaging_450:450/scanner-messaging/ScannerMessagingServiceXmlRpc >> > >> > [no cookies] >> > >> > Request Headers: >> > >> > Is that relevant? >> > >> > Whats also interesting, is if i change the protocol to http, in jmeter >> > 2.1, I get an error message back about tallking non ssl to a ssl host. >> > (which is correct.) in jmeter 2.2 i get a message back from my >> application >> > server, so it seems that jmeter has detected ssl in use and fallen >> back to >> > it despite the explicit use of http. >> > >> > Thats ok; However it means i can't packet sniff the actual request, >> and >> > find out why the same script fails in jmeter 2.2 and passes in 2.1. >> > >> > >> > >> >> The sampler is a "SOAP/XML-RPC Request" and the data file is loaded >> via >> >> "CSV Data Set Config". >> >> >> >>> It would help if you provided some clue as to how you are accessing >> >>> the file, and which samplers you are using. >> >>> >> >>> On 10/04/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >>>> Hi, >> >>>> >> >>>> We've just tried updating to jmeter 2.2 and after resolving the ssl >> >>>> issues >> >>>> with test certificates we now have another issue. >> >>>> >> >>>> We have a data file which has a list of items to use in the >> following >> >>>> requests. I've confirmed that jmeter 2.2 does find this file (it >> gets >> >>>> 'stored') however the server reports back that the values it >> receives >> >>>> are >> >>>> invalid. >> >>>> >> >>>> Running in the same environment with jmeter 2.1.1 the values are >> >>>> valid. >> >>>> >> >>>> (These are soap xml-rpc requests and the data file is a csv, but >> with >> >>>> a >> >>>> .txt extension) >> >>>> >> >>>> Unfortunately i can't see the exact request anywhere to prove >> exactly >> >>>> what >> >>>> the problem here is. I can see all the responses on both the >> server >> >>>> and >> >>>> back at the client end. Can anyone suggest how to catch the >> requests >> >>>> to >> >>>> see exactly what jmeter has sent? Our server application doesnt >> yet >> >>>> log >> >>>> these values! >> >>>> >> >>>> Thanks, >> >>>> Dan >> >>>> >> >>>> --------------------------------------------------------------------- >> >>>> 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] >> >>> >> >>> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> 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] >> > >> > >> >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- 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]
