You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Ijonas Kisselbach (JIRA)" <ji...@apache.org> on 2008/09/17 23:19:44 UTC
[jira] Created: (COUCHDB-122) PUTting standalone attachments >1Mb
cause connection reset
PUTting standalone attachments >1Mb cause connection reset
----------------------------------------------------------
Key: COUCHDB-122
URL: https://issues.apache.org/jira/browse/COUCHDB-122
Project: CouchDB
Issue Type: Bug
Components: HTTP Interface
Affects Versions: 0.9
Environment: Ubuntu 8.04 x86 32-bit
Reporter: Ijonas Kisselbach
Attempting to upload attachments to documents, whereby an attachment >1Mb causes the CouchDB server to reset the socket connection, and not response with a "sensible" error message.
Modifying MAX_RECV_BODY in src/mochiweb/mochweb_request.erl (line 46) to something bigger, say 128Mb, causes the problem to disappear for reasonably large files such as mp3 files. Obviously, the problem of no "sensible" error message still remains, and the socket connection will simply be reset should the upload exceed 128Mb.
(any attachments <1mb work fine and are stored properly)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (COUCHDB-122) PUTting standalone attachments >1Mb cause connection reset
Posted by Paul Davis <pa...@gmail.com>.
There's a document size conifig option in trunk, is this meant to
address this issue and we missed the mochiweb threshold, or am I
missing something on why there are two thresholds?
On Wed, Sep 17, 2008 at 5:19 PM, Ijonas Kisselbach (JIRA)
<ji...@apache.org> wrote:
> PUTting standalone attachments >1Mb cause connection reset
> ----------------------------------------------------------
>
> Key: COUCHDB-122
> URL: https://issues.apache.org/jira/browse/COUCHDB-122
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 0.9
> Environment: Ubuntu 8.04 x86 32-bit
> Reporter: Ijonas Kisselbach
>
>
> Attempting to upload attachments to documents, whereby an attachment >1Mb causes the CouchDB server to reset the socket connection, and not response with a "sensible" error message.
>
> Modifying MAX_RECV_BODY in src/mochiweb/mochweb_request.erl (line 46) to something bigger, say 128Mb, causes the problem to disappear for reasonably large files such as mp3 files. Obviously, the problem of no "sensible" error message still remains, and the socket connection will simply be reset should the upload exceed 128Mb.
>
> (any attachments <1mb work fine and are stored properly)
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Closed: (COUCHDB-122) PUTting standalone attachments >1Mb
cause connection reset
Posted by "Jan Lehnardt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Lehnardt closed COUCHDB-122.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.9
Fixed as of r698260
> PUTting standalone attachments >1Mb cause connection reset
> ----------------------------------------------------------
>
> Key: COUCHDB-122
> URL: https://issues.apache.org/jira/browse/COUCHDB-122
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 0.9
> Environment: Ubuntu 8.04 x86 32-bit
> Reporter: Ijonas Kisselbach
> Fix For: 0.9
>
>
> Attempting to upload attachments to documents, whereby an attachment >1Mb causes the CouchDB server to reset the socket connection, and not response with a "sensible" error message.
> Modifying MAX_RECV_BODY in src/mochiweb/mochweb_request.erl (line 46) to something bigger, say 128Mb, causes the problem to disappear for reasonably large files such as mp3 files. Obviously, the problem of no "sensible" error message still remains, and the socket connection will simply be reset should the upload exceed 128Mb.
> (any attachments <1mb work fine and are stored properly)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.