on the fly database logging

[renek]

Hi

I have a problem with the "on-the-fly" option. When i log the results to database without the on-the-fly option, it runs very well. But with the "on-the-fly" option the sequence hangs in the step "log to database".
Teststand write the STEP_RESULT into the database, but the UUT_RESULT not.

Have anybody an idea?

René

[Scott_Richardson]

René
I am not aware of any hang that we had in the past like this.

Questions:

1. What version of TestStand are you using?
2. What DBMS are you using?
3. How long have you waited (at least 10 minutes), and does the hang eventually timeout?
4. Are you using a default schema or a custom one? If custom please let us know what schema it is most like and describe what you changed?
5. Can you post your database options file from the configuration directory to the forum?
6. Does the hang occur on the first UUT?
7. If you break the execution, what step is it on and what does the call stack look like?
8. Are you running multiple threads in the execution?

[renek]

Hi Scott


    What version of TestStand are you using?
       3.5

    What DBMS are you using?
       Access

    How long have you waited (at least 10 minutes), and does the hang eventually timeout?
       I wait about 5 mins. Then I terminate the program

    Are you using a default schema or a custom one? If custom please let us know what schema it is most like and describe what you changed?
       I use the default schema with one change. I insert in the STEP_RESULT statement under the UUT_RESULT parameter a new one: "Seriennummer"

    Can you post your database options file from the configuration directory to the forum?
       see attachment

    Does the hang occur on the first UUT?
       Yes. There are three numericlimit tests. The result of these test are witten into the database. But the UUT_RESULT table always empty

    If you break the execution, what step is it on and what does the call stack look like?
       Can you help me with this step? I start the test over an OP. I know that TestStand hang in "Database.seq" at step "Log Results to Database"

    Are you running multiple threads in the execution?
       Yes.  The test-sequence runs in a new thread

- the model is not running in a loop
- the main-sequence is running in an endless loop controled by the Operationinterface

René


Message Edited by renek on 04-07-2008 10:03 AM

[renek]

Morning

I verify my problem with a small sequence (DB_Test.seq). On the image you see in the title the error message. I hope this will help you.

René

[Scott_Richardson]

René

You said that the application would previously hang and you used multiple threads so there was no error to look at. In your attached simple case, you attached a non-multithreading sequence and you attached a bitmap that suggested an error occurred. What was the error details, code and message, in the simple case?  Do you believe that this error is the same as the previous hang?

[Scott_Richardson]

René
I just noticed that the expression for the Seriennummer column that you added to the schema was empty in the ini file. I would assume that if you ran this the DBLog would return an error saying "The expression cannot be empty.". I suspect that is the error that you got in your simple test case. Can you verify this?

Can you tell me more about the multi-threading aspects of your hanging testcase. Does the client sequence(MainSequence) use a Sequence Call step to launch the new thread? Does MainSequence wait for the thread to complete before you try to return to Test UUTs in the model, or is the thread still running after you return from MainSequence?

What did you mean by " the model is not running in a loop, the main-sequence is running in an endless loop controled by the Operationinterface"? Looking at the Test UUTs in your model it is running in a loop. Are you logging multiple UUT as a single run, is there a reason why you are not using the loop in Test UUTs?

Message Edited by Scott Richardson on 04-09-2008 10:53 AM