[
https://issues.apache.org/jira/browse/GEODE-8498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202149#comment-17202149
]
ASF GitHub Bot commented on GEODE-8498:
---------------------------------------
sabbeyPivotal closed pull request #5533:
URL: https://github.com/apache/geode/pull/5533
----------------------------------------------------------------
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:
us...@infra.apache.org
> Redis messages written to Netty channel sometimes delivered out of order
> ------------------------------------------------------------------------
>
> Key: GEODE-8498
> URL: https://issues.apache.org/jira/browse/GEODE-8498
> Project: Geode
> Issue Type: Bug
> Components: redis
> Reporter: Sarah Abbey
> Assignee: Sarah Abbey
> Priority: Minor
> Labels: pull-request-available
>
> {code:java}
> [err]: Mix SUBSCRIBE and PSUBSCRIBE in tests/unit/pubsub.tcl
> Expected 'pmessage foo.* foo.bar hello' to be equal to 'message foo.bar hello'
> *** [err]: Mix SUBSCRIBE and PSUBSCRIBE in tests/unit/pubsub.tcl
> Expected 'pmessage foo.* foo.bar hello' to be equal to 'message foo.bar hello'
> {code}
> When writing responses to a Netty channel, the messages may get written out
> of order in the `writeAndFlush` call. To verify this bug, we used a single
> thread to call `writeAndFlush` and added logging right before calling
> `writeAndFlush` and after `afterWrite` in the callback listener. We saw the
> messages get logged in the proper order before `writeAndFlush` was called,
> but the messages were logged out of order in the callback listener and
> arrived in the wrong order on the client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
