jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <p.moua...@ubik-ingenierie.com>
Subject Issue in IfController behaviour
Date Sat, 11 Oct 2014 21:48:38 GMT
Hello,
I think there is currently a big issue in the way IfController works.
The issue is located in GenericController#reInitializeSubController (only
called by IfController).

This method was introduced to fix :

   - https://issues.apache.org/bugzilla/show_bug.cgi?id=50032

The Algorithm currently iterates of test elements following  the next()
(used by regular sampling ) to get Controllers and reset them.

The algorithm has many issues:

   - Stackoverflow whenever first child of IfController is a LoopControler,
   a While Controller, even SimpleController provided it contains somewhere a
   WhileController or LoopControler....
   - It triggers notifications of Listener (which was workaround by
   introducing ThreadContext#isReinitializingSubControllers) breaking
   TransactionController
   - It also hold a performance issue as we in fact need to iterated on
   children of Controller to find Controllers and call
   reInitializeSubController() on it


Related bugs are the following:

   - https://issues.apache.org/bugzilla/show_bug.cgi?id=50032
   - https://issues.apache.org/bugzilla/show_bug.cgi?id=56160
   - https://issues.apache.org/bugzilla/show_bug.cgi?id=52496
   - https://issues.apache.org/bugzilla/show_bug.cgi?id=53768



-- 
Regards.
Philippe M.
@phimdot

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message