[ 
https://issues.apache.org/jira/browse/QPID-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated QPID-7424:
-----------------------------
    Description: 
If a consuming python client application written against the old legacy 
0-8..0-91 API suffers a disconnect from the Broker, the application (calling 
queue.get()) is unaware and will continue to wait indefinitely.

The disconnect may be caused by either management intervention,  a broken 
socket or the enablement of heart-beating Broker-side.  On the latter point, 
The legacy client does not support heat beating so the Broker will always close 
the connection as soon as the line goes quiet.



  was:
If a consuming python client application written against the old legacy 
0-8..0-91 API suffers a disconnect from the Broker, the application (calling 
queue.get()) is unaware and will continue to wait indefinitely.

The disconnect may be caused by either management intervention,  a broken 
socket or the configuration of heart-beating.




> [0-8..0-91] Consuming python client application is not notified of remotely 
> closed connection
> ---------------------------------------------------------------------------------------------
>
>                 Key: QPID-7424
>                 URL: https://issues.apache.org/jira/browse/QPID-7424
>             Project: Qpid
>          Issue Type: Bug
>          Components: Python Client
>            Reporter: Keith Wall
>
> If a consuming python client application written against the old legacy 
> 0-8..0-91 API suffers a disconnect from the Broker, the application (calling 
> queue.get()) is unaware and will continue to wait indefinitely.
> The disconnect may be caused by either management intervention,  a broken 
> socket or the enablement of heart-beating Broker-side.  On the latter point, 
> The legacy client does not support heat beating so the Broker will always 
> close the connection as soon as the line goes quiet.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to