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 GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/27 12:16:00 UTC
[jira] [Work logged] (AMQ-7458) Implement bounds checking on the
message scheduling properties
[ https://issues.apache.org/jira/browse/AMQ-7458?focusedWorklogId=411025&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411025 ]
ASF GitHub Bot logged work on AMQ-7458:
---------------------------------------
Author: ASF GitHub Bot
Created on: 27/Mar/20 12:15
Start Date: 27/Mar/20 12:15
Worklog Time Spent: 10m
Work Description: coheigea commented on pull request #521: AMQ-7458 - Implement bounds checking on the message scheduling proper…
URL: https://github.com/apache/activemq/pull/521
…ties
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 is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 411025)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> 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)