-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Q: Rule as a singleton bean #192
Comments
In If you check at there is a call to In private Map<Long, T> _valueMap = new HashMap<>();
private final ReentrantReadWriteLock _lock = new ReentrantReadWriteLock(); If you have one run per request, on each request you will have a different bean/object for each |
I see the single result that keeps results per thread. Does it mean that we have single lock in result for all the application threads? Is it really optimized for all threads to wait when a single request finishes its work? |
You are right one Result, we have one |
Am I correct that in case rules are defined as spring singleton beans it means that all the application threads will be blocked by the single lock in Result class?
Or I can reformulate the question:
The text was updated successfully, but these errors were encountered: