Hello Mark,
Thanks for your reply. We did the initial testing today with extended logs on. Yes you are correct that after replaying for example following request https://xxx.1907.com/xxxapp/checkSession.html" the Apache Web server send HTTP 200 Ok with timestamp. However according to application team there is set time threshold to kill the session after 30 mins which we are experiencing in the test environment.
The We server returns "HTTP 302 Unknown Reason" and redirects the call to Log on Page. Application team says they don't see any error in App Server. But I feel somehow that CheckSession.HTML page either gets deleted or become unavailable due to some secured authentication settings.
As you suggested we planning to introduce log in transaction before 30 mins period;But that will be a workaround. Do you think we can explore any setting in Load Runner like Keep Alive session settings or its related to Web server settings.
I will also try to correlate Time Stamp but application team saying there is no set threshold
Again I really appreciate for your help and suggestions.
Regards,
Sumit