[
https://issues.apache.org/jira/browse/PROTON-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyG updated PROTON-2573:
--------------------------
Description:
I'm using the python wrapper and have seen this behaviour a number of times but
don't know what precipitates it.
Symptoms are 100% cpu usage and a tcp connection status to 2 (send and receive)
C qpid brokers in "close_wait" (the broker has timed out the connection due to
a lack of heartbeat from the client)
It had, on startup, successfully connected to the broker but sometime later
lost the connection. Scheduled tasks (_timers in _reactor.py) are not running
(presumably starved by a tight loop in the process code)
On turning on debug logging it repeats (endlessly)
*[DEBUG] <proton._reactor.Container object at 0x7fc91cf93310> Yielding*
(presumably from line 251 of _reactor.py)
was:
I'm using the python wrapper and have seen this behaviour a number of times but
don't know what precipitates it.
Symptoms are 100% cpu usage and a tcp connection status to 2 (send and receive)
C qpid brokers in "close_wait".
It had, on startup, successfully connected to the broker but sometime later
lost the connection. Scheduled tasks (_timers in _reactor.py) are not running
(presumably starved by a tight loop in the process code)
On turning on debug logging it repeats (endlessly)
*[DEBUG] <proton._reactor.Container object at 0x7fc91cf93310> Yielding*
(presumably from line 251 of _reactor.py)
> Proton in endless yielding loop
> -------------------------------
>
> Key: PROTON-2573
> URL: https://issues.apache.org/jira/browse/PROTON-2573
> Project: Qpid Proton
> Issue Type: Bug
> Affects Versions: proton-c-0.37.0
> Environment: centos 7
> Reporter: AndyG
> Priority: Major
>
> I'm using the python wrapper and have seen this behaviour a number of times
> but don't know what precipitates it.
> Symptoms are 100% cpu usage and a tcp connection status to 2 (send and
> receive) C qpid brokers in "close_wait" (the broker has timed out the
> connection due to a lack of heartbeat from the client)
> It had, on startup, successfully connected to the broker but sometime later
> lost the connection. Scheduled tasks (_timers in _reactor.py) are not running
> (presumably starved by a tight loop in the process code)
> On turning on debug logging it repeats (endlessly)
> *[DEBUG] <proton._reactor.Container object at 0x7fc91cf93310> Yielding*
> (presumably from line 251 of _reactor.py)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
