Try enabling debug, by setting the the following property in jmeter.properties:
log_level.jmeter.protocol.http.control.CookieManager=DEBUG or on the command-line: -Jjmeter.protocol.http.control.CookieManager=DEBUG Might help to narrow down the problem. S. On 18/10/05, Maness, Marty <[EMAIL PROTECTED]> wrote: > I downloaded and installed 1.4.2 and Jmeter is now running through the > whole test correctly(not just stopping). Still having a problem with > the cookie manager though, in the response headers the cookie value for > sessid is not being populated, the expiration date is in the past? > > Marty Maness > Project Manager - DoIT > Phone: 402-280-3931 > Creighton University > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 18, 2005 9:55 AM > To: JMeter Users List > Subject: Re: cookie manager > > The error is "java.lang.NoSuchMethodError" reported from HTTPSampler. > Unfortunately the method name is not shown ... > > This could be caused by trying to use the HTTPS protocol without > having downloaded JSSE (the Java version is 1.3.1.9) > > Java 1.3 is obsolete, and does not always work properly with JMeter. > Try upgrading to 1.4.2 or later. > > Also, it looks as though you _may_ need the JavaMail jars > (activation.jar and mail.jar). These can be obtained from the Java > website. > > See: > > http://jakarta.apache.org/jmeter/usermanual/get-started.html > > for links > > S. > On 18/10/05, Maness, Marty <[EMAIL PROTECTED]> wrote: > > It is sent. There is an error in the log. I was looking at the wrong > > file. > > > > Marty Maness > > Project Manager - DoIT > > Phone: 402-280-3931 > > Creighton University > > > > -----Original Message----- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, October 18, 2005 9:30 AM > > To: JMeter Users List > > Subject: Re: cookie manager > > > > Can you perhaps send me jmeter.log from a run that just stops? > > > > S. > > On 18/10/05, Maness, Marty <[EMAIL PROTECTED]> wrote: > > > I do not get any error messages. It just stops. What's interesting > > is > > > the application is a third party application - so I don't have a > means > > > to talk to the developers, but each request to the server, it sends > > down > > > a new sessionid in an expired cookie? I tried on 2.0.3 and got the > > same > > > results as 2.1.1 > > > > > > Marty Maness > > > Project Manager - DoIT > > > Phone: 402-280-3931 > > > Creighton University > > > -----Original Message----- > > > From: sebb [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, October 18, 2005 9:21 AM > > > To: JMeter Users List > > > Subject: Re: cookie manager > > > > > > If the expiration date is in the past, then the cookie is surely not > > > valid? > > > > > > I think there were some changes since 2.0.0 to fix cookie date > > handling. > > > > > > However, JMeter should not just stop. > > > Any messages in jmeter.log? or the console window? > > > > > > What happens with JMeter 2.0.3? I'd expect it to behave like 2.1.1 > for > > > Cookies. > > > > > > S. > > > On 18/10/05, Maness, Marty <[EMAIL PROTECTED]> wrote: > > > > I'm still having trouble with cookie manager on the new version of > > > > apache 2.1.1. The cookie manager on 2.0.0 works fine for me. A > > > couple > > > > things to note - the expiration date of the cookie sent by the > > server > > > > has an expiration date in the past. Could this be the issue? > > Jmeter > > > > just stops, and in the response data the session id is not set. > Yet > > > on > > > > 2.0.0 the response date, the sessid is set. Using the same exact > > test > > > > plan on both versions. > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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]
