Tips updated
regularly
- If you get an error while running an experiment which says
"Experiment aborted due to errors in transaction ***** class".
Then there is possibly an error in your transaction file, which you should
edit and recompile. However, to test your new class files, you must quit the
current session of TPPT and restart a new one, as the loading of user source
files is not run-time.
- TPPT requires user transaction classes return certain values so it can
determine the execution status of each transaction, namely, -5 is returned
when an sql Deadlock exception occurred, 0 is returned when transaction ran
to completion, -2 is returned when transaction got a logic failure, -1 is
returned when a java or sql exception (non-deadlock) occurred. Make sure
your transactions return these values accordingly. See more about how
to write user-defined procedure files.
Back
to Help Contents