[
https://issues.apache.org/jira/browse/COUCHDB-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863748#action_12863748
]
Eddie Corns commented on COUCHDB-579:
-------------------------------------
I had this same problem and google led me here so I'll comment here in case
anyone else ends up here.
What I had was some code like:
function (doc,req) { if (doc.status && job.status == 'queued') ...
Out of context like that it is obvious that I had job.status instead of
doc.status. It turned out that this was the culprit. Presumably some sort of
JS runtime error since there was no job var.
HTH
> Using filters on continuous feeds fails
> ---------------------------------------
>
> Key: COUCHDB-579
> URL: https://issues.apache.org/jira/browse/COUCHDB-579
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 0.10
> Environment: Mac OSX 10.6
> Reporter: Joscha Feth
> Attachments: stacktrace-579.txt
>
>
> When using continuous feeds, such as for example:
> /mydb/_changes?feed=continuous&heartbeat=1000&id=myId&since=428&filter=complete/example
> CouchDB fails with a status code of 500 after putting a new document into the
> database.
> test filter for this issue:
> "example": "function(doc, req) { return true; }"
> sysout from couchdb:
> ....PUT here....
> 1> [info] [<0.644.0>] OS Process :: Error converting object to JSON:
> TypeError: toJSON.dispatcher[val.constructor.name] is not a function
> 1> [info] [<0.642.0>] 192.168.178.45 - - 'GET'
> /mydb/f3cacfc2bfbf1aa0b0c8313fc7b181ec?revs_info=true 200
> 1> [info] [<0.1045.0>] 192.168.178.45 - - 'GET' / 200
> 1> [error] [<0.1039.0>] OS Process Error :: {os_process_error,"OS process
> timed out."}
> 1> [info] [<0.1039.0>] 192.168.178.45 - - 'GET'
> Can be reproduced - as soon as feed is not filtered, the issue goes away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
