While testing for 72 hours the conductor is giving some errors as given in the attachment herewith and closes.But the test is still continues.The conductor ,no longer is in control of the test.Theplayer log shows the test running.But no useful info can be derived with that.Can anyone give some know what may be the reason and the solution to this problem?
I have had similar problems, it has typically been associated with having set up a pointer to say a DO_Http request and trying to reference the pointer when an unexpected condition has occurred. The script carries on processing and you then reference the pointer and its pointing to a reserved area of memory causing the conductor to feak out.
I have found that this is typical if you have the abort of error flag in the conductor turned off.
One other thing is that you may want to execute the test where the application is hosted on a different machine, you can't tell if its the application causing the problem or QALoad.
You may also wish to turn on some counters in perfmon and find out what is happening on the PC, check for memory leaks and processor as the increase in response time doesn't look good.