13 Commits

Author SHA1 Message Date
Narendra Pathai
922fd62da6 Resolves #643, test cases failed due to global state in CallsCount (#803)
* Resolves #643, test cases failed due to presence of global state in CallsCount. Because AppTest was executed before B2BServiceTest, it scheduled 1 sec timer using ThrottleTimerImpl class. While resetting it used that global CallCount class reset() method, which reset all counters. So that causes thread safety issue because of unintended sharing of application state between test cases, which is not a good practice.

* Updated class diagram png and added UCLS file
2018-10-21 21:14:07 +03:00
Ilkka Seppälä
95df47e418 Disable intermittently failing test 2018-06-03 14:15:00 +03:00
Christian Cygnus
f3e1cd3a1d Fix checkstyle 2018-05-25 22:47:23 -05:00
Christian Cygnus
4ab46c7fcb #643 Fix flaky tests for throttling pattern 2018-05-25 22:26:35 -05:00
Ilkka Seppälä
17ea0b17f6 Disable flaky tests mentioned in issue #643 and #699 2018-03-31 10:16:56 +03:00
baislsl
991ba320a6 Improve Javadoc 2018-02-19 22:01:14 +08:00
Artur Mogozov
6694d742a3 Migrate to JUnit5 2017-12-31 16:29:48 +09:00
Deepanshu Rastogi
4e236f6da8 Minor modification of Long to long 2017-09-28 15:04:32 +02:00
Deepanshu Rastogi
01b85b9721 Used AtomicLong for concurrenthashmap operations 2017-09-25 12:59:39 +02:00
Dos Debug
d8ac00536c Fixes Checkstyle problems
There are few checkstyles problems found in the  which are required to be fixed
2017-09-21 15:13:57 +05:00
Deepanshu Rastogi
50d7dbe4de Seperated timer class and created Callscount class 2017-09-08 16:15:31 +02:00
Deepanshu Rastogi
5f9100cd03 Adding class diag and updating readme 2017-09-07 15:27:18 +02:00
Deepanshu Rastogi
05629f687b Adding throttling pattern 2017-09-07 12:54:19 +02:00