couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damien Katz (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (COUCHDB-45) Error when concurrently hitting HTTP. Seems that it doesn't honor Connection: Close
Date Mon, 15 Dec 2008 22:49:44 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Damien Katz resolved COUCHDB-45.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.9
         Assignee: Damien Katz

This might have been fixed by an earlier fix to mochiweb library dealing with closing http
connections. I'm going to assume this was fixed too as well, but please reopen if the symptoms
remain.

> Error when concurrently hitting HTTP. Seems that it doesn't honor Connection: Close
> -----------------------------------------------------------------------------------
>
>                 Key: COUCHDB-45
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-45
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>         Environment: linux
>            Reporter: Jeff Davey
>            Assignee: Damien Katz
>             Fix For: 0.9
>
>
> While doing some load testing against couch, i've noticed that it throws errors when
sending concurrently with more than 40 threads.
> I'm guessing that it's trying to send something back to the client after the socket has
already been closed. I'm using Connection: Close in the headers on the http client. 
> {mochiweb_socket_server,221,
>                         {child_error,{{case_clause,{error,enotconn}},
>                                       [{mochiweb_request,get,2},
>                                        {couch_httpd,handle_request,2},
>                                        {mochiweb_http,headers,4},
>                                        {proc_lib,init_p,5}]}}}
> [error] [<0.4889.0>] {error_report,
>     <0.22.0>,
>     {<0.4889.0>,
>      crash_report,
>      [[{pid,<0.4889.0>},
>        {registered_name,[]},
>        {error_info,
>            {{case_clause,{error,enotconn}},
>             [{mochiweb_request,get,2},
>              {couch_httpd,handle_request,2},
>              {mochiweb_http,headers,4},
>              {proc_lib,init_p,5}]}},
>        {initial_call,
>            {mochiweb_socket_server,
>                acceptor_loop,
>                [{<0.53.0>,#Port<0.125>,#Fun<mochiweb_http.1.62821608>}]}},
>        {ancestors,[couch_httpd,couch_server_sup,<0.1.0>]},
>        {messages,[]},
>        {links,[<0.53.0>,#Port<0.3453>]},
>        {dictionary,
>            [{mochiweb_request_body,
>                 <<"{ \"sender\" : \"bob\", \"recipient\" : \"test1\", \"flagNew\"
: true }">>}]},
>        {trap_exit,false},
>        {status,running},
>        {heap_size,6765},
>        {stack_size,21},
>        {reductions,5351}],
>       []]}}
> [error] [<0.53.0>] {error_report,
>     <0.22.0>,
>     {<0.53.0>,
>      std_error,
>      {mochiweb_socket_server,
>          221,
>          {child_error,
>              {{case_clause,{error,enotconn}},
>               [{mochiweb_request,get,2},
>                {couch_httpd,handle_request,2},
>                {mochiweb_http,headers,4},
>                {proc_lib,init_p,5}]}}}}}

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


Mime
View raw message