Edgewall Software

Changes between Initial Version and Version 1 of Ticket #2688


Ignore:
Timestamp:
Jan 30, 2006, 12:44:29 PM (14 years ago)
Author:
Christian Boos
Comment:

When you say tracd "crash", you actually means it only produces the above error in the log, or do you really mean that the server process dies (segfaults?)

If it's only about the errors, it's not that problematic. This error is caused by the clients (i.e. browsers) interrupting their requests, either because the user presses the Stop button, or … hits Reload in rapid succession!

We should however filter out such errors… We already do it for error code 32 (EPIPE on Unix), 10053 (WSAECONNABORTED on Windows), so we should do it for 10054 (WSAECONNRESET on Windows) as well.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2688

    • Property Owner changed from Jonas Borgström to Christian Boos
    • Property Status newassigned
    • Property Milestone0.9.4
  • Ticket #2688 – Description

    initial v1  
    33Some of these crashes can be reproduced by for instance pressing the reload button in the website a couple of times (try to make it reload the page while the last reload was not finished yet).
    44
     5{{{
    56----------------------------------------
    67Exception happened during processing of request from ('myip', 3104)
     
    7980error: (10054, 'Connection reset by peer')
    8081----------------------------------------
     82}}}
    8183
    8284Sometimes it is an error like the following:
    83 
     85{{{
    8486----------------------------------------
    8587Exception happened during processing of request from ('otherip', 4003)
     
    99101error: (10054, 'Connection reset by peer')
    100102----------------------------------------
     103}}}
    101104
    102105We upgraded to 0.9.3 recently but still have this problem (we started at 0.8.4 and had the same problem then, and in all versions in between).