[
https://issues.apache.org/jira/browse/DEFT-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065751#comment-13065751
]
Roger Schildmeijer edited comment on DEFT-156 at 7/15/11 7:53 AM:
------------------------------------------------------------------
Feel free to propose a better solution (There are a couple of things I dont
like with my (my patch) approach...(eg. the two execute..() methods. The
private DecoratedTimeout class and its compareTo impl.. ))
was (Author: rschildmeijer):
Feel free to propose a better solution (There are a couple of things I dont
like with this approach...(eg. the two execute..() methods. The private
DecoratedTimeout class and its compareTo impl.. ))
> Non deterministic behaviour when multiple timeouts have exact same deadline
> ---------------------------------------------------------------------------
>
> Key: DEFT-156
> URL: https://issues.apache.org/jira/browse/DEFT-156
> Project: Deft
> Issue Type: Bug
> Reporter: Roger Schildmeijer
> Attachments: DEFT-156.patch,
> Unit+test+for+multiple+timeouts+with+same+deadline.patch
>
>
> If 2,...n timeout has exact same (timeout) deadline weird things starts to
> happen. (e.g wrong timeouts might get removed from the collection of
> timeouts). See attached unit test that currently fails on trunk.
> My qualified guess is that the problem is because of
> DecoratedTimeout.compareTo (DecoratedTimeout is a private in JMXDTM).
> I think the current design is bad so feel free to propose/implement a better
> solution.
> (Found while doing DEFT-151 (Distributed demo application (elastica)))
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
