[
https://issues.apache.org/jira/browse/QPID-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7720:
-----------------------------
Component/s: (was: Java Common)
JMS AMQP 0-x
> Java client hangs when publishing to C++ broker queue with flow control
> activated
> ---------------------------------------------------------------------------------
>
> Key: QPID-7720
> URL: https://issues.apache.org/jira/browse/QPID-7720
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 0-x
> Affects Versions: qpid-java-6.1.1
> Reporter: Flavio Baronti
> Priority: Major
> Attachments: QPID-7720.patch
>
>
> This is probably the same as QPID-4073.
> When a C++ flow controlled queue is overfull, the broker stops sending
> acknowledgements to client commands. This causes the internal command queue
> of the client to become full.
> In this situation, the client sends a flush request, then waits for the
> internal queue to free some space. Unfortunately, the broker will answer to
> the flush request with an empty response, and will not send anything else
> when the queue becomes underfull again. Thus the client dies with a timeout.
> I suggest a patch which sends again the flush command every 500ms, up to the
> configured timeout. If the queue becomes underfull within the timeout, the
> broker will answer with a non-empty response, and the client will restart
> processing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
