AbstractUserDetailsReactiveAuthenticationManager uses boundidElastic()
Some JVMs have blocking operations when accessing SecureRandom and thus this needs to be performed in a pool that is larger than the number of CPUs Closes gh-7522
This commit is contained in:
parent
06a02ed4bb
commit
0f13c5e44d
|
@ -55,7 +55,7 @@ public abstract class AbstractUserDetailsReactiveAuthenticationManager implement
|
|||
|
||||
private ReactiveUserDetailsPasswordService userDetailsPasswordService;
|
||||
|
||||
private Scheduler scheduler = Schedulers.newParallel("password-encoder", Schedulers.DEFAULT_POOL_SIZE, true);
|
||||
private Scheduler scheduler = Schedulers.boundedElastic();
|
||||
|
||||
private UserDetailsChecker preAuthenticationChecks = user -> {
|
||||
if (!user.isAccountNonLocked()) {
|
||||
|
|
Loading…
Reference in New Issue