hmm... if the expiration date is in the past, (ie older than today ) that could be the cause. AFAIK, the httpsampler just sets the header, so it could be Sun's httpconnection class handles it that way.
peter On 10/18/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. > > >
