[
https://issues.apache.org/jira/browse/AMQ-7458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108306#comment-17108306
]
ASF subversion and git services commented on AMQ-7458:
------------------------------------------------------
Commit 24aaa4698c23f69c6bea1c983c89267261bfcc29 in activemq's branch
refs/heads/master from Colm O hEigeartaigh
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=24aaa46 ]
AMQ-7458 - Implement bounds checking on the message scheduling properties
> Implement bounds checking on the message scheduling properties
> --------------------------------------------------------------
>
> Key: AMQ-7458
> URL: https://issues.apache.org/jira/browse/AMQ-7458
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Job Scheduler
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Priority: Major
> Fix For: 5.16.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This task is to implement bounds checking on the message scheduling
> properties. The values for delay, period + repeat should be rejected if they
> are < 0. Also, a maximum value should be set (and configurable) for the max
> repeat value, as it has the potential to cause a denial of service issue if
> many messages are sent with a repeat value of Integer.MAX_VALUE. In the
> accompanying PR, I've set the default max value to 1000.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
