[
https://issues.apache.org/jira/browse/IGNITE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643043#comment-15643043
]
ASF GitHub Bot commented on IGNITE-4176:
----------------------------------------
GitHub user amirakhmedov opened a pull request:
https://github.com/apache/ignite/pull/1211
IGNITE-4176: IgniteQueue not functioning as expected after remove()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/amirakhmedov/ignite IGNITE-4176
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1211.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 #1211
----
commit cf89f6ea4ae24a770cf1b09ecb7bf582de2c113d
Author: Amir Akhmedov <[email protected]>
Date: 2016-11-07T04:07:19Z
IGNITE-4176: IgniteQueue not functioning as expected after remove()
----
> IgniteQueue not functioning as expected after remove().
> -------------------------------------------------------
>
> Key: IGNITE-4176
> URL: https://issues.apache.org/jira/browse/IGNITE-4176
> Project: Ignite
> Issue Type: Bug
> Components: data structures
> Affects Versions: 1.7
> Reporter: C Saternos
> Assignee: Amir Akhmedov
> Fix For: 1.8
>
> Attachments: WhereDidItGo.java, pom.xml
>
>
> After removing an item from an IgniteQueue, the next item on the queue can be
> viewed using peek(). However, poll() or take() does not retrieve the item.
> When iterating through the remaining items in the queue, it appears that 1/2
> of them are missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
