couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <>
Subject [jira] Commented: (COUCHDB-452) couch logs an [error] record if a client disconnects
Date Wed, 05 Aug 2009 12:40:14 GMT


Jan Lehnardt commented on COUCHDB-452:

It will match, but why don't we want to keep the special case. maybe the question boils down
to why did we have them in the first place. Just wondering about the change.

> couch logs an [error] record if a client disconnects
> ----------------------------------------------------
>                 Key: COUCHDB-452
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Mark Hammond
>         Attachments: dont_log_error_on_disconnect.patch
> If a client makes a request which returns multiple rows (eg, a query) but disconnects
before reading the response, couch logs:
> [error] [<0.66.0>] Uncaught error in HTTP request: {exit,normal}
> [info] [<0.66.0>] Stacktrace: [{mochiweb_request,send,2},
>              {couch_httpd,send_chunk,2},
>              {couch_httpd_view,send_json_view_row,5},
>              {couch_httpd_view,'-make_view_fold_fun/6-fun-0-',12},
>              {couch_view,fold_fun,4},
>              {couch_btree,stream_kv_node2,7},
>              {couch_btree,stream_kp_node,7},
>              {couch_btree,fold,5}]
> This could lead someone to conclude couch has an error which is not correct.  A simple
[info] record recording the premature normal exit is probably more appropriate.
> FYI, the easiest way I found to repro this was to execute:
> % python -c "import urllib; urllib.urlopen('').close()"
> which causes Python to open a connection and close it without reading anything.  I'll
attach a patch as suggested generally by jchris.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message