GitHub user SreeramGarlapati opened a pull request:
https://github.com/apache/qpid-proton/pull/73
proton-j: SSL decode buffer implementation doesn't flush all bytes to the
next transport buffer (_underlyingInput)
Actual Issue/scenario hit by Microsoft Azure EventHubs:
We have a pattern where customers sends messages in a burst to our Queue
and stop sending and then wait for all of them to be received. Because of this
issue - many messages were stuck in the SSL Decode Buffer and were only picked
up when new messages arrive.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SreeramGarlapati/qpid-proton sg.recvstuck
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-proton/pull/73.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 #73
----
commit 2ceb434e1720917e788f55f8439095cb1be0fb78
Author: Sreeram Garlapati <sreer...@microsoft.com>
Date: 2016-04-05T04:34:01Z
JavaClient: Fix stuck issue on Receiver
Underlying Proton-J Issue: Messages were stuck in the SSL Decode Buffer and
were only picked up when new messages arrive.
----
---
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.
---
