james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-2309) Long overflow in JMS delays
Date Wed, 11 Jul 2018 10:37:00 GMT

    [ https://issues.apache.org/jira/browse/JAMES-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539874#comment-16539874
] 

ASF GitHub Bot commented on JAMES-2309:
---------------------------------------

Github user nstdio closed the pull request at:

    https://github.com/apache/james-project/pull/125


> Long overflow in JMS delays
> ---------------------------
>
>                 Key: JAMES-2309
>                 URL: https://issues.apache.org/jira/browse/JAMES-2309
>             Project: James Server
>          Issue Type: Bug
>          Components: Queue
>            Reporter: Tellier Benoit
>            Priority: Major
>              Labels: bug
>
> When using a Long.MAX delay value:
>  - TimeUnit delay conversion to ms detect the overflow and fallback to maximum value
>  - But nextDeliverycalculation in *{color:#ffc66d}getJMSProperties{color}* adds  that
value to current time. And that computation DO overflow.
> See DelayedMailQueueTest :: *{color:#ffc66d}enqueueWithVeryLongDelayShouldDelayMail{color}*
> The consequence is that a delayed mail is directly delivered. Correct behaviour would
be to keep preserving Long.MAX value.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message