Session Time out message

[mke jira <mk...@gmail.com>]

Hi

My JMeter script was working fine couple of days back, now I get the
following message on some pages. Any idea what could be the problem?
Please let me know.

Session timed out
Your previous session has timed out. You will be automatically redirected to
the home page in 5 seconds...
Click here to go back to the home page immediately.

Re: Session Time out message

[Deepak Shetty <sh...@gmail.com>]

VIEWSTATE is a dynamic value. it must be extracted out form the previous
request.

On Thu, Jul 21, 2011 at 4:06 PM, mke jira <mk...@gmail.com> wrote:

> Thanks. This is AJAX app, and there is a viewstate parameter, when I
> removed
> the parameter it seem to work. Need to run real load and test it out.
>
> Thanks
> Kumar
>
> On Thu, Jul 21, 2011 at 3:24 PM, Bruce Ide <flyingrhenquest@gmail.com
> >wrote:
>
> > It should be fine at the beginning of the test.
> >
> > Hmm... Ah! If you look at the "Path" portion of your HTTP Request, does
> it
> > have a JSESSIONID embedded in it? Sometimes the proxy seems to record
> them
> > that way. Also look in the "Send parameters with request" and make sure
> > there's not one in there. You're probably sending the old session ID
> > somehow, and it's just a matter of finding the old one and removing it so
> > that the cookie manager can do its job.
> >
> > --
> > Bruce Ide
> > FlyingRhenquest@gmail.com
> >
>

Re: Session Time out message

[mke jira <mk...@gmail.com>]

Thanks. This is AJAX app, and there is a viewstate parameter, when I removed
the parameter it seem to work. Need to run real load and test it out.

Thanks
Kumar

On Thu, Jul 21, 2011 at 3:24 PM, Bruce Ide <fl...@gmail.com>wrote:

> It should be fine at the beginning of the test.
>
> Hmm... Ah! If you look at the "Path" portion of your HTTP Request, does it
> have a JSESSIONID embedded in it? Sometimes the proxy seems to record them
> that way. Also look in the "Send parameters with request" and make sure
> there's not one in there. You're probably sending the old session ID
> somehow, and it's just a matter of finding the old one and removing it so
> that the cookie manager can do its job.
>
> --
> Bruce Ide
> FlyingRhenquest@gmail.com
>

Re: Session Time out message

[Bruce Ide <fl...@gmail.com>]

It should be fine at the beginning of the test.

Hmm... Ah! If you look at the "Path" portion of your HTTP Request, does it
have a JSESSIONID embedded in it? Sometimes the proxy seems to record them
that way. Also look in the "Send parameters with request" and make sure
there's not one in there. You're probably sending the old session ID
somehow, and it's just a matter of finding the old one and removing it so
that the cookie manager can do its job.

-- 
Bruce Ide
FlyingRhenquest@gmail.com

Re: Session Time out message

[mke jira <mk...@gmail.com>]

I have HTTP cookie manager config element in my test case.

I have HTTP Cookie Manager at the beginning of the test case, does it make a
difference where the cookie manager is added, I mean does it make a
difference if it is at the beginning vs it is at the end of test plan.

Please let me know.

Thanks
Kumar

On Thu, Jul 21, 2011 at 3:03 PM, Bruce Ide <fl...@gmail.com>wrote:

> Did you record the test previously using the http proxy? I bet your test is
> trying to use the old session ID that probably timed out a couple of days
> ago.
>
> I think you can just slap a HTTP cookie manager config element at the start
> of the test and that should fix it.
>
> --
> Bruce Ide
> FlyingRhenquest@gmail.com
>

Re: Session Time out message

[Bruce Ide <fl...@gmail.com>]

Did you record the test previously using the http proxy? I bet your test is
trying to use the old session ID that probably timed out a couple of days
ago.

I think you can just slap a HTTP cookie manager config element at the start
of the test and that should fix it.

-- 
Bruce Ide
FlyingRhenquest@gmail.com