https://issues.apache.org/bugzilla/show_bug.cgi?id=50618
--- Comment #30 from Milamber <[email protected]> 2011-09-14 00:02:12 UTC --- (In reply to comment #27) > Again, > And a little complement to what I said about catching StackOverflowError: > > An Error is a subclass of Throwable that indicates serious problems that a > reasonable application should not try to catch. Most such errors are abnormal > conditions. The ThreadDeath error, though a "normal" condition, is also a > subclass of Error because most applications should not try to catch it. A > method is not required to declare in its throws clause any subclasses of Error > that might be thrown during the execution of the method but not caught, since > these errors are abnormal conditions that should never occur. > > > Regards > Philippe We are in a special case: infinite recursive loop without exit condition when If controller begin to return null (because the condition return false). (Like a branch on a JMeter tree without end - very big branch) It's seems very (very) difficult to solve, a way is to introduce a limit on each call (in recursive method), and test this limit to stop loop. This way is not good for JMeter (introduce a limit for If Controller) With Java, the try catch block is a good way to catch this 'technical' error (the stack is full), and to force JMeter to return on root tree, and start a new turn to fill the stack, etc. A problem still the test case when If Controller always return false (from first loop). JMeter doesn't count iteration, and start a long running without end... -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
