I had actually tried that before mailing to the list. I just tried it again with no change to whether cookies are sent or not.
I can't find the log file, but here's my java version: C:\Program Files (x86)\Console2>java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) C:\Program Files (x86)\Console2> Windows 7 x64 thanks, Daniel On Fri, May 27, 2011 at 3:03 AM, sebb <[email protected]> wrote: > On 27 May 2011 08:48, sebb <[email protected]> wrote: >> On 27 May 2011 06:47, Daniel Watrous <[email protected]> wrote: >>> Hello, >>> >>> I've been trying to setup a jmeter program to test a wordpress plugin. >>> However, I can't get the login to work. It appears to be sending the >>> cookies back correctly when the login is sent, but they don't get >>> picked up by the cookie manager. >>> >>> I've been searching for a while and looked at dozens of examples. >>> Maybe you can spot what I've done wrong from these screenshots: >>> >>> http://screencast.com/t/EW1zAgvlK >>> http://screencast.com/t/2i8dTyBh >>> http://screencast.com/t/fd5dGPvCb >> >> The Cookie Manager is set to require RFC2109 cookies; these have a >> specific format that is not always followed by servers (or browsers). >> >> The default is supposed to be "compatibility" mode, try using that. >> >> What version of Java are you using? This will be shown near the start >> of the jmeter.log file, e.g. >> >> java.version=1.5.0_22 >> java.vm.name=Java HotSpot(TM) Client VM >> >> I've just noticed that the default when adding a new Cookie Manager is >> set correctly to "compatibility" (first option) when using that > > Actually it's the last option when using Java 1.5, first when using > 1.6 - which is where the problem lies ... > >> version, however when using >> >> java.version=1.6.0_25 >> java.vm.name=Java HotSpot(TM) Client VM >> >> which is the current Java version it is set to "rfc109" (the last option). >> >> This is odd, since the code specifically tries to set "compatibility" mode. >> Looks like there may be a Java bug (or at least a change in behaviour). > > It's a change in Java behaviour - the order of cookie policies is > different, because of internal changes to the libraries. > > JMeter incorrectly relies on the order of the entries. Oops. > > However, there's an easy work-round - just change the policy to compatibility. > >> >>> Thanks in advance. >>> >>> Daniel >>> >>> --------------------------------------------------------------------- >>> 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]
