On Thu, 22 Apr 2004, Vitali Kravitzki wrote:
> During my work with Web-Polygraph through proxy I've met a problem
> that Client abords sessions after 300-800 mins while phase defined
> to run 100 hours.
We had Polygraph tests ran for more than a month so I believe that
100-hour phase duration itself should not be a problem.
There may be many reasons why your test does not run as long as you
want it to. For example, depending on proxy performance, it is
possible that robot waiting queues get longer with every hour,
eventually leading to memory starvation. Such memory consumption
growth should be visible in "phase progress stats" that polyclt prints
every 5 minutes (with verbosity level of 7 or higher).
Does Polygraph or OS say anything when polyclt aborts? Check polyclt
console output and OS message/event logs (e.g. /var/log/messages).
Please use "--verb_lvl 10" and e-mail me complete client- (and, if
possible, server-side console logs) and we will go from there.
Thank you,
Alex.
-- Protocol performance, functionality, and reliability testing. Tools, services, and know-how. http://www.measurement-factory.com/
This archive was generated by hypermail 2b29 : Mon Feb 06 2006 - 12:00:27 MST