couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1340) Replication: Invalid JSON reported
Date Wed, 16 Nov 2011 13:37:51 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151189#comment-13151189
] 

Filipe Manana commented on COUCHDB-1340:
----------------------------------------

Alex good observation.
The last 1 is a chunk which contains only a \n character. This is intentionally added by couch
for all json responses:

https://github.com/apache/couchdb/blob/1.1.x/src/couchdb/couch_httpd.erl#L654

I'm unsure this would be the cause for your problem (chunks are separated by \r\n). If you're
able to build from source, you can try commenting the line which sends the chunk containing
only the \n. This change would be on the source database server.
                
> Replication: Invalid JSON reported
> ----------------------------------
>
>                 Key: COUCHDB-1340
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1340
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 1.1.1
>         Environment: CentOS 5.6 x86_64, Couchdb 1.1.1 (Patched for COUCHDB-1333), spidermonkey
1.8.5, curl 7.21, erlang 14b03
>            Reporter: Alex Markham
>              Labels: invalid, json
>         Attachments: 9c94ed0e23508f4ec3d18f8949c06a5b replicaton from wireshark cut.txt,
replication error wireshark.txt, source couch error.log, target couch error.log
>
>
> It seems our replication has stopped, reporting an error
> [emulator] Error in process <0.21599.306> {{nocatch,{invalid_json,<<0 bytes>>}},[{couch_util,json_decode,1},{couch_rep_reader,'-open_doc_revs/3-lc$^1/1-1-',1},{couch_rep_reader,'-open_doc_revs/3-lc$^1/1-1-',1},{couch_rep_reader,open_doc_revs,3},{couch_rep_reader,'-spawn_document_request/4-fun-0-'...

> It was all working until we upgraded some other couches in our replication "web" from
couch 1.0.3 to couch 1.1.1. We then set of database and view compactions, and sometime overnight
some of the replication links stopped.
> I have curled the command myself, both as a multipart message and a single json response
(with header "Accept:application/json" ) and it can be parsed correctly by Python simplejson
- I have attached it here aswell - called "troublecurl-redacted.txt" - though it is 18.8mb.
The request takes about 6 seconds.
> I don't quite understand why it is reported as invalid JSON? Other reports similar to
this that I googled mentioned blank document ids, but I can't see any of these.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message