GitHub user peterjoel opened a pull request:
https://github.com/apache/flex-blazeds/pull/2
Fixed bug with flushing messages to polling client.
When flushing the message queue on a poll, messageClient is null. (See
[JavaDoc](https://github.com/apache/flex-blazeds/blob/master/modules/core/src/flex/messaging/client/FlexClientOutboundQueueProcessor.java#L159)).
This should mean that all messages for the flexClient are flushed. Instead,
only the messages that have the same messageClient as the first message in the
queue are flushed. That means a polling client has to poll multiple times to
get all messages.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/peterjoel/flex-blazeds
flush_all_message_clients
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flex-blazeds/pull/2.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 #2
----
commit 1314af31681ddf822b61c47a4fd12d1e9b6caa51
Author: Peter Hall <peter.h...@algomi.com>
Date: 2016-02-25T10:01:47Z
Fixed bug with flushing messages to polling client.
When flushing the message queue on a poll, messageClient is null. This
should mean that all messages for
the flexClient are flushed. Instead, only the messages that have the same
messageClient as the first
message in the queue are flushed. That means a polling client has to poll
multiple times to get all
messages.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
