-
Notifications
You must be signed in to change notification settings - Fork 38.4k
Potential integer overflow in ExecutorConfigurationSupport.setAwaitTerminationSeconds(int) and AbstractResourceBasedMessageSource.setCacheSeconds(int) #25613
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
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Milestone
Comments
Thanks for spotting this! It may be rare to specify such a large value there but it still needs to work correctly. This also applies to |
jhoeller
added a commit
that referenced
this issue
Aug 27, 2020
jhoeller
added a commit
that referenced
this issue
Aug 27, 2020
jhoeller
added a commit
that referenced
this issue
Aug 27, 2020
engimatic
pushed a commit
to engimatic/spring-framework
that referenced
this issue
Sep 29, 2020
zx20110729
pushed a commit
to zx20110729/spring-framework
that referenced
this issue
Feb 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Affects: 5.2.8.RELEASE
There is a small bug in the class
org.springframework.scheduling.concurrent.ExecutorConfigurationSupport
in the method :
When the input parameter
awaitTerminationSeconds
is bigger thenInteger.MAX_VALUE/1000
the value asigned to
long this.awaitTerminationMillis
can even be negative !I recommend changing the
1000
to the1000l
long version as belowThe text was updated successfully, but these errors were encountered: