You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <qp...@incubator.apache.org> on 2008/10/24 00:58:44 UTC
[jira] Created: (QPID-1395) Explicit close not safe after
connection Closed exception
Explicit close not safe after connection Closed exception
---------------------------------------------------------
Key: QPID-1395
URL: https://issues.apache.org/jira/browse/QPID-1395
Project: Qpid
Issue Type: Bug
Components: Python Client
Affects Versions: M3
Environment: [jross@localhost ~]$ python -V
Python 2.5.1
[jross@localhost ~]$ uname -a
Linux localhost.localdomain 2.6.25.14-69.fc8 #1 SMP Mon Aug 4 14:20:24 EDT 2008 i686 i686 i386 GNU/Linux
[jross@localhost ~]$ cat /etc/redhat-release
Fedora release 8 (Werewolf)
Reporter: Justin Ross
It's natural to write client code with:
conn = Connection(sock)
try:
try:
// session stuff
catch Closed:
// handle it
finally:
conn.close()
ATM, his is not safe, because close blocks and can't be interrupted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.