Opened 13 years ago
Closed 12 years ago
#615 closed defect (worksforme)
openssl dies after about a day
| Reported by: | Moritz Heidkamp | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | unknown | Version: | 4.7.x |
| Keywords: | openssl | Cc: | |
| Estimated difficulty: |
Description
Keeping an openssl connection open for about one day leads to the error "SSL socket already closed" being thrown. Since it has no specific condition type it cannot be handled appropriately. The openssl egg should probably not handle this condition specifically anyway but try to write to the closed socket and just let the error raised by the tcp unit propagate.
Change History (7)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
The only way I'm able to reproduce this is if I catch and ignore the handshake timeout exception and then re-use that same ssl port.
I think this may be a bug in your code. Could you post a (possibly simplified) version of it that fails in this way?
comment:3 Changed 13 years ago by
Also, you may be accidentally reading from or writing to an already closed port. Try the patch in #653 to see if that's happening here.
comment:4 Changed 13 years ago by
| Milestone: | 4.8.0 |
|---|
comment:5 Changed 12 years ago by
Is this still an issue with the refactorings Thomas made with 1.6.1?
comment:6 Changed 12 years ago by
It's been working for me. I have a server that has been up for weeks now. I'm using openssl 1.5.1, though.
comment:7 Changed 12 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Unfortunately I'm unable to reproduce this anymore as I don't have the code at hand. Since Mario says it works for him I'm closing this issue for now.
I think the main problem is that it's reinvoking {{startup}} after the socket & tcp connection has been marked closed. It shouldn't do that.