This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2008年12月18日 00:32 by forest, last changed 2022年04月11日 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| pollwritefail.py | forest, 2008年12月18日 00:31 | example code | ||
| Messages (2) | |||
|---|---|---|---|
| msg78003 - (view) | Author: Forest (forest) | Date: 2008年12月18日 00:31 | |
With use_poll=True on linux, asyncore calls handle_write() after the
socket has been closed.
More specifically, it looks like asyncore dispatches handle_read() and
handle_close() events between the writable() test and the corresponding
handle_write() call. If handle_close() calls close(), as asyncore's
default implementation does, the subsequent handle_write() will fail and
generate an EBADF (bad file descriptor) exception. If handle_error()
also calls close(), as asyncore's default implementation does, this will
mean close() gets called twice on the same socket.
I am attaching example code which demonstrates the problem on Linux
2.6.24 using python 2.5.2, 2.5.3rc1, and 2.6. In one window, run
pollwritefail.py. In another window, establish a TCP connection to port
12345 and immediately close it without reading or writing. This can be
done from within the python interactive interpreter like this:
import socket
s=socket.socket( socket.AF_INET, socket.SOCK_STREAM); s.connect(
('localhost', 12345)); s.close()
The output from pollwritefail.py will look like this:
writable() - asyncore asked if we have data to write
handle_read() - asyncore asked us to read
handle_close() - asyncore said the remote host closed connection
close() - we are closing our end of the connection
handle_write() - asyncore asked us to write
handle_error() - asyncore exception: (9, 'Bad file descriptor')
close() - we are closing our end of the connection
IMHO, two things need fixing here:
1. When writable() returns True, the next handler asyncore calls should
be handle_write(). Calling other handlers in between risks invalidating
the writable() return value.
2. After close(), asyncore should not call handle_write(), even if
writable() would return true.
|
|||
| msg112780 - (view) | Author: Giampaolo Rodola' (giampaolo.rodola) * (Python committer) | Date: 2010年08月04日 09:58 | |
This problem must have been solved at some point because this is what I get now on Linux by using python 2.7: writable() - asyncore asked if we have data to write handle_read() - asyncore asked us to read handle_close() - asyncore said the remote host closed connection close() - we are closing our end of the connection handle_close() - asyncore said the remote host closed connection close() - we are closing our end of the connection Closing out as outdated. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:56:42 | admin | set | github: 48940 |
| 2010年08月04日 09:58:34 | giampaolo.rodola | set | status: open -> closed resolution: out of date messages: + msg112780 versions: + Python 2.6 |
| 2010年07月09日 20:33:01 | giampaolo.rodola | set | assignee: giampaolo.rodola |
| 2010年07月09日 17:29:09 | BreamoreBoy | set | stage: needs patch versions: + Python 3.1, Python 2.7, Python 3.2, - Python 2.6 |
| 2009年03月24日 17:22:19 | intgr | set | nosy:
+ intgr |
| 2008年12月20日 14:36:03 | loewis | set | versions: - Python 2.5, Python 2.5.3 |
| 2008年12月18日 14:31:54 | giampaolo.rodola | set | nosy: + giampaolo.rodola, josiah.carlson |
| 2008年12月18日 00:32:01 | forest | create | |