You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/05/15 13:53:00 UTC
[jira] [Commented] (AMQ-7458) Implement bounds checking on the
message scheduling properties
[ https://issues.apache.org/jira/browse/AMQ-7458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108308#comment-17108308 ]
ASF subversion and git services commented on AMQ-7458:
------------------------------------------------------
Commit 41bef942936f3ee389d72e8a4789e074d3b1b27a in activemq's branch refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=41bef94 ]
Merge pull request #521 from coheigea/AMQ-7458
AMQ-7458 - Implement bounds checking on the message scheduling proper…
> 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)