[
https://issues.apache.org/jira/browse/QPID-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2319:
------------------------------
Assignee: Ted Ross
> qpid-route hangs when connecting to the Java Broker
> ---------------------------------------------------
>
> Key: QPID-2319
> URL: https://issues.apache.org/jira/browse/QPID-2319
> Project: Qpid
> Issue Type: Bug
> Components: python tools
> Reporter: Rob Godfrey
> Assignee: Ted Ross
>
> When working on the QMF implementation in the Java Broker I found that the
> Python tools which use the qmf.console python API hung in the _waitForStable
> function of the Broker class
> Investigating showed that although the count of outstandingRequests did drop
> to zero (the condition the function is waiting for) it was not being alerted
> to this fact.
> Adding debugging information into the code I could see that on entering
> _waitForStable the count of outstanding requests was 1...
> After entering the wait() the count droppped to zero through a call to
> _decOustanding ... then increased again all the way up to through calls to
> incOutstanding 26... then again dropped all the way to 0.
> Looking at the code for _decOutstanding it's clear that the wait should be
> notified that the count has dropped to zero, as long as the syncInFlight
> variable is true.
> If this check is commented out (i.e. decOustanding calls notify even if
> syncInFlight is false) then the tools do not hang
> the conclusion would seem to be that something is setting syncInFlight to
> false causing the _waitForStable function to not receive notifications that
> it can stop waiting...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
