[
https://issues.apache.org/jira/browse/STORM-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514500#comment-14514500
]
ASF GitHub Bot commented on STORM-797:
--------------------------------------
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/537
STORM-797: DisruptorQueueTest has some race conditions in it.
The test had two race conditions in it. The first was that the data
returned by the Consumer was not volatile. The second was that run gave no
time for the consumer to actually receive anything so under heavy load it was
possible for it to not actually complete.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-797
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/537.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #537
----
commit 85db67e659c3a65cbe0209b4fef282b7f5c2a28e
Author: Robert (Bobby) Evans <[email protected]>
Date: 2015-04-27T17:29:26Z
STORM-797: DisruptorQueueTest has some race conditions in it.
----
> Disruptor Queue message order issue
> -----------------------------------
>
> Key: STORM-797
> URL: https://issues.apache.org/jira/browse/STORM-797
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Kishor Patil
> Assignee: Robert Joseph Evans
> Priority: Critical
>
> We notice following ??DisruptorQueueTest.testMessageDisorder?? unit test
> fails intermittently:
> {code}
> java.lang.AssertionError: We expect to receive first published message first,
> but received null expected:<1> but was:<null>
> DisruptorQueueTest.testMessageDisorder:60 We expect to receive first
> published message first, but received null expected:<1> but was:<null>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
