Hi Sewmini, AFAIK, throttling count will start when the API is invoked. Therefore it should be a successful invocation. First it checks API level throttling limit and then Application level throttling limit and then it goes to resource level throttling check.
Regards, Ushani On Wed, Apr 29, 2015 at 1:59 PM, Sewmini Jayaweera <sewm...@wso2.com> wrote: > Hi, > > In API manager throttling functionality, How exactly the throttling tier > exceed? > > 1. At the end of 20 successful invocations/hits or > 2. When total number of hits (successful and faulty) exceeds 20? > > When I test this in both API manager 1.8.0 and 1.9.0 packs, count was > taken using number of successful hits. Therefore I reported [1] > documentation Jira. > > Please do verify and let me know if the functionality is wrong. > > [1]. https://wso2.org/jira/browse/DOCUMENTATION-1665 > <https://wso2.org/jira/browse/DOCUMENTATION-1665> > > Thanks & Regards, > Sewmini > > Sewmini Jayaweera > *Software Engineer - QA Team* > Mobile: +94 (0) 773 381 250 > sewm...@wso2.com > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev